agentleFS
opendatadiscoveryopendatadiscovery/odd-team/.claude/skills/status/SKILL.md

status

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

Show current progress of the audit and implementation system — scanner completion, backlog counts, blockers.

186 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

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 1

    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. Very specific:

    Read state/PROGRESS.md and display its contents

    line 13
  2. Distinctive:

    If counts don't match PROGRESS.md, update it

    line 18
  3. Very specific:

    when network allows: curl -s https://api.github.com/repos/opendatadiscovery/odd-platform/releases/latest + .../milestones?state=open

    line 21

“Common” is measured: kept by at least 6 in 10 of the 154 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

System Status

Show the current state of the ODD Team maintenance system.

Protocol

  1. Read state/PROGRESS.md and display its contents
  2. Count actual files to verify accuracy:
    • Scanner completion: check findings/ for output from each scanner
    • Backlog counts: count files in backlog/{category}/ by status (grep frontmatter)
    • Navigation coverage: count domain files with vs. without populated code entry points
  3. If counts don't match PROGRESS.md, update it
  4. Release trains (adrs/drafts/release-train-doc-gating.md) — derive, never from a state file:
    • open trains: grep -rl 'milestone:' backlog/ contributor/ grouped by version × status (contributor/ is not optional — CTRIB items are the largest producer of release-gated work; a backlog/-only grep hid 22 stale items for 10 weeks, LSN-041) + git -C ../documentation branch -r --list 'origin/release/*'
    • when network allows: curl -s https://api.github.com/repos/opendatadiscovery/odd-platform/releases/latest + .../milestones?state=open
    • reverse check (LSN-041) — merged upstream work with no workspace record: GET /search/issues?q=repo:opendatadiscovery/odd-platform+author:app/odd-contributor+type:pr and diff the head branches (contrib/CTRIB-NNN-*) against ls contributor/CTRIB-*.md. A merged PR with no record is invisible work; book it before anything else.
    • a published release with a still-existing train, or a closed milestone with pending-release items → Next action = the release gate (/implement release:{version}, then post-merge /review release:{version} — playbooks/release-train-merge.md)
  5. Report:
    • Overall phase (audit / triage / implementation / review)
    • What's been done
    • What's next (highest priority pending scanner or work item)
    • Any blockers or stale items

Quick View Format

Phase: {current phase}
Scanners: {done}/{total} complete
Backlog: {total} items ({critical} critical, {high} high, {medium} medium, {low} low)
In Progress: {count} items
Done: {count} items
Release trains: {version}: {n} pending-release / {m} in-flight | none open
Navigation: {populated}/{total} domains have code pointers

Next action: {recommended next step}

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.