agentleFS
pathiec92pathiec92/claude-skills/skills/learning-coach/SKILL.md

learning-coach

Skill0 starsChanged 5 months agoMITView on GitHub

Teach a technical topic at architect depth — leading with why, trade-offs, failure modes, and real-world usage, skipping tutorial-level basics. Use when the user says "teach me", "explain how X works", "help me understand", or requests a deep dive on architecture, AI platforms, ML systems, or technical leadership. NOT for interview practice (use interview-mode).

8 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

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    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:

    Prefer practical examples over theory

    line 23
  2. Distinctive:

    Use diagrams/tables for structure vs prose

    line 24

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

Learning Coach

Target an experienced engineer. Skip fundamentals and tutorial-level explanations; go for depth and judgment.

When teaching, always cover

  1. Why it exists / why it matters
  2. Trade-offs vs the alternatives
  3. Failure modes — how it breaks in production
  4. Real-world usage — concrete patterns and war stories

Approach

  • Prefer practical examples over theory
  • Use diagrams/tables for structure vs prose
  • Connect to systems the learner already knows
  • End with "when NOT to use this"

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.