

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Still calibrating
click for more info
Not enough gems
Cost: 6 gems
1: Skills
incomplete
2: Writing Skills
incomplete
3: Skills Are Tools
incomplete
4: Skill Permissions
incomplete
5: Composable Skills
incomplete
6: Skill, Tool, or Agent?
incomplete
7: Custom Commands
incomplete
8: Dynamic Prompts
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
A "skill" is (mostly) just a reusable prompt for an agent.
Skills are simple, but they're useful enough to deserve serious attention. They sit in the sweet spot between "type the same giant prompt again" and "stuff every possible instruction into AGENTS.md forever."
The problem with typing a new hyper-detailed prompt is the fundamental problem all AI aims to solve: we're lazy af and don't like to type.
The problem with using AGENTS.md and other documentation for all your reusable prompts is that there are a lot of prompts you'll want to reuse often, but not in literally every session.
Skills are prompts that you reuse frequently, but not in every session.
A skill is a directory with a Markdown file and optional additional assets, like scripts or other resources. The agent can load the skill automatically, or you can load it manually. For example, I have a talk-to-database skill. It tells the agent how to connect to my production database safely (and in read-only mode) so that it can answer questions about the data without having to re-explain all the steps specific to my setup each time.
Add type checking to Sloperator's validation skill so the agent checks for type errors whenever you use it.
Tell OpenCode to run and submit the CLI tests from the project root.