skill-writer
- Repo stars 739
- Author updated Live
- Author repo skills
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @getsentry · no license declared
- Token usage
- Moderate
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-writer
description: Create, synthesize, and iteratively improve agent skills following the Agent Skills specificatio…
category: documentation
runtime: no special runtime
---
# skill-writer output preview
## PART A: Task fit
- Use case: Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, precision passes, authoring, registration, and validation..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Core Workflow References / Artifact Layout References / Workflow Mechanic References” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, precision passes, authoring, registration, and validation.”.
- **02** When the source has headings, the agent prioritizes “Core Workflow References / Artifact Layout References / Workflow Mechanic References” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Core Workflow References / Artifact Layout References / Workflow Mechanic References”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-writer
description: Create, synthesize, and iteratively improve agent skills following the Agent Skills specificatio…
category: documentation
source: getsentry/skills
---
# skill-writer
## When to use
- Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Core Workflow References / Artifact Layout References / Workflow Mechanic References” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-writer" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Core Workflow References / Artifact Layout References / Workflow Mechanic References
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Skill Writer
Use this as the single canonical workflow for skill creation and improvement. Primary success condition: maximize high-value input coverage before authoring while minimizing wasted runtime tokens.
Follow the workflow steps in order. Load only the reference files required for the step you are on.
SKILL.md is the primary router: every bundled reference file should be flat under references/ and listed here with a direct "open when..." reason.
Core Workflow References
| Open when you need to... | Read |
|---|---|
| choose the minimum workflow path for create, update, iterate, or research-first work | references/mode-selection.md |
| choose the simplest adequate execution shape before deciding files | references/execution-shapes.md |
| apply writing constraints for depth, concision, and portability | references/design-principles.md |
decide what belongs in SKILL.md, references/, SPEC.md, or supporting files |
references/reference-architecture.md |
| create or update the maintenance contract for a skill | references/spec-template.md |
| find missing high-signal sources, including history and regressions | references/source-discovery.md |
| adapt an upstream prompt, workflow, rubric, benchmark, or docs into a skill | references/source-adaptation.md |
| run the full synthesis pass with coverage checks and source capture | references/synthesis-path.md |
author or update SKILL.md, SPEC.md, and supporting files |
references/authoring-path.md |
| improve trigger language and false-positive/false-negative behavior | references/description-optimization.md |
| iterate from positive, negative, or fix examples | references/iteration-path.md |
| store persistent working and holdout examples for future revisions | references/iteration-evidence.md |
| choose a response template, schema, or output contract | references/output-contracts.md |
| troubleshoot overloaded layouts, hidden refs, or other structure failures | references/structure-troubleshooting.md |
| register the skill and run final validation checks | references/registration-validation.md |
Artifact Layout References
| Open when you need to... | Read |
|---|---|
keep the whole skill inline in one coherent SKILL.md |
references/layout-inline-skill.md |
| split optional deep knowledge into focused routed references | references/layout-reference-backed-skill.md |
| add scripts for deterministic automation or validation | references/layout-script-backed-workflow.md |
| define a skill that is usually invoked with explicit arguments | references/layout-argument-driven-skill.md |
| ship reusable templates, schemas, or other static assets | references/layout-asset-template-skill.md |
Workflow Mechanic References
| Open when you need to... | Read |
|---|---|
| break a task into fixed ordered steps | references/workflow-prompt-chaining.md |
| classify requests and route them to different downstream paths | references/workflow-routing.md |
| split independent work into parallel units or votes | references/workflow-parallel.md |
| discover work units dynamically and coordinate worker outputs | references/workflow-orchestrator-workers.md |
| run validate-fix-repeat checks during authoring or execution | references/workflow-validation-loops.md |
| validate a plan before executing a risky action | references/workflow-plan-validate-execute.md |
Claude Code References
| Open when you need to... | Read |
|---|---|
| use Claude-specific frontmatter or invocation controls | references/claude-frontmatter-invocation.md |
| use Claude argument fields or substitution variables | references/claude-argument-substitutions.md |
build a skill that runs in isolated context: fork |
references/claude-subagent-fork.md |
| build a skill that uses Claude hooks for deterministic enforcement | references/claude-hook-backed.md |
| use Claude shell preprocessing for dynamic context injection | references/claude-dynamic-context.md |
Example Profiles
| Open when you need to... | Read |
|---|---|
| see the expected depth for a documentation-heavy skill | references/example-documentation-skill.md |
| see the expected depth for a workflow-process skill | references/example-workflow-process-skill.md |
| see what a good routed skill looks like | references/example-router-skill.md |
| see what a good subagent-fork skill looks like | references/example-subagent-fork-skill.md |
| see what a good hook-backed skill looks like | references/example-hook-backed-skill.md |
Step 1: Resolve target, path, and shape
- Resolve the intended operation (
create,update,synthesize,iterate) and inspect workspace prior art before choosing where files belong. - Choose the target skill root from observed conventions. If the canonical location is still unclear after inspection, ask one direct question before editing files.
- Read
references/mode-selection.mdto choose the minimum required workflow paths. - Read
references/execution-shapes.mdto choose the primary execution shape. - Default to the simplest adequate shape. If selecting a more complex shape, record why simpler shapes were rejected.
- Load only the exact artifact-layout, workflow-mechanic, and provider-specific leaf files required by that shape.
- Before adding guidance, identify what existing rule, section, or file should be narrowed, replaced, or removed.
- Record portability implications before using provider-specific mechanics.
Step 2: Run synthesis when needed
Read references/synthesis-path.md.
- Use this path for new skills, material changes, and research-first planning.
- Collect and score relevant sources with provenance.
- Read
references/source-discovery.mdwhen source material is thin, stale, or ambiguous. - Read
references/source-adaptation.mdwhen adapting an upstream prompt, workflow, rubric, benchmark, or docs. - Produce source-backed decisions and coverage/gap status, including the class and execution-shape choice.
- Load example profiles only when they add concrete depth for the selected class or shape.
- If the skill uses provider-specific mechanics, include current official provider docs and capture usage constraints.
- Do not move to authoring until required coverage is understood or gaps are explicit.
Step 3: Run iteration first when improving from outcomes/examples
Read references/iteration-path.md first when selected path includes iteration (for example operation iterate).
- Capture and anonymize examples with provenance.
- Read
references/iteration-evidence.mdwhen examples should persist beyond the current turn. - Review skill behavior against working and holdout slices.
- Propose improvements from positive/negative/fix evidence.
- Carry concrete behavior deltas into authoring.
Skip this step when selected path does not include iteration.
Step 4: Author or update skill artifacts
Read references/authoring-path.md.
- Write or update
SKILL.mdin imperative voice with trigger-rich description. - Keep
SKILL.mdas the runtime router, not an encyclopedia. - Run the pre-edit precision check in
references/authoring-path.mdbefore creating new sections or files. - Read
references/reference-architecture.mdbefore adding bulk instructions or new reference files. - Create or update
SPEC.mdusingreferences/spec-template.mdwhen creating a new skill or materially changing its contract. - Create focused reference files, scripts, and assets only when each one has a clear "open when..." reason and cannot be handled by tightening an existing file.
- If you add a bundled reference file, add a direct routing entry for it in this
SKILL.md. - Prefer checklists, tables, templates, and input/output examples over explanatory prose.
- Follow only the specific artifact-layout, workflow-mechanic, Claude-specific, and output-contract references selected for this skill.
- For advanced execution shapes, add the required routing, delegation, or safety contracts before considering the skill complete.
- For authoring/generator skills, include transformed examples in references:
- happy-path
- secure/robust variant
- anti-pattern + corrected version
- After any skill artifact changes, run the post-change precision pass in
references/authoring-path.mdbefore description optimization or validation.
Step 5: Optimize description quality
Read references/description-optimization.md.
- Validate should-trigger and should-not-trigger query sets.
- Reduce false positives and false negatives with targeted description edits.
- Keep trigger language generic across providers unless the skill is intentionally provider-specific.
Step 6: Register and validate
Read references/registration-validation.md.
- Apply repository registration steps for the active layout you verified in the workspace.
- Run quick validation for structural checks.
- Review validator warnings, precision-pass results, and coverage gaps with judgment before completion.
Output format
Return:
SummaryChanges MadeValidation ResultsOpen Gaps
Decide Fit First
Design Intent
How To Use It
Boundaries And Review