Build your own skill

User skills live in ~/.slo/user_skills/ and shadow built-in skills of the same name. The easiest way to create one is to ask Slo to do it for you.

Ask Slo to build the skill

Just describe what you want the skill to cover:

"Create a user skill for writing GraphQL resolvers in our naming convention."

"Build me a user skill that enforces our internal API response format across all routes."

"I want a skill that always adds structured logging to every new service I write — create that for me."

Slo uses its built-in create-user-skill skill to scaffold the SKILL.md, fill in the guidance, and save it to ~/.slo/user_skills/<your-skill-name>/SKILL.md.

What Slo creates

~/.slo/user_skills/
  your-skill-name/
    SKILL.md

The SKILL.md will include:

• A frontmatter block (name, description, when_to_use, group, kind)
• Structured guidance written in your conventions
• Concrete examples drawn from your description

Overriding a built-in skill

To override a built-in, ask Slo to create a user skill with the same name as the built-in:

"Create a user skill called typescript-named-arguments-and-type-hints that uses our team's stricter rules."

Slo will override the built-in with your version from that point on.

Editing a skill later

User skills are plain markdown. Open ~/.slo/user_skills/<skill-name>/SKILL.md in any editor and update it directly. Changes take effect immediately on the next Slo session.

You can also ask Slo to revise a skill:

"Update my graphql-resolvers skill to also enforce cursor-based pagination."