跳到主内容
智客 ZICQ

技能库 智客分类:设计创意 skill-forge

Skill Forge

为克洛德·克洛德·克洛德创造出高质量的生产级技能. 关于技能架构、工作流程设计、即时工程和包装的专家指导。 当用户想创造出新技能,构建出技能,设计出技能,写出技能,更新已存在的技能,提高技能,重构技能,调试技能,或打包技能时使用. 触发:"创造技能","建设技能","新技能","技能创造","写作技能","制作技能","设计技能","改进技能","包装技能","技能发展","技能模板","技能最佳做法","写作SKILL.md".

3955 安装量

官方网址:skills.sh

技能介绍

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

做什么

为克洛德·克洛德·克洛德创造高质量的生产级技能. 关于技能架构、工作流程设计、即时工程和包装的专家指导

何时用

" SKILL.MD机身中的信息. 机体在触发后加载——为时已晚

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Skill Forge、What is a Skill、Workflow、Step 1: Understand the Skill ⚠️ REQUIRED、Step 2: Plan Architecture、Step 3: Initialize ⛔ BLOCKING。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/description-guide.md、references/architecture-guide.md、scripts/init_skill.py、references/writing-techniques.md、references/workflow-patterns.md、references/parameter-system.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Create high-quality, production-grade skills for Claude Code. Expert guidance on skill architecture, workflow design, prompt engineering, and packaging. Use when user wants to create a new skill, build a skill, design a skill, write a skill, update an existing skill, improve a skill, refactor a skill, debug a skill, or package a skill. Triggers: 'create skill', 'build skill', 'new skill', 'skill creation', 'write a skill', 'make a skill', 'design a skill', 'improve skill', 'package skill', 'skill development', 'skill template', 'skill best practices', 'write SKILL.md'.

Skill ForgeWhat is a SkillWorkflowStep 1: Understand the Skill ⚠️ REQUIREDStep 2: Plan ArchitectureStep 3: Initialize ⛔ BLOCKINGStep 4: Write DescriptionStep 5: Write SKILL.md Body5.1 Set Iron Law5.2 Design Workflow Checklist5.3 Add Confirmation Gates5.4 Add Parameter System (if applicable)

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
skill-forge
description
Create high-quality, production-grade skills for Claude Code. Expert guidance on skill architecture, workflow design, prompt engineering, and packaging. Use when user wants to create a new skill, build a skill, design a skill, write a skill, update an existing skill, improve a skill, refactor a skill, debug a skill, or package a skill. Triggers: 'create skill', 'build skill', 'new skill', 'skill creation', 'write a skill', 'make a skill', 'design a skill', 'improve skill', 'package skill', 'skill development', 'skill template', 'skill best practices', 'write SKILL.md'.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 7
  • references/description-guide.md
  • references/architecture-guide.md
  • scripts/init_skill.py
  • references/writing-techniques.md
  • references/workflow-patterns.md
  • references/parameter-system.md
  • references/output-patterns.md

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

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

安装这个技能

Skills CLI ↗

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

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

交给 Agent 安装

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

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

GitHub 完整包 ↗

终端安装 · Skills CLI

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

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

npx skills add 'https://github.com/sanyuan0704/sanyuan-skills' --skill 'skill-forge'

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

阅读排版
--- name: skill-forge description: "Create high-quality, production-grade skills for Claude Code. Expert guidance on skill architecture, workflow design, prompt engineering, and packaging. Use when user wants to create a new skill, build a skill, design a skill, write a skill, update an existing skill, improve a skill, refactor a skill, debug a skill, or package a skill. Triggers: 'create skill', 'build skill', 'new skill', 'skill creation', 'write a skill', 'make a skill', 'design a skill', 'improve skill', 'package skill', 'skill development', 'skill template', 'skill best practices', 'write SKILL.md'." --- # Skill Forge IRON LAW: Every line in a skill must justify its token cost. If it doesn't make the model's output better, more consistent, or more reliable — cut it. ## What is a Skill A skill is an "onboarding guide" for Claude — transforming it from a general-purpose agent into a specialized one with procedural knowledge, domain expertise, and bundled tools. ``` skill-name/ ├── SKILL.md # Required: workflow + instructions (<500 lines) ├── scripts/ # Optional: deterministic, repeatable operations ├── references/ # Optional: loaded into context on demand └── assets/ # Optional: used in output, never loaded into context ``` **Default assumption: Claude is already very smart.** Only add what Claude doesn't already know. Challenge every paragraph: "Does this justify its token cost?" ## Workflow Copy this checklist and check off items as you complete them: ``` Skill Forge Progress: - [ ] Step 1: Understand the Skill ⚠️ REQUIRED - [ ] 1.1 Clarify purpose and concrete use cases - [ ] 1.2 Collect 3+ concrete usage examples - [ ] 1.3 Identify trigger scenarios and keywords - [ ] Step 2: Plan Architecture - [ ] 2.1 Identify reusable resources (scripts, references, assets) - [ ] 2.2 Design progressive loading strategy - [ ] 2.3 Design parameter system (if applicable) - [ ] Step 3: Initialize ⛔ BLOCKING (skip if skill already exists) - [ ] Run init_skill.py - [ ] Step 4: Write Description - [ ] Load references/description-guide.md - [ ] Apply keyword bombing technique - [ ] Step 5: Write SKILL.md Body - [ ] 5.1 Set Iron Law - [ ] 5.2 Design workflow checklist - [ ] 5.3 Add confirmation gates - [ ] 5.4 Add parameter system (if applicable) - [ ] 5.5 Apply writing techniques - [ ] 5.6 Add anti-patterns list - [ ] 5.7 Add pre-delivery checklist - [ ] Step 6: Build Resources - [ ] 6.1 Implement and test scripts - [ ] 6.2 Write reference files - [ ] 6.3 Prepare assets - [ ] Step 7: Review ⚠️ REQUIRED - [ ] Run pre-delivery checklist (Step 9) - [ ] Present summary to user for confirmation - [ ] Step 8: Package - [ ] Run package_skill.py - [ ] Step 9: Iterate based on real usage ``` ## Step 1: Understand the Skill ⚠️ REQUIRED Ask yourself: - What specific problem does this skill solve that Claude can't do well on its own? - What would a user literally type to trigger this skill? - What are 3-5 concrete usage examples with realistic inputs and expected outputs? If unclear, ask the user (don't ask everything at once — start with the most critical): - "Can you give me 3 examples of how you'd use this skill?" - "What would you literally say to trigger it?" - "What does a good output look like?" Do NOT proceed until you have at least 3 concrete examples. ## Step 2: Plan Architecture For each concrete example, ask: 1. What operations are deterministic and repeatable? → `scripts/` 2. What domain knowledge does Claude need at specific steps? → `references/` 3. What files are used in output but not in reasoning? → `assets/` Key constraints: - SKILL.md must stay under 500 lines — everything else goes to `references/` - References organized by domain, one level of nesting only - Load references/architecture-guide.md for progressive loading patterns and organization strategies ## Step 3: Initialize ⛔ BLOCKING Skip if working on an existing skill. Otherwise run: ```bash python3 scripts/init_skill.py --path ``` The script creates a template with Iron Law placeholder, workflow checklist, and proper directory structure. ## Step 4: Write Description This is the most underestimated part of a skill. The description determines: 1. Whether the skill triggers automatically 2. Whether users find it by search Load references/description-guide.md for the keyword bombing technique and good/bad examples. Key rule: NEVER put "When to Use" info in the SKILL.md body. The body loads AFTER triggering — too late. ## Step 5: Write SKILL.md Body Load reference files as needed for each sub-step: ### 5.1 Set Iron Law Ask: "What is the ONE mistake the model will most likely make with this skill?" Write a rule that prevents it. Place it at the top of SKILL.md, right after the frontmatter. → Load references/writing-techniques.md for Iron Law patterns and red flag signals. ### 5.2 Design Workflow Checklist Create a trackable checklist with: - ⚠️ REQUIRED for steps that must not be skipped - ⛔ BLOCKING for prerequisites - Sub-step nesting for complex steps - (conditional) for steps that depend on earlier choices → Load references/workflow-patterns.md for checklist patterns and examples. ### 5.3 Add Confirmation Gates Force the model to stop and ask the user before: - Destructive operations (delete, overwrite, modify) - Generative operations with significant cost - Applying changes based on analysis → Load references/workflow-patterns.md for confirmation gate patterns. ### 5.4 Add Parameter System (if applicable) If the skill benefits from flags like `--quick`, `--style`, `--regenerate N`: → Load references/parameter-system.md for $ARGUMENTS, flags, argument-hint, and partial execution patterns. ### 5.5 Apply Writing Techniques Three techniques that dramatically improve output quality: 1. **Question-style instructions**: Give questions, not vague directives 2. **Anti-pattern documentation**: List what NOT to do 3. **Iron Law + Red Flags**: Prevent the model from taking shortcuts → Load references/writing-techniques.md for all three with examples. ### 5.6 Add Anti-Patterns List Ask: "What would Claude's lazy default look like for this task?" Then explicitly forbid it. → Load references/writing-techniques.md for anti-pattern examples. ### 5.7 Add Pre-Delivery Checklist Add concrete, verifiable checks. Each item must be specific enough that the model can check it by looking at the output. Not "ensure good quality" but "no placeholder text remaining (TODO, FIXME, xxx)." → Load references/output-patterns.md for checklist patterns and priority-based output. ### Writing Principles - **Concise**: Only add what Claude doesn't already know - **Imperative form**: "Analyze the input" not "You should analyze the input" - **Match freedom to fragility**: Narrow bridge → specific guardrails; open field → many routes - High freedom (text): multiple valid approaches - Medium (pseudocode/params): preferred pattern, some variation OK - Low (specific scripts): fragile operations, consistency critical ## Step 6: Build Resources ### Scripts - Encapsulate deterministic, repeatable operations - Scripts execute without loading into context — major token savings - Test every script before packaging - In SKILL.md, document only the command and arguments, not the source code ### References - Organize by domain, not by type - One level of nesting only - Each file referenced from SKILL.md with clear "when to load" instructions - Large files (>100 lines) should have a table of contents at the top ### Assets - Templates, images, fonts used in output - Not loaded into context, just referenced by path → Load references/architecture-guide.md for detailed patterns. ## Step 7: Review ⚠️ REQUIRED Present the skill summary to the user and confirm before packaging. ### Pre-Delivery Checklist #### Structure - [ ] SKILL.md under 500 lines - [ ] Frontmatter has `name` and `description` only (plus optional `allowed-tools`, `license`, `metadata`) - [ ] Description includes trigger keywords and usage scenarios - [ ] No README.md, CHANGELOG.md, or other unnecessary files - [ ] No example/placeholder files left from initialization #### Quality - [ ] Has an Iron Law or core constraint at the top - [ ] Has a trackable workflow checklist with ⚠️/⛔ markers - [ ] Confirmation gates before destructive/generative operations - [ ] Uses question-style instructions, not vague directives - [ ] Lists anti-patterns (what NOT to do) - [ ] References loaded progressively, not all upfront #### Resources - [ ] Scripts tested and executable - [ ] References organized by domain, one level deep - [ ] Large references have table of contents - [ ] Assets used in output, not loaded into context #### Anti-Patterns to Avoid - Stuffing everything into one massive SKILL.md (>500 lines) - Vague description like "A tool for X" - No workflow — letting the model freestyle - No confirmation gates — model runs unchecked to completion - Vague instructions like "ensure good quality" instead of specific checks - Including README.md, INSTALLATION_GUIDE.md, or other documentation files - "When to Use" info in the body instead of the description field ## Step 8: Package ```bash python3 scripts/package_skill.py [output-directory] ``` Validates automatically before packaging. Fix errors and re-run. ## Step 9: Iterate After real usage: 1. Notice where the model struggles or is inconsistent 2. Identify which workflow step needs improvement 3. Add more specific instructions, examples, or anti-patterns 4. Re-test and re-package

相关技能

设计创意

Automation Workflows

设计和实施自动化工作流程,以节省时间和规模化操作作为独家. 用于识别重复任务实现自动化,构建跨工具的工作流程,设置触发器和行动,或优化现有自动化. 包括自动化机会识别,工作流程设计,工具选择(Zapier,Make,n8n),测试,和维护. 触发"自动","自动","工作流程自动…

设计创意

Ui Ux Pro Max

UI/UX设计智能及建筑抛光接口实施指导. 当用户要求UI设计,UX流量,信息架构,视觉风格方向,设计系统/托盘,组件规格,副本/显微镜,可访问性,或生成/critique/refine前端UI(HTML/CSS/JS,React,Next.js,Vue,Svelte,Tailw…

设计创意

Frontend Design

创建美丽现代UI的专家前端设计指南. 在构建起落架页面,仪表板,或任何用户界面时使用.

设计创意

N8n Workflow Automation

设计和输出 n8n 工作流程 JSON 有强力触发器, idempotency, 错误处理, 记录, 重试, 以及 人入"一站"审查队列. 当您需要可审计的自动化时使用.