agentleFS
fullymiddleagedfullymiddleaged/Clawness/skills/status/SKILL.md

status

Skill5 starsChanged 4 months agoMITView on GitHub

Show the current Clawness configuration: which rules are loaded, which agents are available, and how the hook is configured. Use to understand what rules Claude is seeing for this project.

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

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

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep this FAST — it's a quick health check, not a full scan.

    line 24
  2. Distinctive:

    Show the corpus + token cost: Run (fast):

    line 43
  3. Very specific:

    Project rules (only if present): If .clawness/rules/ exists in the project (walk up to the git root), mention it.

    line 49

“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

Clawness Status

Show the user what's currently active in their Clawness setup.

Running the Clawness CLI. It ships with the plugin but isn't on your PATH. Use the bundled launcher, falling back to the wrapper the SessionStart bootstrap stashes (older Claude Code doesn't substitute the plugin root in skills):

CLAW="${CLAUDE_PLUGIN_ROOT}/scripts/clawness-cli.sh"
[ -f "$CLAW" ] || CLAW="${CLAUDE_CONFIG_DIR:-$HOME/.claude}/clawness/clawness-cli.sh"
bash "$CLAW" <command>          # e.g. bash "$CLAW" stats

If neither path exists (an older Claude Code before the bootstrap has run), start a fresh session. (Editable/manual installs may instead use python -m clawness.cli ....)

Keep this FAST — it's a quick health check, not a full scan. Step 1 already proves retrieval at zero cost, so a test query is unnecessary.

Steps

  1. Report the rules you already see (no command). You (Claude) receive the Clawness rule block at the top of your context this turn. Summarize it: how many mandatory + relevant rules, and a few rule IDs. If you see it, injection is working — this alone is the health check.

    If you do NOT see an injected block, say so plainly and do not rationalize it. The hook injects the global rules on every prompt in every directory — the working directory (including being in the Clawness source repo) does not disable injection; it only affects the optional .clawness/rules/ project overlay. A missing block means the hook is not running — either not loaded this session (needs a restart / /reload-plugins) or erroring (check /hooks and claude --debug). Never attribute a missing block to the current directory.

  2. Show the corpus + token cost. Run (fast):
    bash "$CLAW" stats
    Report total rules, domains, and the Tokens / turn line.
  3. Project rules (only if present). If .clawness/rules/ exists in the project (walk up to the git root), mention it; otherwise skip silently.

Summary — keep it to a few lines:

  • Rule injection: working (you saw the block) / not seeing rules
  • Global rules: N across M domains; ~N tokens/turn (tune with CLAW_TOP_K, CLAW_VERBOSE, CLAW_COMPACT)
  • Project rules: N, or "none — bash \"$CLAW\" init . to add some"

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.