跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 skill-writer

Skill Writer

按照代理技能规范创建,合成,并迭代地提高代理技能. 被请求时使用"创造出技能","写出技能","将各种来源合成成技能","从正/负等例子中改进出技能","更新技能",或"保持技能docs和注册". 处理源捕取,精准传出,作者,注册,验证.

1962 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

按照代理技能规范创建、合成和迭代提高代理技能

何时用

要求"创造出技能","写出技能","将来源合成成技能","从正/负等例子改进出技能","更新技能",或"保持技能的docs和注册". 处理源捕获、精密通行证、编写、登记和验证

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Skill Writer、Core Workflow References、Artifact Layout References、Workflow Mechanic References、Claude Code References、Example Profiles。 其中含规范建议的小节:分步指令、输入输出示例。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/mode-selection.md、references/execution-shapes.md、references/design-principles.md、references/reference-architecture.md、references/spec-template.md、references/source-discovery.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

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.

Skill WriterCore Workflow ReferencesArtifact Layout ReferencesWorkflow Mechanic ReferencesClaude Code ReferencesExample ProfilesStep 1: Resolve target, path, and shapeStep 2: Run synthesis when neededStep 3: Run iteration first when improving from outcomes/examplesStep 4: Author or update skill artifactsStep 5: Optimize description qualityStep 6: Register and validate

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
skill-writer
description
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.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 12
  • references/mode-selection.md
  • references/execution-shapes.md
  • references/design-principles.md
  • references/reference-architecture.md
  • references/spec-template.md
  • references/source-discovery.md
  • references/source-adaptation.md
  • references/synthesis-path.md
  • references/authoring-path.md
  • references/description-optimization.md
  • references/iteration-path.md
  • references/iteration-evidence.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「skill-writer」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-626731a95451fbf1-%E6%8A%80%E8%83%BD%E4%BD%9C%E5%AE%B6.html
请存为 .cursor/skills/skill-writer/SKILL.md 或 .claude/skills/skill-writer/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/getsentry/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/getsentry/skills' --list

npx skills add 'https://github.com/getsentry/skills' --skill 'skill-writer'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: skill-writer description: 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.

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 | | add or update evals for a skill's generated outputs or runtime behavior | references/skill-evals.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

  1. Resolve the intended operation (create, update, synthesize, iterate) and inspect workspace prior art before choosing where files belong.
  2. Choose the target skill root from observed conventions. If the canonical location is still unclear after inspection, ask one direct question before editing files.
  3. Read references/mode-selection.md to choose the minimum required workflow paths.
  4. Read references/execution-shapes.md to choose the primary execution shape.
  5. Default to the simplest adequate shape. If selecting a more complex shape, record why simpler shapes were rejected.
  6. Load only the exact artifact-layout, workflow-mechanic, and provider-specific leaf files required by that shape.
  7. Before adding guidance, identify what existing rule, section, or file should be narrowed, replaced, or removed.
  8. Record portability implications before using provider-specific mechanics.

Step 2: Run synthesis when needed

Read references/synthesis-path.md.

  1. Use this path for new skills, material changes, and research-first planning.
  2. Collect and score relevant sources with provenance.
  3. Read references/source-discovery.md when source material is thin, stale, or ambiguous.
  4. Read references/source-adaptation.md when adapting an upstream prompt, workflow, rubric, benchmark, or docs.
  5. Produce source-backed decisions and coverage/gap status, including the class and execution-shape choice.
  6. Load example profiles only when they add concrete depth for the selected class or shape.
  7. If the skill uses provider-specific mechanics, include current official provider docs and capture usage constraints.
  8. 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).

  1. Capture and anonymize examples with provenance.
  2. Read references/iteration-evidence.md when examples should persist beyond the current turn.
  3. Review skill behavior against working and holdout slices.
  4. Propose improvements from positive/negative/fix evidence.
  5. 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.

  1. Write or update SKILL.md in imperative voice with trigger-rich description.
  2. Keep SKILL.md as the runtime router, not an encyclopedia.
  3. Run the pre-edit precision check in references/authoring-path.md before creating new sections or files.
  4. Read references/reference-architecture.md before adding bulk instructions or new reference files.
  5. Create or update SPEC.md using references/spec-template.md when creating a new skill or materially changing its contract.
  6. 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.
  7. If you add a bundled reference file, add a direct routing entry for it in this SKILL.md.
  8. Prefer checklists, tables, templates, and input/output examples over explanatory prose.
  9. Follow only the specific artifact-layout, workflow-mechanic, Claude-specific, and output-contract references selected for this skill.
  10. For advanced execution shapes, add the required routing, delegation, or safety contracts before considering the skill complete.
  11. For authoring/generator skills, include transformed examples in references:
  • happy-path
  • secure/robust variant
  • anti-pattern + corrected version
  1. Read references/skill-evals.md when the request asks for evals, regression cases, benchmark cases, or model-graded quality checks for the skill being authored.
  2. After any skill artifact changes, run the post-change precision pass in references/authoring-path.md before description optimization or validation.

Step 5: Optimize description quality

Read references/description-optimization.md.

  1. Validate should-trigger and should-not-trigger query sets.
  2. Reduce false positives and false negatives with targeted description edits.
  3. Keep trigger language generic across providers unless the skill is intentionally provider-specific.

Step 6: Register and validate

Read references/registration-validation.md.

  1. Apply repository registration steps for the active layout you verified in the workspace.
  2. Run quick validation for structural checks.
  3. Review validator warnings, precision-pass results, and coverage gaps with judgment before completion.

Output format

Return:

  1. Summary
  2. Changes Made
  3. Validation Results
  4. Open Gaps

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…