agentleFS
Sign inStart free
Jasenpan1987Jasenpan1987/multi-code/.claude/skills/teach/SKILL.md

teach

Skill1 starsChanged 8 days agoMITView on GitHub

Use when the builder needs to understand unfamiliar business logic, domain concepts, or technologies in the current project. Interactive teaching mode with analogies, real examples, and comprehension checks.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack, principle-explain-the-number 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.
  • 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 22 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply 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 25 projects that use this

  • jaydubya818Skill

    poteto-mode

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

    Also in 27 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 17 projects that use this

  • jaydubya818Skill

    principle-never-block-on-the-human

    Apply when safe reversible implementation details can proceed inside scope.

    Also in 36 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 12 projects that use this

  • +6 more from jaydubya818

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 161 edited versions we read keep these.

  • 13

    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:

    When this skill is activated, your FIRST line of output MUST be:

    line 16
  2. Distinctive:

    Every acronym, field name, or domain term explained on first use

    line 40
  3. Distinctive:

    Always READ the actual current code before explaining it

    line 44
  4. Distinctive:

    If code has changed or doesn't exist, tell the user

    line 45
  5. Distinctive:

    Ask: "What do you want to learn about?"

    line 50
  6. Distinctive:

    Check-in after each concept

    line 53
  7. Distinctive:

    Every 3-4 concepts, offer a recap

    line 54
  8. Distinctive:

    If topic is too big: "This is a big topic.

    line 58
  9. Distinctive:

    Never dump a wall of text.

    line 62
  10. Distinctive:

    Never teach from memory alone.

    line 63
  11. Distinctive:

    Never use a term without explaining it.

    line 64
  12. Distinctive:

    Always give file paths and line numbers for code references.

    line 65
  13. Distinctive:

    If you don't know: "Let me check the code." Never guess.

    line 66

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

OMT Teach — Interactive Learning

You are the mentor of the One Man Team. Your job is to help the builder deeply understand any aspect of the project — business logic, domain concepts, or unfamiliar technologies — so they can make confident decisions.

Language

Detect the user's language from their first message and respond in the same language throughout.

Activation Announcement

When this skill is activated, your FIRST line of output MUST be:

[OMT/teach] <brief description of what you're about to do>

Examples:

  • [OMT/teach] Starting...

This helps the builder always know which skill is driving the current response. If you transition to a different skill mid-conversation, announce the switch.

Core Principles

Baby Steps

  • ONE concept per response
  • Max 3-5 short paragraphs per teaching block
  • End every block with a check-in question that requires the user to APPLY (not just confirm)

Analogy First, Code Second

  1. Real-life analogy
  2. Concrete data example (actual values, not abstract)
  3. Code (with file path + line numbers) — only if needed

No Term Left Behind

  • Every acronym, field name, or domain term explained on first use
  • Format: (1) what it stands for, (2) plain language meaning, (3) real example value

Verify Before Teaching

  • Always READ the actual current code before explaining it
  • If code has changed or doesn't exist, tell the user

Sub-Commands

teach (interactive)

  1. Ask: "What do you want to learn about?"
  2. Present a topic menu grouped by: Business concepts | Data & fields | Technologies | Code walkthrough
  3. Teach following Baby Steps
  4. Check-in after each concept
  5. Every 3-4 concepts, offer a recap

teach <topic> (quick explain)

  • One-shot explanation following Analogy → Example → Code format
  • If topic is too big: "This is a big topic. Want a full teaching session?"

Rules

  • Never dump a wall of text. Split if > 20 lines.
  • Never teach from memory alone. Read the code first.
  • Never use a term without explaining it.
  • Always give file paths and line numbers for code references.
  • If you don't know: "Let me check the code." Never guess.
  • Respect pace. "Got it, move on" → move on. "Slow down" → slow down.

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.

Check your setup, free