skill-creator

Guides creation and packaging of Agent skill units with SKILL.md frontmatter.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/werlang/event-hub --skill skill-creator-werlang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/werlang/event-hub/tree/main/.agents/skills/skill-creator
Command: npx skills add https://github.com/werlang/event-hub --skill skill-creator-werlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a well-structured Agent skill requires knowing the SKILL.md format, frontmatter rules, progressive disclosure patterns, and packaging steps, which are easy to get wrong without guidance. ## Core Features & Use Cases - Skill Authoring Guidance: Provides principles for writing concise SKILL.md files with proper name and description frontmatter. - Resource Planning: Explains when to bundle scripts, references, and assets and how to structure them for progressive disclosure. - Packaging Workflow: Covers initializing skills with init_skill.py and validating plus packaging them with package_skill.py into distributable .skill files. - Use Case: When you want to build a new skill for a domain like PDF editing or brand guidelines, follow this guide to plan resources, write the SKILL.md, and package the result. ## Quick Start Ask the agent to create a new skill for your chosen domain and follow the guided steps to initialize, edit, and package it.

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 Agent skill from scratch?▼

Run the init_skill.py script with a skill name and output path to generate a template directory containing SKILL.md and example scripts, references, and assets folders. Then customize the frontmatter and body, and delete unneeded example files.

What should go in the SKILL.md frontmatter?▼

Include only the name and description fields. The description is the primary triggering mechanism, so state both what the skill does and when it should be used, since only these fields are read for discovery.

When should I add scripts, references, or assets to a skill?▼

Add scripts for deterministic or repeatedly rewritten code, references for documentation loaded on demand like schemas or policies, and assets for files used in outputs such as templates or fonts. Most skills do not need all three.

How do I package a skill into a .skill file?▼

Run package_skill.py with the path to your skill folder. The script validates frontmatter, naming, and structure first, then creates a .skill file, which is a zip archive, if validation passes.

How long should a SKILL.md body be?▼

Keep the body under 500 lines and focused on essential procedural instructions. Move detailed reference material, schemas, and examples into references files linked from SKILL.md to avoid context bloat.