skill-creator

Create standardized Claude Code skills with SKILL.md frontmatter and structured sections.

59|4|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/lanegrid/agtrace --skill skill-creator-lanegrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/lanegrid/agtrace/tree/main/.agent/skills/skill-creator
Command: npx skills add https://github.com/lanegrid/agtrace --skill skill-creator-lanegrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized approach to creating domain-specific Claude Code skills, ensuring consistent SKILL.md entries that are easy to discover and activate.

Core Features & Use Cases

  • Structured frontmatter with name and description to satisfy discovery requirements.
  • A repeatable workflow (research → structure → write → verify) to build well-scoped skills.
  • Clear guidance for organizing knowledge about subsystems, workflows, or meta-skills.

Quick Start

Create a new directory under .agent/skills/<skill-name>, add SKILL.md with the required frontmatter and content sections, and verify that the skill is accessible via .claude/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 domain-specific skill for Claude Code?

To create a Claude Code skill, add a SKILL.md file with required frontmatter and content sections under the .agent/skills/<skill-name> directory structure. This enforces standardized frontmatter and body sections for discovery and activation.

What frontmatter is required for a Claude Code skill to be discoverable?

Discoverable Claude Code skills require frontmatter containing at least the name and description fields. This metadata ensures the skill can be found and activated through the discovery system.

What is the best way to structure documentation for new subsystems and workflows?

The best way to structure subsystem or workflow documentation is following a research-to-write workflow that enforces a structured SKILL.md body with required sections, safety checks, and explicit integration metadata.

How do I verify a newly created skill is accessible in Claude Code?

To verify skill accessibility, create the directory under .agent/skills/<skill-name>, add the SKILL.md file, and check that the skill is accessible via the .claude/skills directory.

Can I use the skill-creator meta-skill to document meta-skills themselves?

Yes, the skill-creator meta-skill applies when documenting new subsystems, workflows, or meta-skills, guiding researchers through a repeatable workflow to build well-scoped entries.

Are there limitations to the standard skill creation workflow?

The standard skill creation workflow focuses on domain-specific Claude Code skills with a consistent SKILL.md entrypoint, requiring strict frontmatter compliance and structured body sections for safety checks and integration.