跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

create-skill

Create new marketing skills for the mktg playbook. Use when the agent needs to add a new capability, someone says 'create a skill', 'new skill', 'add a marketing skill', 'extend the playbook', 'I need a skill for X', 'build a skill', 'make a skill for Y', or 'add capability for Z'. Also use when someone wants to capture a marketing workflow they just did into a reusable skill, or when they say 'turn this into a skill'. Reads the skill contract, generates SKILL.md with correct frontmatter and structure, creates the directory, and reminds the agent to register in the manifest.

MoizIbnYousaf · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add MoizIbnYousaf/marketing-cli --skill create-skill

技能说明


name: create-skill description: | Create new marketing skills for the mktg playbook. Use when the agent needs to add a new capability, someone says 'create a skill', 'new skill', 'add a marketing skill', 'extend the playbook', 'I need a skill for X', 'build a skill', 'make a skill for Y', or 'add capability for Z'. Also use when someone wants to capture a marketing workflow they just did into a reusable skill, or when they say 'turn this into a skill'. Reads the skill contract, generates SKILL.md with correct frontmatter and structure, creates the directory, and reminds the agent to register in the manifest. allowed-tools: []

/create-skill — Skill Creator

Meta-skill for extending the mktg marketing playbook. You create new skills that follow the drop-in contract so they work immediately with /cmo, mktg doctor, and the full skill ecosystem.

For brand memory protocol, see /cmo rules/brand-memory.md.

On Activation

  1. Read the skill contract: workflows/create-new-skill.md
  2. Read the template: templates/marketing-skill.md
  3. Read skills-manifest.json in the project root to understand existing skills and avoid overlap.
  4. Ask: What marketing capability should this skill add?

Phase 0: Validate the Need

Gate check. Before creating a new skill, verify it doesn't already exist:

SignalAction
Capability covered by existing skillSkip. Point to the existing skill.
Slight variation of existing skillSkip. Suggest extending the existing skill instead.
Genuinely new marketing capabilityProceed.
Orchestrator chaining existing skillsProceed. Mark as orchestrator layer.

Check skills-manifest.json for the full list. Common near-misses:

  • "social media copy" → /content-atomizer already handles this
  • "brand guidelines" → /brand-voice covers this
  • "SEO strategy" → /keyword-research + /seo-audit cover this

Phase 1: Gather Requirements

Ask these questions (one at a time, stop when clear):

  1. Name — What should the skill be called? (kebab-case, e.g., webinar-funnel)
  2. Trigger phrases — What would someone say to invoke this? (5-8 natural phrases)
  3. Category — Where does it fit? (foundation / strategy / copy-content / distribution / creative / seo / conversion / growth / knowledge)
  4. Layer — What layer? (foundation / strategy / execution / orchestrator)
  5. Tier — How essential? (must-have / nice-to-have / experimental)
  6. Brand reads — Which brand/ files does it need? (voice-profile.md, audience.md, etc.)
  7. Brand writes — Which brand/ files does it update?
  8. Dependencies — Which skills should run first? (e.g., brand-voice, audience-research)
  9. Core workflow — What are the main phases? (3-5 phases typical)

Phase 2: Generate the Skill

  1. Copy the template from templates/marketing-skill.md.
  2. Fill in all frontmatter fields from Phase 1 answers.
  3. Write the skill body following this structure:
    • Title line — # /<name> — <Short Description>
    • Opening paragraph — What this skill does and why it matters (2-3 sentences)
    • Brand memory reference — Link to /cmo brand-memory rules
    • On Activation — Steps to load context and assess the request
    • Phases 1-N — The core workflow (3-5 phases)
    • Worked Example — One concrete example showing the skill in action
    • Anti-Patterns — Table of common mistakes and corrections
    • YAGNI Principles — What NOT to add
  4. Write the description field carefully — it's used for routing. Include:
    • What the skill does (first sentence)
    • When to use it (second sentence)
    • Trigger phrases (remaining text)

Phase 3: Create the Directory

skills/<name>/
├── SKILL.md              # Required — the skill itself
├── templates/            # Optional — reusable templates
├── workflows/            # Optional — step-by-step procedures
└── references/           # Optional — supporting knowledge

Only create subdirectories if the skill genuinely needs them. Most skills are a single SKILL.md.

Phase 4: Register and Validate

  1. Remind the agent (or user) to add an entry to skills-manifest.json:
    "<name>": {
      "source": "new",
      "category": "<category>",
      "layer": "<layer>",
      "tier": "<tier>",
      "reads": ["<file1>.md"],
      "writes": ["<file1>.md"],
      "depends_on": ["<skill1>"],
      "triggers": ["<phrase1>", "<phrase2>"],
      "review_interval_days": 60
    }
    
  2. Validate with mktg skill validate <name> if the CLI is available. If CLI is unavailable, manually verify:
    • Frontmatter has name, description, allowed-tools fields
    • name matches the directory name exactly
    • Description includes trigger phrases for routing
    • All referenced brand files use valid names from the standard set
    • No trigger phrases conflict with existing skills (check manifest)
  3. Test by invoking /<name> and verifying the On Activation flow works.

Do NOT modify skills-manifest.json directly in this skill — that's a separate step to avoid merge conflicts.

Handling Modification Requests

If the user wants to modify an existing skill (not create a new one):

  • "Update skill X" or "add a mode to Y" → Read the existing SKILL.md, understand its structure, make targeted edits. Do not use the creation workflow.
  • "Merge skill X into skill Y" → Read both, propose the merge, confirm, then edit the target skill.
  • Route here only for genuinely new capabilities.

Key Principles

Frontmatter Contract

Every SKILL.md must have this exact frontmatter structure:

---
name: <kebab-case-name>
description: |
  <Multi-line description. First sentence: what it does.
  Second sentence: when to use it. Remaining: trigger phrases.>
allowed-tools: []
---
  • name must match the director
阅读完整来源 ↗