Skip to content
Back to skills

Status

ASecurity

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.

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 5, 2026
ai-agentspythonbashgit

Works with

  • claude code
  • cli

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add fullymiddleaged/Clawness --skill status --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Status?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Status
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fullymiddleaged-status/badge)](https://www.skillsdirectory.com/skills/fullymiddleaged-status)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: status
description: >
  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.
---

# 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):
> ```bash
> 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
   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"

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.