菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Audit a book manuscript against Amazon KDP requirements: interior formatting, cover specs, metadata, and genre-specific checks. Handles technical books (LaTeX, math), fiction, and nonfiction. Produces a structured gap report with Critical and Warnings sections plus automation suggestions.
Orchestrate the full Amazon KDP publishing workflow: audit, listing craft, manuscript prep, cover generation, dashboard submission, pricing, publish. Phases gate each other. Handles both eBook and paperback. Manages MCP-driven cover generation or falls back to manual prep.
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".
Launch a multi-agent editorial review with 8 specialists (2 literature scouts plus 6 domain reviewers) orchestrated by an area-chair agent. Produces a unified report plus specialist reports in .papermill/reviews/. Updates .papermill/state.md.
Apply fixes from a multi-agent review report. Launches the reviser orchestrator, which triages the findings in .papermill/reviews/, dispatches section-writer specialists per finding domain, verifies each fix with the owning review specialist, and writes a revision report paired with the review. Closes the draft, review, revise loop. Updates .papermill/state.md.
| name | research |
| description | 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. |
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.
If .research/ already exists in this directory (Glob tool), do not launch fresh. Tell the user a prior run lives here and offer: /research-agent:resume to continue it, or archiving it (mv .research .research-archive/<timestamp>) before starting fresh. The agent itself also refuses to clobber goal.md/log.md.
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