agentleFS
Sign inStart free
sammcjsammcj/agentic-coding/Skills/extract-wisdom/CLAUDE.md

agentic-coding / extract-wisdom

CLAUDE.md167 starsChanged 10 days agoApache-2.0View on GitHub

Before making major changes to the Extract Wisdom skill you should first activate any skill-builder / skill-creator related skills you might have, you can skip this however for simple change requests. When making changes to the Python script, always run the LSP / linter and ensure there's no errors: - uvx ty check scripts/wisdom.py - python3 -m unittest discover -s tests (stdlib, no network; covers the frames quote lookup) When testing PDF functionality during development or debugging avoid reading the…

We split this CLAUDE.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Before making major changes to the Extract Wisdom skill you should first activate any skill-builder / skill-creator related skills you …

    line 3
  2. Distinctive:

    When making changes to the Python script, always run the LSP / linter and ensure there's no errors:

    line 5
  3. Distinctive:

    When testing PDF functionality during development or debugging avoid reading the raw PDF data in to your context directly as this can …

    line 9
  4. Very specific:

    If you make changes to the static index.html template or if the user asks you to regenerate the index HTML, run uv run …

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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
CLAUDE.md

Extract Wisdom Skill

Before making major changes to the Extract Wisdom skill you should first activate any skill-builder / skill-creator related skills you might have, you can skip this however for simple change requests.

When making changes to the Python script, always run the LSP / linter and ensure there's no errors:

  • uvx ty check scripts/wisdom.py
  • python3 -m unittest discover -s tests (stdlib, no network; covers the frames quote lookup)

When testing PDF functionality during development or debugging avoid reading the raw PDF data in to your context directly as this can overload the context.

If you make changes to the static index.html template or if the user asks you to regenerate the index HTML, run uv run ~/.claude/skills/extract-wisdom/scripts/wisdom.py index

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