agentleFS
Sign inStart free
blueOctopusAIblueOctopusAI/intel-hub/.claude/skills/status/skill.md

status

Skill0 starsChanged 9 months agoMITView on GitHub

Generate a comprehensive but actionable status report. Read config.json for business context. No arguments required. Optionally: /status <project-name> for a single-project deep dive. Before generating the report, run git worktree list to check for active secondary sessions. If any worktrees exist besides the main one: - Report them: "Active parallel sessions: [branch name] at [path]" - Remind the user to merge when done Momentum indicators: - Active this week - Touched recently - Stale (7+ days since last activity) Today:…

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

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No arguments required. Optionally: /status <project-name> for a single-project deep dive.

    line 7
  2. Distinctive:

    Before generating the report, run git worktree list to check for active secondary sessions.

    line 18
  3. Very specific:

    Check the synergy map in data/portfolio/projects.md.

    line 49
  4. Very specific:

    If you spot opportunities the user hasn't considered, add 1-3 NEW recommendations to the Recommendations table in …

    line 57
  5. Distinctive:

    All related action items from intelligence-brief.md

    line 73
  6. Distinctive:

    Ask: "Want me to update any project statuses, or start on [recommended task]?"

    line 88

“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

Status Report

Generate a comprehensive but actionable status report. Read config.json for business context.

Input

No arguments required. Optionally: /status <project-name> for a single-project deep dive.

Data Sources

  1. config.json — Business name and categories
  2. data/portfolio/projects.md — Projects, tiers, statuses, blockers, recommendations
  3. data/research/intelligence-brief.md — Key signals and action items
  4. data/research/intake-log.md — Recent research activity (check for staleness)

Pre-Report Check: Active Worktrees

Before generating the report, run git worktree list to check for active secondary sessions. If any worktrees exist besides the main one:

  • Report them: "Active parallel sessions: [branch name] at [path]"
  • Remind the user to merge when done

Full Status Output

Project Pulse

ProjectTierMomentumBlockerNext Action

Momentum indicators:

  • Active this week
  • Touched recently
  • Stale (7+ days since last activity)

Recommended Focus

Today: 1-2 specific tasks with reasoning This week: 3-5 tasks that compound Parking lot: Important but not urgent

Priority framework:

  1. Revenue-generating work and deadlines
  2. Unblocking other projects (multipliers)
  3. Revenue-adjacent (content, outreach)
  4. Compounding work (tools, automation)
  5. Portfolio polish

Synergy Alerts

Check the synergy map in data/portfolio/projects.md. Flag:

  • Research that applies to a tracked project
  • Tools evaluated but not installed that would help active projects
  • Content ideas that are ready to write (research done, just needs authoring)
  • Pipeline gaps between projects

New Recommendations

If you spot opportunities the user hasn't considered, add 1-3 NEW recommendations to the Recommendations table in data/portfolio/projects.md. Each needs:

  • A specific, actionable suggestion
  • The source (which data led you to this)
  • Initial vote of +0
  • Status: pending

Stale Items

Flag anything untouched for 7+ days:

  • Projects with old "Last touched" dates
  • Action items that haven't progressed
  • Recommendations pending with no votes

Single Project Deep Dive (/status <project>)

  • Full current state
  • All related action items from intelligence-brief.md
  • Related bookmarks and strategy docs
  • Synergies and how they're performing
  • Recommended next 3 actions with reasoning

Principles

  1. Actionable over informational — Every section should end with "do X"
  2. Honest momentum — Don't sugarcoat stale projects
  3. Connect dots — The value is in seeing cross-project patterns
  4. Respect user time — Be concise. Tables over paragraphs.
  5. Decision framework — Revenue > deadlines > unblocking > compounding

After Reporting

Ask: "Want me to update any project statuses, or start on [recommended task]?"

ARGUMENTS: project

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