apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Create or update a skill that extends Claude's capabilities. Use when the user asks to \"create a skill\", \"make a new skill\", \"write a skill for...\", or \"update this skill\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill write-skill --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill write-skill -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill write-skill -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill write-skill -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill write-skill -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill write-skill -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill write-skill -a windsurf -y
name: write-skill description: "Create or update a skill that extends Claude's capabilities. Use when the user asks to \"create a skill\", \"make a new skill\", \"write a skill for...\", or \"update this skill\"."
This skill guides the creation of effective skills. Authoring guidance is split across the reference files below. Read the ones the current step needs rather than all of them.
| Reference | Covers | |---|---| | [references/principles.md](references/principles.md) | Conciseness, instructions-not-documentation, degrees of freedom | | [references/structure.md](references/structure.md) | Frontmatter, naming, descriptions, progressive disclosure, file layout | | [references/writing.md](references/writing.md) | Prose rules: terminology, phrasing, conditions, thresholds | | [references/workflows.md](references/workflows.md) | Step/phase structure, feedback loops, exit signals, output patterns | | [references/composition.md](references/composition.md) | Depending on, invoking, and fanning out to other skills | | [references/tools.md](references/tools.md) | Agent, Bash, AskUserQuestion, and MCP tool invocation | | [references/evaluation.md](references/evaluation.md) | Evaluations and iterating on a skill from observed behavior | | [references/scripts.md](references/scripts.md) | Skills that bundle executable code | | [references/harness.md](references/harness.md) | Harness tool names, permission modes, and discovery paths |
For conceptual background on how Skills work, see the Skills overview on platform.claude.com.
Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
For example, when building an image-editor skill, relevant questions include:
To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
Conclude this step when every function the skill should support has at least one concrete example the user supplied or confirmed.
To turn concrete examples into an effective skill, analyze each example by:
1. Considering how to execute on the example from scratch 2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly
Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:
1. Rotating a PDF requires re-writing the same code each time 2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill
Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
1. Writing a frontend webapp requires the same boilerplate HTML/React each time 2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill
Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:
1. Querying BigQuery requires re-discovering the table schemas and relationships each time 2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill
To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
When creating a new skill, establish with that list in hand whether the skill earns its existence. The contents fail that test when they compensate for a problem fixable at its source, when they serve a one-time job rather than a recurring one, or when the instruction files the harness already loads cover them. Where any of those holds, state which one and name the alternative — the upstream fix, a runbook, or a doc pointer — then use `AskUserQuestion` to let the user choose between that alternative and building the skill anyway, and continue from their answer. When updating an existing skill, apply the test to the change in hand and record any doubt about the whole skill's reason to exist beside the finished edit.
Skip this step if the skill being developed already exists and iteration is needed. In this case, continue to the next step.
When creating a new skill from scratch, create the skill directory with:
After initialization, customize or remove the generated files as needed.
When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Focus on including information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines
A human-gated agentic software factory for Claude Code and Codex: you decide what to build and judge the result; skills shape, build, polish, ship, and learn.
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…
Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…
Shared changelog conventions and formatting rules. Not typically invoked directly.
Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.