Skills

Packaged expertise — technique packs the Build AI must follow.

#What Skills does

A skill is packaged expertise: written instructions, plus optional template files, that get injected into the Build AI’s system prompt. Attach a skill to a project and the AI doesn’t just know your brand — it follows proven technique.

Skills are organised by category: SEO, AEO (answer-engine optimisation), Performance, Accessibility, Content and Other. The curated library covers techniques like llms.txt and robots.txt starters, technical SEO, XML sitemaps and Core Web Vitals.

#Two libraries, like Components

  • sSystm Library — curated technique packs maintained by the platform, read-only and available to every workspace.
  • My Library — your organisation’s own skills: your agency’s playbook, written once, applied to every build.

Skills can carry template files (path + content pairs) — starters the AI works from rather than inventing structure.

#Attach a skill to a build

  1. Open Skills and browse the library, or create your own skill with instructions and optional template files.
  2. In Build, open the project’s context panel and tick the skills the project must follow.
  3. From then on, every generation includes the attached skills’ instructions and files — always, not just when the AI remembers to look.

#On the MCP surface

Your own AI can build and apply skills too — a review finding on Claude’s side can become a reusable skill in your library:

Tools (write):

  • sstm_skill_create
  • sstm_project_skill_attach

Resources (read):

  • sstm://skills
  • sstm://skill/{id}

Full definitions live in the MCP reference.