playbooks

home / skills / zpankz / mcp-skillset / createskill

CreateSkill skill

/CreateSkill

This skill helps create and validate new skills by enforcing structure, naming, and workflow references for consistent skill packs.

This is most likely a fork of the createskill skill from danielmiessler
npx playbooks add skill zpankz/mcp-skillset --skill createskill

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.7 KB
---
name: CreateSkill
description: Create and validate skills. USE WHEN create skill, new skill, skill structure, canonicalize. SkillSearch('createskill') for docs.
---

# CreateSkill

MANDATORY skill creation framework for ALL skill creation requests.

## Authoritative Source

**Before creating ANY skill, READ:** `$PAI_DIR/skills/CORE/SkillSystem.md`

This document contains the complete specification for:
- Skill directory structure
- SKILL.md format and required sections
- Workflow file conventions
- Naming conventions (TitleCase)
- Examples section requirements

## How to Create a Skill

1. **Read the spec:** `$PAI_DIR/skills/CORE/SkillSystem.md`
2. **Create directory:** `$PAI_DIR/skills/SkillName/`
3. **Create SKILL.md** with required frontmatter and sections
4. **Add Workflows/** directory if needed
5. **Validate** by checking all workflow references resolve

## How to Validate a Skill

Run the pack validator:
```bash
bun run $PAI_DIR/Tools/validate-pack.ts
```

Or manually check:
- SKILL.md exists with valid frontmatter
- All `Workflows/*.md` references in SKILL.md exist
- Examples section is present

## How to Canonicalize a Skill

1. Rename files/directories to TitleCase
2. Ensure SKILL.md has required sections
3. Verify workflow references resolve
4. Add Examples section if missing

## Examples

**Example 1: Create a new skill**
```
User: "Create a skill for managing my recipes"
→ Read SkillSystem.md for structure
→ Create $PAI_DIR/skills/Recipes/SKILL.md
→ Use TitleCase naming throughout
```

**Example 2: Fix an existing skill**
```
User: "Canonicalize the daemon skill"
→ Rename files to TitleCase
→ Ensure Examples section exists
→ Validate workflow references
```

Overview

This skill provides a mandatory framework for creating, validating, and canonicalizing new skills. It standardizes folder layout, manifest content, workflow conventions, and naming so new skills are consistent and immediately usable. Follow the core skill system spec before starting any new skill work.

How this skill works

It guides you through reading the core skill system spec, creating a skill folder with a skill manifest and optional workflow files, and validating references. Validation can be done with an automated pack validator or by manually checking that the manifest exists, required sections are present, and all referenced workflow files resolve. Canonicalization enforces TitleCase naming, required sections, and example coverage.

When to use it

  • Creating a new skill from scratch
  • Adding or updating workflows for an existing skill
  • Fixing naming or structure inconsistencies
  • Preparing a skill for publication or inclusion in the pack
  • Canonicalizing example and metadata sections

Best practices

  • Always read the core skill system spec before starting
  • Use TitleCase for directories and filenames to avoid naming conflicts
  • Include a clear manifest with required metadata and examples section
  • Keep Workflows/ files organized and reference them from the manifest
  • Run the automated pack validator before submitting changes

Example use cases

  • Create a new Recipes skill with a manifest, workflows, and examples
  • Validate a recently added skill to ensure workflow links resolve
  • Rename and normalize an existing daemon skill to TitleCase and add missing examples
  • Add a Workflows/ directory and update the skill manifest to reference new flows
  • Run the validator to catch missing sections or broken references before publishing

FAQ

How do I validate a skill automatically?

Run the pack validator tool provided in the toolchain to check manifest presence, workflow references, and required sections.

What naming convention should I use?

Use TitleCase for skill directories and filenames to ensure consistency across the pack.

What if a workflow reference is broken?

Fix the reference by creating or renaming the target workflow file to match the manifest entry, then re-run validation.