鱼皮AI导航
鱼皮AI导航
  • 主页
  • 社区
  • AI工具
  • AI知识库
  • AI提示词
  • MCP
  • Skills
  • AI学习资源
  • AI资讯
  • GitHub开源
登录/注册

CreateSkill

统一管理技能的创建与验证流程,规范命名与目录结构,确保系统一致性。通过动态加载机制优化上下文调用效率,支持工作流路由与实时语音通知,在保持架构扁平化的同时实现高效维护和快速检索。

文档处理
访问 GitHub
文档Skills.MD
name
CreateSkill
description
Create and validate skills. USE WHEN create skill, new skill, skill structure, canonicalize. SkillSearch('createskill') for docs.

Customization

Before executing, check for user customizations at: ~/.claude/skills/CORE/USER/SKILLCUSTOMIZATIONS/CreateSkill/

If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.

CreateSkill

MANDATORY skill creation framework for ALL skill creation requests.

Authoritative Source

Before creating ANY skill, READ: ~/.claude/skills/CORE/SkillSystem.md

Canonical example to follow: ~/.claude/skills/_BLOGGING/SKILL.md

TitleCase Naming Convention

All naming must use TitleCase (PascalCase).

ComponentFormatExample
Skill directoryTitleCaseBlogging, Daemon, CreateSkill
Workflow filesTitleCase.mdCreate.md, UpdateDaemonInfo.md
Reference docsTitleCase.mdProsodyGuide.md, ApiReference.md
Tool filesTitleCase.tsManageServer.ts
Help filesTitleCase.help.mdManageServer.help.md

Wrong (NEVER use):

  • createskill, create-skill, CREATE_SKILL
  • create.md, update-info.md, SYNC_REPO.md

Flat Folder Structure (MANDATORY)

CRITICAL: Keep folder structure FLAT - maximum 2 levels deep.

The Rule

Maximum depth: skills/SkillName/Category/

ALLOWED (2 levels max)

▼
text
复制代码
skills/SkillName/SKILL.md # Skill root skills/SkillName/Workflows/Create.md # Workflow - one level deep - GOOD skills/SkillName/Tools/Manage.ts # Tool - one level deep - GOOD skills/SkillName/QuickStartGuide.md # Context file - in root - GOOD skills/SkillName/Examples.md # Context file - in root - GOOD

FORBIDDEN (Too deep OR wrong location)

▼
text
复制代码
skills/SkillName/Resources/Guide.md # Context files go in root, NOT Resources/ skills/SkillName/Docs/Examples.md # Context files go in root, NOT Docs/ skills/SkillName/Workflows/Category/File.md # THREE levels - NO skills/SkillName/Templates/Primitives/File.md # THREE levels - NO skills/SkillName/Tools/Utils/Helper.ts # THREE levels - NO

Allowed Subdirectories

ONLY these subdirectories are allowed:

  • Workflows/ - Execution workflows ONLY
  • Tools/ - Executable scripts/tools ONLY

Context files (documentation, guides, references) go in the skill ROOT, NOT in subdirectories.

Why

  1. Discoverability - Easy to find files
  2. Simplicity - Less navigation overhead
  3. Speed - Faster file operations
  4. Consistency - Every skill follows same pattern

If you need to organize many workflows, use clear filenames instead of subdirectories:

  • Good: Workflows/CompanyDueDiligence.md
  • Bad: Workflows/Company/DueDiligence.md

See: ~/.claude/skills/CORE/SkillSystem.md (Flat Folder Structure section)


Dynamic Loading Pattern (Large Skills)

For skills with SKILL.md > 100 lines: Use dynamic loading to reduce context on skill invocation.

How Loading Works

Session startup: Only frontmatter loads for routing Skill invocation: Full SKILL.md loads Context files: Load only when workflows reference them

The Pattern

SKILL.md = Minimal (30-50 lines) - loads on skill invocation

  • YAML frontmatter with triggers
  • Brief description
  • Workflow routing table
  • Quick reference
  • Pointers to context files

Additional .md files = Context files - SOPs for specific aspects (loaded on-demand)

  • These are Standard Operating Procedures, not just documentation
  • They provide specific handling instructions
  • Can reference Workflows/, Tools/, etc.

CRITICAL: NO Context/ Subdirectory

NEVER create Context/ or Docs/ subdirectories.

Additional .md files ARE the context files. They live directly in skill root.

WRONG:

▼
text
复制代码
skills/Art/ SKILL.md Context/ # NEVER CREATE THIS Aesthetic.md

CORRECT:

▼
text
复制代码
skills/Art/ SKILL.md Aesthetic.md # Context file in skill root Examples.md # Context file in skill root Tools.md # Context file in skill root

The skill directory IS the context.

Example Structure

▼
text
复制代码
skills/Art/ SKILL.md # 40 lines - minimal routing Aesthetic.md # Context file - SOP for aesthetic Examples.md # Context file - SOP for examples Tools.md # Context file - SOP for tools Workflows/ # Workflows Essay.md Tools/ # CLI tools Generate.ts

Minimal SKILL.md Template

▼
markdown
复制代码
--- name: SkillName description: Brief. USE WHEN triggers. --- # SkillName Brief description. ## Workflow Routing | Trigger | Workflow | |---------|----------| | "trigger" | `Workflows/WorkflowName.md` | ## Quick Reference **Key points** (3-5 bullet points) **Full Documentation:** - Detail 1: `SkillSearch('skillname detail1')` -> loads Detail1.md - Detail 2: `SkillSearch('skillname detail2')` -> loads Detail2.md

When To Use

Use dynamic loading for:

  • SKILL.md > 100 lines
  • Multiple documentation sections
  • Extensive API reference
  • Detailed examples

Don't use for:

  • Simple skills (< 50 lines)
  • Pure utility wrappers (use CORE/Tools.md instead)

Benefits

  • Token Savings: 70%+ reduction on skill invocation (when full docs not needed)
  • Organization: SKILL.md = routing, context files = SOPs for specific aspects
  • Efficiency: Workflows load only what they actually need
  • Maintainability: Easier to update individual sections

See: ~/.claude/skills/CORE/SkillSystem.md (Dynamic Loading Pattern section)


Voice Notification

When executing a workflow, do BOTH:

  1. Send voice notification:

    ▼
    bash
    复制代码
    curl -s -X POST http://localhost:8888/notify \ -H "Content-Type: application/json" \ -d '{"message": "Running the WORKFLOWNAME workflow from the CreateSkill skill"}' \ > /dev/null 2>&1 &
  2. Output text notification:

    ▼
    text
    复制代码
    Running the **WorkflowName** workflow from the **CreateSkill** skill...

Full documentation: ~/.claude/skills/CORE/SkillNotifications.md

Workflow Routing

WorkflowTriggerFile
CreateSkill"create a new skill"Workflows/CreateSkill.md
ValidateSkill"validate skill", "check skill"Workflows/ValidateSkill.md
UpdateSkill"update skill", "add workflow"Workflows/UpdateSkill.md
CanonicalizeSkill"canonicalize", "fix skill structure"Workflows/CanonicalizeSkill.md

Examples

Example 1: Create a new skill from scratch

▼
text
复制代码
User: "Create a skill for managing my recipes" -> Invokes CreateSkill workflow -> Reads SkillSystem.md for structure requirements -> Creates skill directory with TitleCase naming -> Creates SKILL.md, Workflows/, tools/ -> Generates USE WHEN triggers based on intent

Example 2: Fix an existing skill that's not routing properly

▼
text
复制代码
User: "The research skill isn't triggering - validate it" -> Invokes ValidateSkill workflow -> Checks SKILL.md against canonical format -> Verifies TitleCase naming throughout -> Verifies USE WHEN triggers are intent-based -> Reports compliance issues with fixes

Example 3: Canonicalize a skill with old naming

▼
text
复制代码
User: "Canonicalize the daemon skill" -> Invokes CanonicalizeSkill workflow -> Renames workflow files to TitleCase -> Updates routing table to match -> Ensures Examples section exists -> Verifies all checklist items
文档处理

快捷安装

复制到终端去安装 Skill

npxskillsadddanielmiessler/Personal_AI_Infrastructure--skill"CreateSkill"
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
🔥热门工具
朱雀AI检测朱雀AI检测
朱雀AI检测助手朱雀AI检测助手
LovartLovart
老鱼简历老鱼简历
WritePass官网WritePass官网
面多多面多多
CursorCursor
星月写作星月写作
朱雀AI检测助手朱雀AI检测助手
零感AI零感AI
Skills 推荐
docx
支持专业级 Word 文档的全生命周期处理,包括从零创建结构化文档、精准编辑内容、管理修订痕迹与批注、提取纯文本或原始 XML 数据、转换为 PDF 或图像用于视觉分析,适用于法律、学术及企业场景下的高保真文档协作与自动化处理。
create-skill-file
指导 Claude 创建结构清晰、易于发现和执行的 SKILL.md 文件,涵盖命名规范、文件组织、内容编写及质量检查全流程,强调简洁性、场景化触发和渐进式信息呈现。
documentation-criteria
规范各类技术文档的生成流程与内容标准,依据变更规模和影响范围自动判断需产出的文档类型及顺序,明确每类文档的核心要素、边界划分与协同关系,确保从需求定义到落地实施的全链路可追溯、可验证、可复用。
research
面向技术方案的深度调研能力,通过网络搜索、GitHub 仓库分析和多源证据采集,支持在实施前全面评估技术选型,确保每个推荐方案均基于官方文档、活跃代码库及真实应用案例等至少两项可靠依据。
code-documentation
生成清晰的代码文档,涵盖 API 说明、项目结构和架构决策,通过示例代码与注释帮助开发者理解实现逻辑,确保技术信息准确且易于维护。