research-agent/skills/status/SKILL.md
Show the current state of an in-flight research-agent run from .research/state.md, log.md, and attempts/. Read-only summary of cycles, sub-problems, hypothesis statuses, eval trend, and current focus.
npx skillsauth add queelius/claude-anvil statusInstall 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.
Show the current state of an in-flight research-agent run. Read-only: this skill never modifies the .research/ directory or relaunches the agent.
Use the Glob tool to confirm .research/ exists in the working directory.
If absent, tell the user there is no research run here and suggest
/research-agent:research to start one.
Read in order (Read tool):
.research/goal.md for the original goal and eval script path.research/state.md for sub-problem statuses, hypothesis statuses, and current focus.research/log.md for the last 10 cycle entries (read the full file if it is short, otherwise tail with Bash: tail -200 .research/log.md)Use Glob and Bash to count:
attempts/*/notes.md: total attempts; list the most recent 3 with their
slugs and one-line summariesfindings/*: confirmed results promoted out of attempts/synthesis.md: present means the run has concluded (note this prominently)Output a structured summary:
# Research Status: {one-line goal}
## Goal
{verbatim from goal.md, trimmed if very long}
## Run state
- Total cycles logged: N
- Last cycle: {timestamp} in {phase}
- Current focus: {from state.md}
- Concluded: yes (synthesis.md present) | no
## Sub-problems
| Status | Count |
|--------|-------|
| open | N |
| in-progress | N |
| resolved | N |
| abandoned | N |
Currently focused sub-problem: {description}
## Hypotheses
| Status | Count |
|--------|-------|
| untested | N |
| confirmed | N |
| refuted | N |
| inconclusive | N |
## Recent activity
- {date} Cycle N: {hypothesis snippet} via {modality} -> {pass/fail}
- ... (last 5 cycles)
## Eval trend
- Latest score: X (or "self-evaluation")
- Best score: Y
- Trend over last 5 cycles: improving | flat | declining
## Attempts inventory
- {N} attempts total
- {M} findings promoted
- Most recent attempts:
- attempts/{NNN}-{slug}: {one-line note}
- ...
End the report with a brief next-actions block based on the run state:
synthesis.md present): point the user to .research/synthesis.md/research-agent:resume to continue/research-agent:synthesize to lock in current results, or note that the researcher should pivot strategies on next resumetools
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).