Skill Creator
Install when you need to author or revise Claude Code skills with concise procedural knowledge, bundled resources, and workflow patterns that extend agent capabilities.
Overview
Skill Creator is a journey-wide agent skill that guides authoring and updating effective Claude Code skills—usable whenever a solo builder needs to package specialized workflows and knowledge before relying on ad-hoc pro
Install
npx skills add https://github.com/jezweb/claude-skills --skill skill-creatorWhat is this skill?
- Teaches core principles: concise context, challenge every line Claude may already know
- Covers specialized workflows, tool integrations, domain expertise, and bundled scripts or references
- Frames skills as modular onboarding packages that turn a general agent into a domain specialist
- Explicit compatibility note: designed for Claude Code skill packaging workflows
- Includes guidance for creating new skills and updating existing ones
- 4 capability areas skills provide: workflows, integrations, domain expertise, bundled resources
Adoption & trust: 504 installs on skills.sh; 841 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want a reusable agent capability but lack a disciplined way to structure SKILL.md content without bloating the context window.
Who is it for?
Indie builders maintaining a personal or team skill library who want Claude Code–native packages instead of one-off system prompts.
Skip if: Teams that only need a single inline instruction with no SKILL.md file, or users on agents that do not support Claude Code skill loading.
When should I use this skill?
Users want to create a new skill or update an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
What do I get? / Deliverables
You produce a concise, modular skill package with clear workflows and resources, ready to commit and list in a catalog like Prism.
- Structured SKILL.md draft
- Optional bundled scripts, references, or assets
- Concise workflow steps for the target domain
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Define which workflows deserve a dedicated skill before you commit to a full agent build.
Draft SKILL.md with workflows, references, and assets for a new integration skill.
Trim explanatory fluff so skill metadata stays small alongside other loaded skills.
Self-review a skill PR for concision and missing bundled resources before publishing.
Update an existing skill when APIs or business rules change without rewriting the whole agent.
How it compares
Use instead of pasting long domain tutorials into chat—skills are versioned packages with scoped procedural knowledge.
Common Questions / FAQ
Who is skill-creator for?
Solo and indie developers using Claude Code who author or maintain agent skills and want them discoverable in directories such as Prism.
When should I use skill-creator?
When creating a new skill or updating an existing one before implementation; during Build agent-tooling; also in Validate when scoping agent workflows, or Operate when iterating runbooks into reusable skills.
Is skill-creator safe to install?
It is editorial guidance only—review the Security Audits panel on this Prism page and inspect the skill files in the repo before trusting bundled scripts.
SKILL.md
READMESKILL.md - Skill Creator
# Skill Creator This skill provides guidance for creating effective skills. ## About Skills Skills are modular, self-contained packages that extend Claude's capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks—they transform Claude from a general-purpose agent into a specialized agent equipped with procedural knowledge that no model can fully possess. ### What Skills Provide 1. Specialized workflows - Multi-step procedures for specific domains 2. Tool integrations - Instructions for working with specific file formats or APIs 3. Domain expertise - Company-specific knowledge, schemas, business logic 4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks ## Core Principles ### Concise is Key The context window is a public good. Skills share the context window with everything else Claude needs: system prompt, conversation history, other Skills' metadata, and the actual user request. **Default assumption: Claude is already very smart.** Only add context Claude doesn't already have. Challenge each piece of information: "Does Claude really need this explanation?" and "Does this paragraph justify its token cost?" Prefer concise examples over verbose explanations. ### Set Appropriate Degrees of Freedom Match the level of specificity to the task's fragility and variability: **High freedom (text-based instructions)**: Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach. **Medium freedom (pseudocode or scripts with parameters)**: Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior. **Low freedom (specific scripts, few parameters)**: Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed. Think of Claude as exploring a path: a narrow bridge with cliffs needs specific guardrails (low freedom), while an open field allows many routes (high freedom). ### Anatomy of a Skill Every skill consists of a required SKILL.md file and optional bundled resources: ``` skill-name/ ├── SKILL.md (required) │ ├── YAML frontmatter metadata (required) │ │ ├── name: (required) │ │ ├── description: (required) │ │ └── compatibility: (optional, rarely needed) │ └── Markdown instructions (required) └── Bundled Resources (optional) ├── scripts/ - Executable code (Python/Bash/etc.) ├── references/ - Documentation intended to be loaded into context as needed └── assets/ - Files used in output (templates, icons, fonts, etc.) ``` #### SKILL.md (required) Every SKILL.md consists of: - **Frontmatter** (YAML): Contains `name` and `description` fields (required), plus optional fields like `license`, `metadata`, and `compatibility`. Only `name` and `description` are read by Claude to determine when the skill triggers, so be clear and comprehensive about what the skill is and when it should be used. The `compatibility` field is for noting environment requirements (target product, system packages, etc.) but most skills don't need it. - **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers (if at all). #### Bundled Resources (optional) ##### Scripts (`scripts/`) Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten. - **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed - **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks - **Benefits**: Token efficient, determinis