agentleFS
Sign inStart free
AlenroyfeildAlenroyfeild/ai-dev-workspace/skills/lesson/SKILL.md

lesson

Skill0 starsChanged 26 days agoMITView on GitHub

Record a requested mistake-to-rule lesson in workspace memory.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use explain and start.

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.
  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the user's requested lesson and verified session context to form one line: what happened → rule.

    line 7

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use the user's requested lesson and verified session context to form one line: what happened → rule. Ask if either part is missing; omit secrets and private identifiers. When verified context identifies relevant files or an area, suggest optional --path "<relative repo glob>" (repeatable) and --area "<area>" tags; do not guess paths. Run ws lesson add "<what happened → rule>" with the agreed tags, then ws lesson search "<distinctive words>" to confirm it was recorded. Report the saved rule briefly. Briefs prefer lessons matching files changed from the claimed task's starting commit, then its title/area.

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.

Reviews can't be read right now.

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