菜单
Resume an interrupted research-agent run. Re-launches the researcher with instructions to read .research/state.md and log.md, reorient, and continue from the documented current focus. Use after a context compression, session restart, or explicit pause.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | resume |
| description | Resume an interrupted research-agent run. Re-launches the researcher with instructions to read .research/state.md and log.md, reorient, and continue from the documented current focus. Use after a context compression, session restart, or explicit pause. |
Continue a paused or interrupted research-agent run. If the user names a branch (e.g. "resume the induction-proof branch" or /research-agent:resume induction-proof), verify .research/branches/<name>/ exists and add <branch>name</branch> to the launch prompt; all checks below then apply to the branch subtree's files.
Use the Read tool on .research/state.md. If state.md is missing but .research/goal.md exists (a run interrupted before its first REFLECT), still resume: the researcher reorients from goal.md and log.md and rebuilds state.md. Only when .research/ itself is absent should you tell the user there is no research to resume and suggest /research-agent:research.
Use Read tool to load .research/state.md and the last 5 entries from .research/log.md. Show the user a one-paragraph preview of what the researcher will pick up:
Resuming research on "{goal}". Current focus: {from state.md}. Last cycle was {N} on {date}: {modality} -> {result}. Outstanding sub-problems: {count open}. Untested hypotheses: {count untested}.
Spawn the researcher agent (Agent tool, subagent_type research-agent:researcher) with this prompt:
<mode>resume</mode>
<working_directory>
{absolute path to current working directory}
</working_directory>
Resume your research from disk. Do NOT recreate .research/ or
overwrite goal.md.
Step 1: Read .research/state.md in full to reload current beliefs,
sub-problem statuses, hypothesis statuses, and current focus.
Step 2: Read the last 15 entries of .research/log.md to recall recent
activity, including any failed attempts and pivots.
Step 3: Continue your research loop from the documented "Current
focus" in state.md. Run cycles as normal: DECOMPOSE if needed,
HYPOTHESIZE, ATTEMPT, EVALUATE, REFLECT. Append to log.md after
every cycle.
If state.md indicates the goal has been concluded (synthesis.md
exists), do NOT run new cycles; tell the orchestrator the research
is already complete and point at synthesis.md.
After launching, tell the user:
Researcher resumed. It has reloaded state from .research/state.md and is continuing from the current focus. Use
/research-agent:statusto check progress, or/research-agent:synthesizeto force conclusion.
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.