agentleFS
dccooperdccooper/agentic-psychologist/.agents/skills/start-course/SKILL.md

start-course

Skill2 starsChanged 15 days agoMITView on GitHub

Begin or resume the course. Use when the learner types /start-course or says they want to start.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. midegdugarova/operating-production-agents★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Read workspace/progress.md with your file tools.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Start the course

  1. Check that you can edit files. If you can't (for example, file editing is turned off or every edit is blocked), don't start the lesson. Say once, plainly, that you need to be able to save their progress, and help them fix it using lessons/SCREEN_GUIDE.md. Then stop.
  2. Read workspace/progress.md with your file tools. Don't run terminal commands to check anything (no git status, no ls). Reading files is enough, and a command prompt this early would worry a new learner. See AGENTS.md → Running commands.
  3. If no lessons are marked complete: welcome the learner warmly in 3–4 sentences:

    • They're a new student arriving at a fictional university psychology department (see world/department.md).
    • The course teaches by doing. They'll type, click, and build things themselves, and you'll guide them.
    • Nothing here uses real patient or participant data, ever.
    • They can type /next-step, /im-stuck, or /my-progress at any time. (Typing the first few letters and pressing Tab fills in the rest.)
    • Your replies can take a minute or two. While you work, the agent panel shows Working… or what you're reading. Tell them to wait rather than refresh or resend.

    Then set the current lesson to the first lesson in lessons/0-getting-started/ and begin it by following its script.

  4. If they've already started: welcome them back in one sentence, say which lesson they're on (from progress.md), and pick up at the next unfinished checkpoint. Catch-up check: compare the completed lessons with the order in lessons/README.md. If an earlier lesson now has a script in lessons/ but isn't marked complete (it was skipped while still being written), tell them in one sentence and offer to do it now or carry on. Don't edit progress.md just to record the visit. Save the session date the next time you save anyway.
  5. For a brand-new learner, progress.md is first written in Lesson 0.1, step 1 (their name).

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.