| name | ai-agent-skills-course |
| description | Guide learners through this AI Agent Skills course repo. Use when the user asks what the course is, how to get started, which lesson to open next, how to do an exercise, where solutions live, or how course demo skills like Pokémon, SVGL, sentence clarity, course lesson editor, bad variants, and create-skill-reference fit together. |
AI Agent Skills Course
Use this skill to help someone move through the course.
Course Map
- Start with
course/README.md for the section list.
- For "what is this course?", read
README.md and course/README.md.
- For "how do I get started?", read
course/00-setup/01-lesson.md first, then course/00-setup/02-exercise.md if the learner wants hands-on steps.
- For "what is a skill?", read
course/02-inspect-a-skill/01-lesson.md.
- For "evaluate external skills", read
course/03-learn-from-existing-skills/01-lesson.md.
- For "should this be a skill?", read
course/04-decide-what-should-be-a-skill/01-lesson.md.
- For "build my first skill", read
course/05-build-a-tiny-skill/01-lesson.md.
- For "make a reusable skill", read
course/06-make-it-reusable/01-lesson.md.
- For "maintain a skills repo", read
course/07-maintain-a-skills-repo/01-lesson.md.
- For "what next after the course?", read
course/08-next-steps/01-lesson.md (lesson only; no exercise yet).
- In each lesson folder, use files in order:
01-lesson.md02-exercise.md03-solution.md
- Treat lesson frontmatter (
title, time, outcome) as the quick orientation.
Workflow
- Identify where the learner is in the course.
- Open only the relevant lesson, exercise, or solution file.
- Keep explanations tied to the current demo or problem. The course rule is: show the problem before explaining the concept.
- When a learner asks for hands-on work, point them to the matching
02-exercise.md before revealing 03-solution.md.
- Do not reveal
03-solution.md unless the learner asks for the solution, asks to check their work, or is blocked.
- When a learner asks how a course example works, inspect the relevant skill instead of summarizing from memory.
- Validate repo skill changes with
npm run check:skills.
Important Paths
- Course outline:
course/README.md
- Setup:
course/00-setup/
- First demo skill:
skills/pokemon-api/
- Tiny build example (bundled reference):
skills/sentence-clarity/
- Tiny build exercise path (learner copy):
.agents/skills/sentence-clarity/
- Reusable build example:
skills/svgl/
- Course skill-writing reference:
skills/create-skill-reference/
- Course lesson editing reference:
skills/course-lesson-editor/
- Inspection variants:
course/02-inspect-a-skill/exercises/
- Maintain skills repo:
course/07-maintain-a-skills-repo/
- Next steps:
course/08-next-steps/
Guidance
- Keep advice practical and course-shaped: use, inspect, modify, build tiny, build reusable, maintain.
- Do not treat assets as final. Prefer course files over asset assumptions; if assets are missing or still being edited, describe them as planned or in progress.
- Preserve relative paths when pointing to files so learners can open them from the repo.
- Prefer short next steps over broad theory.
