Automated summary
Creates a new skill for AI agents using a meta-skill generator, including scripts, references, and validation.
Strengths
- Clear step-by-step structure for creation
- Automatically generates skeleton files
- Includes validation and optional packaging
Limitations
- Requires local Python script execution
- Final quality depends on manual editing of SKILL.md
- Shared context window may limit file size
Use this meta-skill when you need to create a specialized skill for an AI agent from scratch.
Avoid using it if you don't need scripts or external references, or if the skill is very simple.
Security analysis
SafeThe skill only documents a meta-process for creating new skills using predefined scripts; no destructive, exfiltrating, or obfuscated actions are present.
No concerns found
How this analysis is madeExamples
/create-skill pdf-editorCreate a new skill called api-helper that helps interact with REST APIsI want to create a new skill for my AI agent.description: "Create a new skill for AI agents using meta-skill-creator"
Create Skill: $ARGUMENTS
Create a new skill that extends AI agent capabilities with specialized knowledge, workflows, or tool integrations.
Arguments
$ARGUMENTS should be the skill name in hyphen-case (e.g., pdf-editor, api-helper, brand-guidelines).
If no arguments provided, ask the user for:
- Skill name (hyphen-case, e.g.,
my-new-skill) - Brief description of what the skill should do
Process
Step 1: Understand the Skill
Before creating, gather context:
- What functionality should this skill support?
- What are concrete examples of how it will be used?
- What would a user say that should trigger this skill?
Ask clarifying questions if the purpose is unclear.
Step 2: Plan Reusable Contents
Analyze what resources the skill needs:
- scripts/: Executable code for tasks that require deterministic reliability
- references/: Documentation loaded into context as needed (schemas, guides, patterns)
- assets/: Files used in output (templates, images, boilerplate)
Step 3: Initialize the Skill
Run the initialization script:
python meta-skill-creator/scripts/init_skill.py "$ARGUMENTS" --path ./skills
This creates:
skills/$ARGUMENTS/SKILL.md- Main skill file with templateskills/$ARGUMENTS/scripts/example.py- Example scriptskills/$ARGUMENTS/references/api_reference.md- Example referenceskills/$ARGUMENTS/assets/example_asset.txt- Example asset
Step 4: Edit the Skill
Update the generated SKILL.md:
-
Frontmatter - Complete the description:
--- name: $ARGUMENTS description: [Complete description of what skill does AND when to use it] --- -
Body - Choose appropriate structure:
- Workflow-Based: For sequential processes
- Task-Based: For tool collections
- Reference/Guidelines: For standards or specifications
- Capabilities-Based: For integrated systems
-
Resources - Add/customize scripts, references, assets as needed
-
Clean up - Delete unused example files
Step 5: Validate the Skill
Run validation:
python meta-skill-creator/scripts/quick_validate.py ./skills/$ARGUMENTS
Fix any errors before proceeding.
Step 6: Package (Optional)
If ready for distribution:
python meta-skill-creator/scripts/package_skill.py ./skills/$ARGUMENTS
Creates $ARGUMENTS.skill file (zip format).
Guidelines
Naming Conventions
- Hyphen-case only:
my-skill-name - Lowercase letters, digits, and hyphens
- Max 64 characters
- No leading/trailing hyphens or consecutive hyphens
Description Best Practices
- Include what the skill does
- Include when to use it (triggers/contexts)
- Max 1024 characters
- No angle brackets
Keep It Concise
- Context window is shared - only add what the model doesn't know
- SKILL.md body should be under 500 lines
- Use references/ for detailed documentation
Output
When complete, report:
- Skill location:
./skills/$ARGUMENTS/ - Files created
- Next steps (edit SKILL.md, add resources, validate)
Example
/create-skill pdf-editor
Creates a skill at ./skills/pdf-editor/ with:
- SKILL.md template ready for PDF manipulation workflows
- Example resource directories
- Validation passing
Reference
See meta-skill-creator/SKILL.md for complete skill creation documentation.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/meta-skill-creator-mrwakebi/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/meta-skill-creator-mrwakebi' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/meta-skill-creator-mrwakebi/download' --output '.skill-downloads/meta-skill-creator-mrwakebi/SKILL.md.part' && mv '.skill-downloads/meta-skill-creator-mrwakebi/SKILL.md.part' '.skill-downloads/meta-skill-creator-mrwakebi/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/meta-skill-creator-mrwakebi/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.