agentleFS
aka-kikaaka-kika/akakika-skills/skills/session-rituals/til/SKILL.md

til

Skill11 starsChanged 3 months agoMITView on GitHub

Teach the user exactly ONE thing from the current session or project, in plain English, one or two short paragraphs. Use when the user types ;til or "til", asks "what did I learn", "explain one thing from this session", or at session close alongside other closing rituals. Also appropriate mid-session when a concept keeps recurring that the user clearly hasn't used themselves. One thing only — never a list, never a lecture.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    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:

    Default length: two paragraphs max.

    line 52
  2. Distinctive:

    Must come from the actual session content.

    line 53
  3. Distinctive:

    Never condescend. The user ships production apps.

    line 55
  4. Distinctive:

    Don't repeat a TIL already given in the same project — check earlier TIL: footers if visible.

    line 57

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

til

The user is a builder who ships real things, often without a formal CS background. Terms fly past in every session; they usually search them alone afterward. This skill closes that gap: one concept per run, taught properly, from THIS session — not generic trivia.

Picking the one thing

Priority order — take the first that applies:

  1. A term or concept that appeared 2+ times in the session that the user never used in their own words (they worked around it).
  2. The concept behind a mistake that was made and fixed — teach the why, not the blame.
  3. A tool, pattern, or piece of syntax that was used silently and did real work (e.g. a flag, an atomic write, a data structure choice).
  4. Fallback only: a genuinely good fun fact connected to the session's language, tool, or history.

One thing. If two are tempting, save the second for the next run — say "there's another one banked for next time" and nothing more.

How to teach it

  • Name the term first, exactly as it's written, so it can be searched.
  • One or two short paragraphs. Plain English. Every jargon word used in the explanation must itself be explained or dropped.
  • Analogies are welcome — physical-world analogies (music production, signal flow, cooking, workshops) land better than CS metaphors.
  • End with one line: why it mattered in THIS session specifically.
  • Close with: "Want the deeper version?" — and only expand if asked. The deep version may go longer, show code, and link docs.

Output footer

Last line, always, greppable:

TIL: <term> — <summary in ten words or fewer>

Hard rules

  • Exactly one concept. Never a list. Never "3 things you learned."
  • Default length: two paragraphs max. Expansion only on request.
  • Must come from the actual session content. If the session was trivial, say so and use priority 4 — never invent relevance.
  • Never condescend. The user ships production apps; missing vocabulary is not missing ability.
  • Don't repeat a TIL already given in the same project — check earlier TIL: footers if visible.

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.