agentleFS
ldaytonldayton/Dippy/.claude/skills/verify-counts/SKILL.md

verify-counts

Skill243 starsChanged 8 months agoMITView on GitHub

Verify numerical claims in documentation are still accurate

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Verify all count assertions in documentation against actual values.

    line 6
  2. Very specific:

    Parable tests: Check table in /Users/lily/source/Parable/tests/README.md

    line 24
  3. Distinctive:

    If any claim is STALE or FAIL, note which file(s) need updating.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Verify all count assertions in documentation against actual values.

Claims to Verify

LocationClaimVerification
README.md:1414,000+ testsDippy + Parable combined
../Dippy.wiki/Reference/Security-Model.md:79Over 200 read-only commandsSIMPLE_SAFE count
../Dippy.wiki/Reference/Security-Model.md:94Over 80 toolsCLI handler count
../Dippy.wiki/Reference/Handler-Model.md:21080+ handlersCLI handler count

Verification Commands

Dippy tests:

uv run pytest --collect-only -q 2>/dev/null | tail -1

Parable tests: Check table in /Users/lily/source/Parable/tests/README.md

SIMPLE_SAFE count:

uv run python -c "from src.dippy.core.allowlists import SIMPLE_SAFE; print(len(SIMPLE_SAFE))"

CLI handlers:

ls -1 src/dippy/cli/*.py | grep -v __init__ | wc -l

Output

Report each claim with:

  • Documented value
  • Actual value
  • Status (PASS/FAIL/STALE)

Status Criteria

  • PASS: Actual value is within ~10% of documented value
  • STALE: Claim is technically true but significantly outdated (e.g., "50+" when actual is 77)
  • FAIL: Claim is false

If any claim is STALE or FAIL, note which file(s) need updating.

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.