research-agent/skills/research/SKILL.md
Launch an autonomous research agent that iterates toward a goal through proofs, code, simulations, tests, and counterexample search. Fire-and-forget mode: the agent runs autonomously and writes all results to .research/ in the target project.
npx skillsauth add queelius/claude-anvil researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Launch an autonomous research agent that iterates toward a goal through proofs, code, simulations, tests, and counterexample search.
Read the user's message to extract:
.sh, .py, or similar.If the goal is unclear, ask the user to clarify before proceeding. If no eval script is mentioned, the agent will self-evaluate.
If an eval script path was given, verify it exists (Read tool). If it does not exist, tell the user and ask whether to proceed with self-evaluation instead.
Spawn the researcher agent (Agent tool, subagent_type: research-agent:researcher) with this prompt structure:
<goal>
{the user's research goal, verbatim}
</goal>
<eval>
{path to eval script, or "none - use self-evaluation"}
</eval>
<working_directory>
{current working directory}
</working_directory>
Begin your research. Create .research/ and start the DECOMPOSE phase.
The agent runs autonomously from here. Inform the user:
Research agent launched. It will work autonomously in this directory, writing progress to
.research/log.md. When it finishes, the synthesis will be at.research/synthesis.md.While it runs, you can:
/research-agent:statusto see cycle progress, current focus, and eval trend (read-only)/research-agent:resumeto continue after an interruption or session restart/research-agent:synthesizeto force conclusion if results are good enough or the agent is stalling
tools
This skill should be used when the user asks about research directions, open problems, future work, or follow-up research from the academic literature. Trigger phrases include "open problems in X", "what's next for Y", "future work for paper Z", "research directions on T", "salient follow-up research", "what should I work on next in", "find me follow-up research unrelated to my prior work", "broad survey of W", "neglected directions in V". Routes the request to the right Vista MCP tool, reads back the structured paper sections, and synthesizes research directions in the conversation.
testing
Discover latent themes in the metafunctor corpus. Use when the user wants to find implicit through-lines across their blog posts, surface recurring ideas they have not consciously framed as a series, or get candidate themes for a synthesis post. Reads titles, descriptions, and tags; proposes 3 themes that connect 4+ posts each, each with a single-sentence through-line. Output is a proposal, not a draft. Trigger phrases include "find themes in my posts", "what threads connect my writing", "latent themes in my corpus", "scribe".
development
Use when drafting prose sections for a bookwright (technical non-fiction) project. Encodes the Bernoulli-textbook workflow: atom-outward design, deferral discipline, running threads, page budgets, Path A subagent pattern, header comment block convention.
testing
Use when drafting or executing a paired notebook for a bookwright chapter. Covers when notebooks are required vs optional, numerical-sanity-target convention, exec-from-fresh-kernel requirement, and stack-specific execution commands (Jupyter/R Markdown/Quarto).