benchmark
Run SWE-bench Lite benchmarks against agtx coding agent workflows. Guides setup, configuration, execution, evaluation, and…
@fynnflueggeInstall SkillDevelopment
Skill
/agtx-research
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 Code
$ npx -y skills add fynnfluegge/agtx --skill agtx-research --agent claude-code
Codex
$ npx skills add fynnfluegge/agtx --skill agtx-research -a codex -y
Cursor
$ npx skills add fynnfluegge/agtx --skill agtx-research -a cursor -y
Gemini CLI
$ npx skills add fynnfluegge/agtx --skill agtx-research -a gemini-cli -y
GitHub Copilot
$ npx skills add fynnfluegge/agtx --skill agtx-research -a github-copilot -y
OpenCode
$ npx skills add fynnfluegge/agtx --skill agtx-research -a opencode -y
Windsurf
$ npx skills add fynnfluegge/agtx --skill agtx-research -a windsurf -y
SKILL.md
agtx-research.SKILL.mdname: agtx-research
description: 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.
Research Phase
You are in the **research phase** of an agtx-managed task. This is a read-only exploration.
Input
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.
Instructions
1. Fetch the task description via `get_task` 2. Explore the codebase to find relevant files, patterns, and architecture 3. Identify dependencies, related code, and potential complexity 4. Assess feasibility and estimate scope
Output
Write your findings to `.agtx/research.md`. Include:
Relevant Files
Key files and their roles — what exists, what needs changing.
Architecture
How the relevant parts of the codebase fit together.
Complexity
Assessment of scope — simple change, moderate refactor, or major undertaking.
Open Questions
Things that need clarification before planning can begin.
CRITICAL: Do Not Modify Code
This is a **read-only** exploration:
- Do NOT modify any source files
- Do NOT create branches or worktrees
- Do NOT start planning or implementing
- Say: "Research complete. Findings written to .agtx/research.md."
- Wait for further instructions
Output Style
Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
Read more
name: agtx-research description: 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.
Research Phase
You are in the **research phase** of an agtx-managed task. This is a read-only exploration.
Input
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.
Instructions
1. Fetch the task description via `get_task` 2. Explore the codebase to find relevant files, patterns, and architecture 3. Identify dependencies, related code, and potential complexity 4. Assess feasibility and estimate scope
Output
Write your findings to `.agtx/research.md`. Include:
Relevant Files
Key files and their roles — what exists, what needs changing.
Architecture
How the relevant parts of the codebase fit together.
Complexity
Assessment of scope — simple change, moderate refactor, or major undertaking.
Open Questions
Things that need clarification before planning can begin.
CRITICAL: Do Not Modify Code
This is a **read-only** exploration:
- Do NOT modify any source files
- Do NOT create branches or worktrees
- Do NOT start planning or implementing
- Say: "Research complete. Findings written to .agtx/research.md."
- Wait for further instructions
Output Style
Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
In this plugin
See everything inside Ships withagtx
The terminal-native agentic development environment for 10x productivity. A blackboard for coding agents - One shared board. A fleet of agents.
1.7k8 skills1 MCP
Stars on GitHub
Momentum
- stars in total
- 1.7k
Other skills on agtx.
@fynnflueggeInstall Skillagtx-execute
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
@fynnflueggeInstall Skillagtx-plan
Plan a task implementation. Analyze the codebase, create a detailed plan, write it to .agtx/plan.md, then stop and wait for user…
@fynnflueggeInstall Skillagtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
@fynnflueggeInstall Skillbrainstorm
Enter brainstorm mode to explore a feature or enhancement idea. Stays in discussion mode only — no planning, no implementation.…
@fynnflueggeInstall Skilloneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each…
@fynnflueggeInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about agtx-research.
- Which coding agents can use agtx-research?
- agtx-research installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.