skill-creator

Create reusable SKILL.md files that capture workflows and instructions for future agent sessions.

Updated May 25, 2026
One-click install
npx skills add https://github.com/dheejay282002/final_project --skill skill-creator-dheejay282002
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/dheejay282002/final_project/tree/main/.local/secondary_skills/skill-creator
Command: npx skills add https://github.com/dheejay282002/final_project --skill skill-creator-dheejay282002

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable workflows, conventions, and task-specific knowledge discovered during a conversation are lost when the session ends. This Skill guides the structured capture of that knowledge into persistent, reusable skill files that future agent instances can discover and follow. ## Core Features & Use Cases - Guided Skill Authoring: Walks through intent capture, naming, frontmatter rules, and instruction writing to produce a valid SKILL.md. - Progressive Disclosure Structure: Enforces a three-level loading model (metadata, body, bundled resources) so skills stay discoverable without bloating context. - Quality Checklist: Validates naming constraints, description triggers, and file placement before finishing. - Use Case: After debugging a tricky deployment process with an agent, ask it to turn the session into a skill so the next instance follows the same checklist automatically. ## Quick Start Turn the workflow we just completed into a reusable skill saved under .agents/skills.

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 reusable skill for an AI agent?▼

Write a SKILL.md file with YAML frontmatter containing a name and description, followed by Markdown instructions. Save it to .agents/skills/<skill-name>/SKILL.md so future agent instances can discover and load it.

What should go in a SKILL.md description field?▼

The description should state what the skill does and when it triggers, including specific phrases or scenarios. It is the primary discovery mechanism, so be explicit about trigger conditions rather than writing a vague summary.

What are the naming rules for skill directories?▼

Skill names must be lowercase letters, numbers, and hyphens only, with a maximum of 64 characters. Examples include deploy-checklist and api-conventions.

How long can a SKILL.md file be?▼

Keep SKILL.md under 500 lines. Move larger content into a references/ subdirectory and link to those files from the main body with guidance on when to read them.

Where are user-created skills stored versus platform skills?▼

User-created skills go in .agents/skills/<skill-name>/ and can be freely modified or deleted. Platform-provided skills live in .local/skills/ and are read-only.