status
Display a read-only dashboard for paper project status: stage, thesis, experiments, review history, venue, and suggested next action. Reads .papermill/state.md.
What this skill does
# 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**: count or brief summary of open issues 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 the stage is `drafting` and there is written content --> "Consider running `/papermill:review` to get feedback on the current draft." 5. If reviews have been conducted and there are unresolved findings --> "Consider running `/papermill:review` to address open findings." 6. If reviews are done with no unresolved findings --> "Consider running `/papermill:polish` for final editing, or `/papermill:venue` to evaluate target venues." 7. 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.
Related in Data & Analytics
clawarr-suite
IncludedComprehensive management for self-hosted media stacks (Sonarr, Radarr, Lidarr, Readarr, Prowlarr, Bazarr, Overseerr, Plex, Tautulli, SABnzbd, Recyclarr, Unpackerr, Notifiarr, Maintainerr, Kometa, FlareSolverr). Deep library exploration, analytics, dashboard generation, content management, request handling, subtitle management, indexer control, download monitoring, quality profile sync, library cleanup automation, notification routing, collection/overlay management, and media tracker integration (Trakt, Letterboxd, Simkl).
querying-soql
IncludedSOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
habit-flow
IncludedAI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
visualizing-data
IncludedBuilds dashboards, reports, and data-driven interfaces requiring charts, graphs, or visual analytics. Provides systematic framework for selecting appropriate visualizations based on data characteristics and analytical purpose. Includes 24+ visualization types organized by purpose (trends, comparisons, distributions, relationships, flows, hierarchies, geospatial), accessibility patterns (WCAG 2.1 AA compliance), colorblind-safe palettes, and performance optimization strategies. Use when creating visualizations, choosing chart types, displaying data graphically, or designing data interfaces.