agentleFS
Sign inStart free
faizkhairifaizkhairi/claude-code-blueprint/skills/status/SKILL.md

status

Skill73 starsChanged 4 months agoMITView on GitHub

Show project status dashboard across registered repositories

  • Reads credentials

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 4 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check CLAUDE.md or memory for registered project paths

    line 11
  2. Distinctive:

    Services: Check if dev servers are running

    line 13
  3. Distinctive:

    Check CLAUDE.md for configured dev ports

    line 14
  4. Very specific:

    Use lsof -i :PORT or netstat to check port availability

    line 15
  5. Distinctive:

    Database: Check database connectivity if applicable

    line 17
  6. Very specific:

    Test connection using the project's database URL from its env/config (.env, application.yml, config/database.yml, etc.)

    line 18
  7. Distinctive:

    Test Status: Run a quick test count (if test command is known from CLAUDE.md)

    line 22

“Common” is measured: kept by at least 6 in 10 of the 146 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project status dashboard:

  1. Git Status for each project in the workspace:
    • Branch name, uncommitted changes, last commit, ahead/behind remote
    • Check CLAUDE.md or memory for registered project paths
  2. Services: Check if dev servers are running
    • Check CLAUDE.md for configured dev ports
    • Use lsof -i :PORT or netstat to check port availability
  3. Database: Check database connectivity if applicable
    • Test connection using the project's database URL from its env/config (.env, application.yml, config/database.yml, etc.)
  4. Recent Activity: Last 3 commits per repo
  5. Test Status: Run a quick test count (if test command is known from CLAUDE.md)

Present as a clean dashboard with status indicators.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free