agentleFS
aleemont1aleemont1/TheCouncil/.claude/skills/add-lens/SKILL.md

add-lens

Skill1 starsChanged 37 days agoMITView on GitHub

Add a new engineering lens (skill) to TheCouncil and register it everywhere it must appear.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add the lens $ARGUMENTS. Categories in use: architecture, distributed, formal, performance, resilience, security, state, systems, types, …

    line 8
  2. Very specific:

    Read one existing skills/<category>/*/SKILL.md in the same category and match its structure, tone and length.

    line 10
  3. Very specific:

    Update the seat count ("18") in README, INSTALL.md, package.json, plugin.json, gemini-extension.json, .claude-plugin/*.json and …

    line 17
  4. Very specific:

    If an existing lens conflicts with the new one, add the new slug to that lens's conflicts_with too.

    line 18
  5. Very specific:

    Run python3 scripts/check-manifests.py and fix every error.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Add the lens $ARGUMENTS. Categories in use: architecture, distributed, formal, performance, resilience, security, state, systems, types, router.

  1. Read one existing skills/<category>/*/SKILL.md in the same category and match its structure, tone and length.
  2. Create skills/<category>/<slug>/SKILL.md. Required frontmatter: name (equals the directory name), description, triggers (JSON list), conflicts_with (JSON list of category/slug), primary_sources (title + url, real sources only). Required sections, in order: an **Apply** paragraph copied verbatim from a sibling lens (directly under the H1), then Core Philosophy & Deliberate Rejections, Hard Implementation Rules, Code Review Checklist, Canonical Idiom. Write description as the lens's leading concept followed by Use when ... branches.
  3. Register it:
    • .claude-plugin/plugin.json: add ./skills/<category>/<slug> to skills, keep alphabetical order.
    • skills/registry.json: add an entry to skills with name, path, category, author, and the same triggers, conflicts_with, primary_sources as the SKILL.md.
    • skills/registry.json conflict_matrix: add a pair for each real conflict (tension, thesis_a, thesis_b).
    • README.md: add a row to the seats table, a line to the layout tree, and the author's works to Primary Engineering Works.
    • Update the seat count ("18") in README, INSTALL.md, package.json, plugin.json, gemini-extension.json, .claude-plugin/*.json and registry.json descriptions.
    • If an existing lens conflicts with the new one, add the new slug to that lens's conflicts_with too.
  4. Run python3 scripts/check-manifests.py and fix every error. Report warnings you did not fix.

Cite only sources you have verified. Write plain prose.

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.