Skip to main content
A few habits make skills sharper and keep your agent reliable.

​
Match the mode to the source

The generation mode shapes the whole result. If an API skill reads like marketing copy, you’re probably in design mode — switch to api and re-generate.

​
Point at the most specific URL

Generate from the page closest to what you need, not the homepage.

Do

docs.stripe.com/api/charges — focused and dense with the right detail.

Avoid

stripe.com — broad and shallow, mostly navigation and marketing.

​
Keep skills fresh

Sources drift. Re-generate when an API ships a new version or a library has a major release, then re-install so every agent session picks up the change. 
npx @getskillmd/cli sync

​
Commit skills to your repo

Treat skills like any other project config. Committing them means every teammate — and every CI run and agent session — shares the exact same context.

​
Prefer one skill per source

Resist the urge to staple ten pages into one file. Several focused skills beat one giant one: your agent loads only what a task needs, and each stays easy to refresh.
Name skills for what they cover, not where they came from — stripe-webhooks is easier to reach for than docs-stripe-com-3.