writing-skills

Étoiles2

Forks1

Mis à jour6 juin 2026 à 14:31

Use when creating or editing a slipstream skill, to produce one that loads cleanly and earns its place. Covers the frontmatter contract, the trigger-shaped description, the required body sections and the verification gate, so the skill validator passes and the skill is actually useful.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

sarmakska

sarmakska/slipstream

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	writing-skills
description	Use when creating or editing a slipstream skill, to produce one that loads cleanly and earns its place. Covers the frontmatter contract, the trigger-shaped description, the required body sections and the verification gate, so the skill validator passes and the skill is actually useful.
slipstream	{"category":"context","requires":[],"tags":["meta","authoring","quality"]}

Overview

A skill is a reusable piece of judgement the agent loads when it is relevant. A weak skill is worse than none: it adds noise and trains the agent to ignore skills. This meta-skill is how to write one that loads cleanly, fires at the right moment and changes behaviour. It encodes slipstream's own contract so a new skill passes the validator on the first try.

Steps

Name it in kebab case and put SKILL.md in a directory of the same name under the right category folder. The directory name must match the name in the frontmatter.
Write the description as a trigger, not a label. Start with "Use when ..." and name the situation that should surface the skill, because that text is what the agent matches against.
Pick the category. Building categories (backend, auth, payments and the like) require a slipstream.verification gate with a real command. The memory and context categories are gateless because they are about discipline, not a deployable artifact.
Write the body with the required ## Steps and ## Verify sections, plus an optional ## Overview. Steps are small and concrete; Verify states how to prove the skill worked.
Keep requires pointing only at skills that really exist, since the loader checks every dependency.

Verify

Run npx slipstream validate and confirm the skill loads with no issues, the directory matches the name, the required sections are present and any non-gateless category carries a verification gate.

Plus depuis ce dépôt

même dépôt

dispatching-parallel-agents

sarmakska/slipstream

Use when several pieces of work are genuinely independent and can run at once, to fan them out across parallel agents instead of doing them in sequence. Cuts wall-clock time and keeps each strand in its own clean context.

2026-06-172

executing-plans

sarmakska/slipstream

Use when a written plan exists and you are about to build it in the current session, to work it task by task with a checkpoint after each. Keeps execution honest against the plan instead of drifting into a freehand build.

2026-06-172

using-git-worktrees

sarmakska/slipstream

Use when work needs its own isolated checkout — parallel strands that would fight over files, or a risky change you want quarantined from the main tree. Gives each strand a real working directory on its own branch without re-cloning.

2026-06-172

using-slipstream

sarmakska/slipstream

Use whenever the user says "use slipstream", "use superpowers", or starts any task in a project that has slipstream. A hard, always-on discipline that forces scoped reads over whole-file reads to save tokens, recalls memory before acting, and records what is durable every turn so memory grows constantly.

2026-06-062

frontend-design-system

sarmakska/slipstream

Use when a site needs to look designed rather than defaulted, before building sections: establish a cohesive design system of type scale, spacing, colour, radius and shadow tokens so every component shares one premium visual language.

2026-06-062

frontend-hero-section

sarmakska/slipstream

Use when building the top of a landing page, to produce a high-impact hero with confident display type, a clear single call to action and balanced composition, the kind of opening a polished marketing site leads with.

2026-06-062

name	writing-skills
description	Use when creating or editing a slipstream skill, to produce one that loads cleanly and earns its place. Covers the frontmatter contract, the trigger-shaped description, the required body sections and the verification gate, so the skill validator passes and the skill is actually useful.
slipstream	{"category":"context","requires":[],"tags":["meta","authoring","quality"]}

Overview

Steps

Name it in kebab case and put SKILL.md in a directory of the same name under the right category folder. The directory name must match the name in the frontmatter.
Write the description as a trigger, not a label. Start with "Use when ..." and name the situation that should surface the skill, because that text is what the agent matches against.
Pick the category. Building categories (backend, auth, payments and the like) require a slipstream.verification gate with a real command. The memory and context categories are gateless because they are about discipline, not a deployable artifact.
Write the body with the required ## Steps and ## Verify sections, plus an optional ## Overview. Steps are small and concrete; Verify states how to prove the skill worked.
Keep requires pointing only at skills that really exist, since the loader checks every dependency.

Verify

Run npx slipstream validate and confirm the skill loads with no issues, the directory matches the name, the required sections are present and any non-gateless category carries a verification gate.