技能作家
- 作者仓库星标 739
- 作者仓库 skills
- 领域
- 文档
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @getsentry · 未声明许可证
- 上下文用量评级
- 中等消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
在选择文件所属位置之前,解析预期操作(`create`、`update`、`synthesize`、`iterate`)并检查工作区现有技术。从观察到的惯例中选择目标技能根源。如果检查后规范位置仍然不清楚,请在编辑文件之前直接询问一个问题。阅读`references/mode-selection.md` 选择所需的最少工作流程路径。阅读`references/execution-shapes.md` 选择主要执行形状。
阅读`references/synthesis-path.md`。使用这条路径来获得新技能、材料变化和研究优先的规划。收集相关来源并对其进行评分。当源材料薄弱、陈旧或不明确时,请阅读`references/source-discovery.md`。在调整上游提示、工作流程、标题、基准或文档时,请阅读`references/source-adaptation.md`。
当所选路径包含`iteration`时,先读取`references/iteration-path.md`(例如操作`iterate`)。捕获并匿名化示例并注明出处。当示例应该持续到当前回合之后时,请阅读`references/iteration-evidence.md`。根据工作切片和坚持切片检查技能行为。根据正面/负面/修正证据提出改进建议。
阅读`references/authoring-path.md`。使用命令式语气编写或更新`SKILL.md`,并提供丰富的描述。将`SKILL.md`保留为运行时路由器,而不是百科全书。在创建新的部分或文件之前,运行`references/authoring-path.md`中的预编辑精度检查。添加批量说明或新参考文件之前,请阅读`references/reference-architecture.md`。
阅读`references/description-optimization.md`。验证应该触发和不应该触发的查询集。通过有针对性的描述编辑来减少误报和漏报。保持触发语言在提供者之间通用,除非该技能是故意针对提供者的。
阅读`references/registration-validation.md`。对您在工作区中验证的活动布局应用存储库注册步骤。运行结构检查的快速验证。在完成之前进行判断,审查验证器警告、精确通过结果和覆盖范围差距。
# 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
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
12. 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`
按说明文件中的顺序排列。
核心工作流程参考
工件布局参考
工作流程机制参考
克劳德代码参考
配置文件示例
文件/命令 -> references/ · references/mode-selection.md · references/execution-shapes.md · references/design-principles.md · SPEC.md · references/reference-architecture.md · references/spec-template.md · references/source-discovery.md
内容校验值 -> d55f3f24de38
当前原文的自动摘译,尚未人工审校。
核心工作流程参考
当您需要...时打开·阅读选择创建、更新、迭代或研究优先工作的最小工作流路径·
references/mode-selection.md在决定文件之前选择最简单的适当执行形状·references/execution-shapes.md应用深度、简洁和可移植性的写作约束·references/design-principles.md决定哪些内容属于SKILL.md、references/、SPEC.md或支持文件·references/reference-architecture.md工件布局参考
当您需要时打开... · 阅读将整个技能内联为一个连贯的
SKILL.md·references/layout-inline-skill.md将可选的深入知识拆分为集中的路由参考 ·references/layout-reference-backed-skill.md添加用于确定性自动化或验证的脚本 ·references/layout-script-backed-workflow.md定义通常通过显式参数调用的技能 ·references/layout-argument-driven-skill.md工作流程机制参考
当您需要时打开... · 阅读将任务分解为固定顺序的步骤 ·
references/workflow-prompt-chaining.md对请求进行分类并将其路由到不同的下游路径 ·references/workflow-routing.md将独立工作拆分为并行单元或投票 ·references/workflow-parallel.md动态发现工作单元并协调工作人员输出 ·references/workflow-orchestrator-workers.md克劳德代码参考
当您需要时打开... · 阅读使用 Claude 特定的 frontmatter 或调用控件 ·
references/claude-frontmatter-invocation.md使用 Claude 参数字段或替换变量 ·references/claude-argument-substitutions.md构建在隔离中运行的技能context: fork·references/claude-subagent-fork.md构建使用 Claude 钩子进行确定性执行的技能 ·references/claude-hook-backed.md配置文件示例
当您需要...时打开 · 阅读查看文档密集型技能的预期深度 ·
references/example-documentation-skill.md查看工作流程技能的预期深度 ·references/example-workflow-process-skill.md查看良好的路由技能是什么样子 ·references/example-router-skill.md了解良好的子代理分叉技能是什么样子 ·references/example-subagent-fork-skill.md