skill-creator

Create, edit, audit, and package AgentSkills with SKILL.md frontmatter and bundled resources.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/guizonatto/myopen-claw --skill skill-creator-guizonatto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/guizonatto/myopen-claw/tree/main/.claude/skills/skill-creator
Command: npx skills add https://github.com/guizonatto/myopen-claw --skill skill-creator-guizonatto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Writing effective AgentSkills requires knowing the SKILL.md spec, frontmatter rules, progressive disclosure patterns, and packaging conventions—this Skill encodes that procedural knowledge so new or existing skills are created and improved consistently. ## Core Features & Use Cases - Skill Authoring Workflow: Guides a six-step process from understanding use cases through initialization, editing, and packaging. - Spec & Structure Guidance: Enforces frontmatter rules (name, description), naming conventions, and the scripts/references/assets resource model. - Audit & Improvement: Reviews existing skills for context bloat, stale content, and spec compliance, then restructures them. - Use Case: Ask the agent to create a new 'pdf-editor' skill; it initializes the directory with init_skill.py, drafts the SKILL.md, adds reusable scripts, and packages it into a distributable .skill file. ## Quick Start Ask the agent to create a new skill for a task you repeat often, or to review and tidy up an existing skill directory.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new AgentSkill from scratch?

Run the init_skill.py script with a skill name and output path to scaffold the directory, then edit the generated SKILL.md frontmatter and body, add any needed scripts or references, and package it with package_skill.py.

What must a SKILL.md file contain to be valid?

A valid SKILL.md requires YAML frontmatter with exactly two fields: name and description, followed by a Markdown body with usage instructions. The description drives triggering, so it must state what the skill does and when to use it.

When should I use scripts, references, or assets in a skill?

Use scripts for deterministic, repeatedly rewritten code; references for documentation loaded into context only when needed; and assets for files used in outputs like templates or fonts. Only create directories that are actually required.

How long should a SKILL.md body be?

Keep the body under 500 lines and under 5k words, moving detailed material into reference files linked from SKILL.md. This follows the progressive disclosure principle to minimize context window usage.

Why does skill packaging fail during validation?

Packaging fails when frontmatter is malformed, naming conventions are violated, the description is incomplete, or symlinks exist in the skill directory. Fix the reported validation errors and rerun package_skill.py.