agentleFS
akimisri17akimisri17/idea-to-app-kit/.agents/skills/log-lesson/SKILL.md

log-lesson

Skill0 starsChanged 40 days agoMITView on GitHub

Writes down a mistake before fixing it, so it isn't repeated in later sessions. Use whenever the person corrects you or reports a problem ("that's wrong", "it should be…", "you missed…", "this doesn't work"), when a check or test fails, or when the plan review finds a gap.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Add the cheapest reliable guard so it can't come back, and fill in the Guard column:

    line 10
  2. Very specific:

    If the same kind of mistake could happen elsewhere (another form, another role, a later wave), add it to that wave's test list in …

    line 16

≈ “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

Log a lesson (before fixing)

  1. First, add a row to docs/lessons.md: date · what went wrong (concrete) · why it happened · the fix you'll make · guard (leave empty for now) · status open.
  2. Then make the fix.
  3. Add the cheapest reliable guard so it can't come back, and fill in the Guard column:
    1. a test or check that runs (best);
    2. a hook;
    3. a rule that loads only for that part of the code (see AGENTS.md);
    4. one line in AGENTS.md (last resort).
  4. Set the status to guarded.
  5. If the same kind of mistake could happen elsewhere (another form, another role, a later wave), add it to that wave's test list in docs/5-BUILD-PLAN.md.
  6. Tell the person in one or two sentences what was wrong, what you changed, and how it's now guarded.

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.