skill-creator

Creates new AI agent skills following the Agent Skills SKILL.md specification.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jhannka/php-skills --skill skill-creator-jhannka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/jhannka/php-skills/tree/main/skills/skill-creator
Command: npx skills add https://github.com/jhannka/php-skills --skill skill-creator-jhannka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a new AI agent skill from scratch is error-prone: inconsistent frontmatter, missing trigger descriptions, and unclear structure make skills hard to discover and reuse. This Skill provides a standardized template, naming conventions, and a checklist so every new SKILL.md follows the Agent Skills spec. ## Core Features & Use Cases - SKILL.md Template: Provides a complete frontmatter and body template with required fields (name, description, license, metadata) and recommended sections. - Naming & Structure Conventions: Defines naming patterns for generic, project-specific, testing, and workflow skills, plus rules for when to use assets/ versus references/ directories. - Creation Checklist: Includes a pre-creation checklist covering duplication checks, frontmatter completeness, and registration in AGENTS.md. - Use Case: When you notice your team repeatedly re-explaining a project convention to an AI agent, use this Skill to author a reusable SKILL.md that captures the pattern once and registers it for discovery. ## Quick Start Ask the agent to create a new skill for your project's naming conventions using the skill-creator template and register it in AGENTS.md.

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 AI agent skill?

Create a directory under skills/ containing a SKILL.md file with YAML frontmatter defining name, description, license, and metadata, followed by a markdown body with usage rules and examples. Then register the skill in AGENTS.md so agents can discover it.

What frontmatter fields are required in a SKILL.md file?

A SKILL.md requires name (lowercase with hyphens), description (what the skill does plus a trigger condition), license, and metadata with author and version. The description should include trigger keywords so agents know when to load the skill.

When should I create a skill versus regular documentation?

Create a skill when a pattern repeats, project conventions differ from generic best practices, or workflows need step-by-step guidance. Skip it when documentation already exists, the pattern is trivial, or the task is a one-off.

What is the difference between assets and references directories in a skill?

Use assets/ for code templates, JSON schemas, and example configs that the skill provides directly. Use references/ for links to local documentation files; references should point to local paths, not web URLs.

How should I name a project-specific agent skill?

Use {project}-{component} for project-specific skills, {technology} for generic ones, {project}-test-{component} for testing skills, and {action}-{target} for workflow skills like skill-creator. Names must be lowercase with hyphens.