Display a read-only dashboard for paper project status: stage, thesis, experiments, review history, venue, and suggested next action. Reads .papermill/state.md.
2 stars
0 votes
0 copies
0 views
Added October 19, 2026
ai-agentsgo
Security analysis
A100/100
Scanned October 19, 2026
$npx -y skills add queelius/claude-anvil --skill status --agent claude-code
Installs into .claude/skills of the current project.
Are you the author of Status?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/queelius-status)
---
name: status
description: >-
Display a read-only dashboard for paper project status: stage, thesis,
experiments, review history, venue, and suggested next action. Reads
.papermill/state.md.
---
# Status Dashboard
Present a concise project status dashboard for an academic paper managed by Papermill. This skill is **read-only** -- it does not modify any files.
## Step 1: Read the project file
Read `.papermill/state.md` from the repository root (Read tool).
If the file does not exist, stop and display:
> No `.papermill/state.md` found in this repository. Run `/papermill:init` to set up Papermill for this project.
Do not proceed further if the file is missing.
## Step 2: Parse the frontmatter and body
The file has YAML frontmatter (between `---` delimiters) and a markdown body below it. Parse both. The frontmatter contains structured project metadata. The body contains freeform notes and activity logs.
## Step 3: Present the dashboard
Display a dashboard with the following sections, using the exact headers shown. For any section where data is absent or empty in the frontmatter, show the fallback text indicated.
### Stage
Show the current `stage` value with a brief one-line description:
- **idea** -- Exploring research questions and directions
- **thesis** -- Refining the central claim and novelty
- **literature** -- Surveying prior work and identifying gaps
- **outlining** -- Structuring the argument and paper skeleton
- **drafting** -- Writing sections and producing content
- **review** -- Incorporating feedback and revising
- **submission** -- Final editing, formatting, and submission prep
If no stage is set, show: "No stage set. Run `/papermill:init` to configure."
### Thesis
Show the `thesis.claim` and `thesis.novelty` fields. Format as:
> **Claim:** [claim text]
> **Novelty:** [novelty text]
If the thesis fields are empty or not defined, show: "Not yet defined. Run `/papermill:thesis` to develop your central claim."
### Prior Art
Show a summary from the `prior_art` fields:
- **Key references**: count of entries in `key_references` (e.g., "12 key references")
- **Last survey date**: the `last_survey` date
- **Identified gaps**: the `gaps` text
If no prior art data exists, show: "No survey yet. Run `/papermill:prior-art` to begin."
### Experiments
If `experiments` contains entries, display a markdown table:
| Name | Type | Status | Last Run |
|------|------|--------|----------|
| ... | ... | ... | ... |
If the experiments list is empty, show: "None registered."
### Reviews
Show a summary from `review_history`:
- **Count**: number of reviews conducted
- **Last review date**: when the most recent review occurred
- **Unresolved findings**: derived value, not a stored field. If the most recent review_history entry's `recommendation` is not `ready`, report that review's `findings_critical` + `findings_major` + `findings_minor` as unresolved (treat a missing `findings_critical`, from reviews recorded before it existed, as 0); otherwise report none.
- **Revision**: if the entry has `revised`/`findings_fixed` (written by `/papermill:revise`), show "Revised YYYY-MM-DD: N findings fixed" and subtract `findings_fixed` from the unresolved count (floor at zero).
If no reviews exist, show: "No reviews yet."
### Venue
Show the `venue.target` field. If not set, show: "Not yet selected."
If `venue.candidates` has entries, list them as bullet points.
### Related Papers
If `related_papers` contains entries, display a markdown table:
| Project | Relationship | Description |
|---------|-------------|-------------|
| ... | ... | ... |
Where **Project** is the last path component of `path` (e.g., `masked-causes-in-series-systems`), **Relationship** is the `rel` value, and **Description** is the `label`.
If the `related_papers` list is empty or missing, show: "None linked. Run `/papermill:init` with refresh to discover related projects."
## Step 4: Suggest the next action
Based on the current project state, suggest exactly one next skill to run. Evaluate the conditions in order and use the first match:
1. If the thesis is not defined or empty --> "Consider running `/papermill:thesis` to define your research claim."
2. If the thesis is defined but no prior art data exists --> "Consider running `/papermill:prior-art` to survey related work."
3. If the markdown body does not contain a `## Outline` section and the stage is before `outlining` --> "Consider running `/papermill:outline` to structure the paper."
4. If an outline exists (a `## Outline` section or an outline file) but there is no manuscript content yet --> "Consider running `/papermill:draft` to draft the paper with the multi-agent writer."
5. If the stage is `drafting` and there is written content --> "Consider running `/papermill:review` to get feedback on the current draft."
6. If the latest review's `recommendation` is not `ready` and the entry has no `revised` date --> "Consider running `/papermill:revise` to apply the findings, then re-run `/papermill:review`."
7. If the latest review's `recommendation` is not `ready` and the entry HAS a `revised` date --> "A revision pass was applied; re-run `/papermill:review` to verify the findings are resolved."
8. If the latest review's `recommendation` is `ready` --> "Consider running `/papermill:polish` for final editing, or `/papermill:venue` to evaluate target venues."
9. Otherwise --> "The project is in good shape. Continue working on the current stage."
Display this under a **Suggested next step** heading.
## Step 5: Show recent activity
Read the last 10 non-empty, non-heading lines from the markdown body of `.papermill/state.md` (the content below the frontmatter). These typically contain timestamped notes or activity logs.
Display them under a **Recent activity** heading. If the body is empty or contains no notes, show: "No activity logged yet."
## Formatting rules
- Use plain markdown throughout. No HTML.
- Keep the dashboard compact. Each section should be a few lines at most.
- Do not editorialize or add commentary beyond what is specified above.
- Do not modify `.papermill/state.md` or any other file. This skill is read-only.