status

Prints fluidpy chapter progress, open items, environment state, and the next command to run.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/shammun/fluidpy --skill status-shammun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/shammun/fluidpy/tree/main/.claude/skills/status
Command: npx skills add https://github.com/shammun/fluidpy --skill status-shammun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through a multi-chapter, multi-phase book-building pipeline, it is hard to remember which chapter is in progress, which phases passed or failed, and what to do next. This Skill reads the project's tracking files and prints a single consolidated status report. ## Core Features & Use Cases - Progress table: Renders one compact table from progress.json showing every chapter's phase status (analyze, curate, design, implement, verify, review, viz, notebook, knowledge, publish) with pass/running/fail/blocked/todo markers. - Current-chapter detail: Surfaces the verdict, open items, viz summary, and must-fix list from the current chapter's verification, viz, and review reports, each trimmed to eight lines. - Environment and git check: Reports Python and package versions, chapter text split state, Jupyter kernel registration, recent commits, working tree cleanliness, remote sync, and GitHub Pages availability. - Use Case: After returning to the fluidpy project, run /status to see that chapter 2 failed verification, review its must-fix items, and get the exact /do-chapter command to resume. ## Quick Start Run /status to print the full project progress table, current chapter issues, environment state, and the recommended next command.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check progress of a multi-phase chapter pipeline?

Run /status to print one compact table from progress.json showing each chapter's phase status with pass, running, fail, blocked, or todo markers. A chapter counts as finished only when its publish phase passes.

What does the status report show for the current chapter?

For the first unfinished chapter it shows the verdict line and open items from the verification report, the summary table from the viz report, and the must-fix list from the review report, each trimmed to eight lines.

Does the status check verify the Python environment?

Yes. It reports the virtualenv Python version, numpy, scipy, sympy, plotly, and playwright versions, whether the chapters directory is split into per-chapter text files, and whether the fluidpy-venv Jupyter kernel is registered.

How does status decide which command to run next?

It recommends /setup-project if the environment is missing, /do-chapter N --from the first failing phase for interrupted chapters, /clear then /do-chapter N+1 when a chapter is fully published, or gh commands when chapter 1 lacks a git remote.

Can status check if the published site is live?

Yes. When a git origin exists, it sends an HTTP request to the GitHub Pages root taken from the site_url in book.yaml and reports the returned status code.