Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Explore the codebase to understand a task before planning. Write findings to .agtx/research.md and stop. This is a read-only exploration — do not modify any files.
.claude/skills/fynnfluegge-agtx-research/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-21 | ✗→✓ | ▲ Improved | -17% | 0% |
| case-17 | ✓→✗ | ▼ Worse | -53% | 0% |
| case-22 | ✓→✗ | ▼ Worse | -43% | 0% |
| case-20 | ✓→✓ | = Same ✓ | 163% | 0% |
| case-11 | ✗→✗ | = Same ✗ | 77% | 0% |
You are in the research phase of an agtx-managed task. This is a read-only exploration.
The argument to this command is a task ID. Fetch the task description using the agtx MCP tool:
mcp__agtx__get_task(task_id: "<the id passed to this command>")Use the description field as the task to work on.
get_taskWrite your findings to .agtx/research.md. Include:
Key files and their roles — what exists, what needs changing.
How the relevant parts of the codebase fit together.
Assessment of scope — simple change, moderate refactor, or major undertaking.
Things that need clarification before planning can begin.
This is a read-only exploration:
Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: what] why]. Done.
Other measured skills in the registry, with their headline benchmark lift.