agentleFS
Andamio-PlatformAndamio-Platform/coach/skills/start/SKILL.md

start

Skill6 starsChanged 8 months agoMITView on GitHub

Welcome to Coach. Choose your pathway — beginner, apprentice, or teacher — to start building a course.

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-audio 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.
  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +5 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 117 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If running as a plugin (${CLAUDE_PLUGIN_ROOT} is set):

    line 18
  2. Very specific:

    Check whether ${CLAUDE_PLUGIN_DATA}/knowledge/ exists.

    line 20
  3. Very specific:

    If it does not exist, copy the seed knowledge base from ${CLAUDE_PLUGIN_ROOT}/knowledge/ to ${CLAUDE_PLUGIN_DATA}/knowledge/.

    line 21
  4. Distinctive:

    If not running as a plugin, skip this step.

    line 24
  5. Distinctive:

    After the user selects a pathway, read and follow the instructions in the corresponding skill:

    line 50
  6. Distinctive:

    If the user isn't sure which pathway fits:

    line 60

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

Welcome to Coach

You help people build courses. Find out how they'd like to work.

Instructions

0. Plugin Initialization

If running as a plugin (${CLAUDE_PLUGIN_ROOT} is set):

  1. Check whether ${CLAUDE_PLUGIN_DATA}/knowledge/ exists.
  2. If it does not exist, copy the seed knowledge base from ${CLAUDE_PLUGIN_ROOT}/knowledge/ to ${CLAUDE_PLUGIN_DATA}/knowledge/. This gives the user a working knowledge base that they can accumulate into via /compound.
  3. Confirm initialization silently — do not interrupt the welcome flow. If initialization happened, append a brief note after the welcome message: "Knowledge base initialized with seed patterns from 7+ courses."

If not running as a plugin, skip this step.

1. Welcome

Welcome to Coach.

Coach helps you design learning experiences — courses where each module
has a clear target: something a learner can do after completing it.

Each course you build makes the system smarter for the next one.

How would you like to get started?

1. Beginner — You want to design a personalized learning experience
   about something new.

2. Apprentice — You know some of the content and you're ready to
   build a course.

3. Teacher — You have learning targets ready, and you're an expert
   on the subject.

2. Dispatch

After the user selects a pathway, read and follow the instructions in the corresponding skill:

  • 1 (Beginner) → Read and execute skills/beginner/SKILL.md
  • 2 (Apprentice) → Read and execute skills/apprentice/SKILL.md
  • 3 (Teacher) → Read and execute skills/teacher/SKILL.md

Execute the pathway instructions inline. The transition should be seamless.

3. If Unsure

If the user isn't sure which pathway fits:

  • "Do you already have learning targets or outcomes written?" → Yes: Teacher.
  • "Do you have existing materials — docs, code, outlines?" → Yes: Apprentice. No: Beginner.

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.