agentleFS
Sign inStart free
svandragtsvandragt/lessons/skill/SKILL.md

lessons

Skill0 starsChanged 5 months agoNo licenceView on GitHub

Capture concepts the user is learning as numbered lesson files. Use when the user signals they are learning something new — 'what is X?', 'explain X', 'I don't understand X', 'how does X work?', 'TIL', 'never heard of X', 'first time using X', 'new to me' — AND the concept appears unfamiliar to them. Writes lessons to ~/Documents/lessons/NNN-slug.md (one central, cross-project location) with a short explanation, read-more links, and up to three minimally-scoped exercises. Also handles: 'list lessons', 'show lesson N', 'next exercise'.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use distill-prompt, herdr-advisor and 1 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.
  • OpenSWESkill

    distill-prompt

    Distill this conversation's underlying goal into one reusable prompt that reaches the same final outcome in a fresh session.

    Also in 3 projects that use this

  • OpenSWESkill

    herdr-advisor

    Pair a Herdr worker with one advisor, a stronger model that answers questions on the user's behalf to unblock the worker and leads it to its next task, by accepting its prompt suggestion or sending it text: a worker "still waiting on your go" gets `go`. Invoked by the user (`/herdr-advisor`), and by you in one case only, before the first step of the work and whatever the plan's size, when a grilling session has ended with its frontier empty, the user's confirmation has you execute the plan now, no advisor pair is live, and the confirmation did not decline one.

    Also in 3 projects that use this

  • gootfSkill

    log-decisions

    Append-only DECISIONS.md journal at the project root for consequential calls the spec didn't settle. Use when you (or the user) make a non-trivial call worth a durable record — an ambiguity you interpreted, a tradeoff, a deviation, or a hard-to-undo action.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

No licence file, so all rights are reserved — 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 11 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.

Check your setup, free