agentleFS
alexj11324alexj11324/Mikka/.claude/skills/teach/SKILL.md

teach

Skill87 starsChanged 4 days agoAGPL-3.0View on GitHub

Teach the user a new skill or concept, within this workspace.

216 other projects use a version of this, 98 of them edited; 93 of 98 edited versions we compared changed its rules; 6 new projects in the last 4 weeks, against 10 the 4 before.

How people change it

93 of 98 edited versions changed its rules, and some changes recur.

Of the 98 edited versions we compared: 5 keep every rule, 93 made changes of their own.

Rules people drop

  1. Treat the current directory as a teaching workspace. Workspace paths (./lessons/ and the rest) resolve from the directory /teach was run in; only the *-FORMAT.md links resolve from this skill's folder. …dropped by 91 of 93
  2. If possible, open the lesson file for the user by running a CLI command.dropped by 9 of 93
  3. Every lesson should be tied into the mission - the reason that the user is interested in learning about the topic.dropped by 6 of 93
  4. If knowledge is all about acquisition, skills are about durability and flexibility. Make the knowledge stick.dropped by 5 of 93
  5. Before the RESOURCES.md is well-populated, your focus should be to find high-quality resources which will help the user acquire knowledge. Never trust your parametric knowledge.dropped by 5 of 93
  6. If the user is unclear about the mission, or the MISSION.md is not populated, your first job should be to question the user on why they want to learn this.dropped by 4 of 93
  7. When the user asks a question that appears to require wisdom, your default posture should be to attempt to answer - but to ultimately delegate to a community.dropped by 3 of 93

Rules people add

  1. Treat the current directory as a teaching workspace. The state of their learning is captured in this directory in several files:added by 82 of 93

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 6 new projects took it in the last 4 weeks, 0.6× the 4 weeks before.

Week of Sep 20: 1 new projectWeek of Sep 27: 2 new projectsWeek of Oct 4: 5 new projectsWeek of Oct 11: 2 new projectsWeek of Oct 18: 3 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 1 new projectWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use poteto-mode, setup-pstack 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.
  • jaydubya818Skill

    poteto-mode

    Use when non-trivial work should follow the smallest rigorous Jstack workflow.

    Also in 29 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 24 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 44 projects that use this

  • jaydubya818Skill

    principle-migrate-callers-then-delete-legacy-apis

    Apply when replacing an internal API without leaving ambiguous dual paths.

    Also in 38 projects that use this

  • shiwenbin1617Skill

    principle-explain-the-number

    Apply before you measure, and before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 27 projects that use this

  • +7 more from jaydubya818

The file

We split this skill into the rules it gives an agent

7 rules. 4 are common, 0 are distinctive, and 3 are very specific to this project.

  • 4

    Common

    Most of the 138 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 138 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.

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.