Skills

#What Skills does

Technique packs — SEO, performance, accessibility, content — that attach to projects and are injected verbatim into every AI build.

• Instructions the AI must follow. Each skill carries instructions that are injected into the Build AI's system prompt whenever the skill is attached to the project — not a suggestion, a standing order.
• Template files included. Skills can carry starter files — an llms.txt, a robots.txt, a sitemap generator — that the AI works from instead of inventing its own.
• Two libraries. The sSystm Library ships curated, platform-maintained skills (technical SEO, AEO, Core Web Vitals, accessibility). My Library is yours — your agency's own standards, versioned as skills.
• Attach per project. Skills bind to projects, so a content site gets the SEO pack while an internal tool gets the accessibility pack — automatically, on every build.
• Readable and writable over MCP. Your external AI reads skills via sstm://skills and can create new ones with sstm_skill_create — turning a good conversation into a permanent standard.

#On the MCP surface

Skills are how you teach every AI — built-in and MCP-connected — your way of working. Your AI reads them over sstm://skills, attaches them with sstm_project_skill_attach, and creates new ones with sstm_skill_create.

Tools (write):

• sstm_skill_create
• sstm_project_skill_attach

Resources (read):

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

Full definitions live in the MCP reference.