creating-skills

Create reusable SKILL.md definitions with standardized frontmatter and documentation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BPSAI/paircoder --skill creating-skills-bpsai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-skills
Source: https://github.com/BPSAI/paircoder/tree/main/tools/cli/bpsai_pair/data/cookiecutter-paircoder/{{cookiecutter.project_slug}}/.claude/skills/creating-skills
Command: npx skills add https://github.com/BPSAI/paircoder --skill creating-skills-bpsai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams formalize repeated tasks into reusable Claude Skill definitions, reducing duplication and human error when workflows are repeated across projects.

Core Features & Use Cases

  • Template-driven: Provides a consistent SKILL.md structure for creating new skills.
  • Documentation discipline: Encourages standardized frontmatter and markdown bodies.
  • Onboarding acceleration: Enables quick scaffolding for new skills to speed up adoption.

Quick Start

Create a new directory under .claude/skills/{skill-name}, add SKILL.md using the template, and validate with the Skill validator.

Frequently Asked Questions about creating-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize repeated workflows into reusable skill definitions?

Standardize workflows by creating reusable skill definitions in SKILL.md format with structured frontmatter (name and description only), hyphenated gerund naming, and step-by-step documentation. This enforces consistent process documentation and enables repeatable deployment across teams.

What should I include in a SKILL.md file?

SKILL.md requires frontmatter with name and description (under 1024 characters), followed by steps, commands, and examples. Keep the total file under 500 lines, use hyphenated gerund naming for the skill name, and structure content to document the complete workflow.

How can I reduce duplication when the same task repeats across projects?

Formalize repeated tasks into reusable Claude Skill definitions stored in .claude/skills/{skill-name}. This reduces human error, accelerates onboarding, and ensures consistent execution when workflows are applied across multiple projects.

What naming convention should I follow for new skills?

Use hyphenated gerund naming for skill names—verb forms with hyphens separating words, such as creating-skills or parsing-data. This standardizes naming across the skill repository and improves discoverability.

Can I use a template to scaffold new skills quickly?

Yes. Create a new directory under .claude/skills/{skill-name}, populate it with SKILL.md using the standardized template structure, and validate it with the Skill validator to ensure compliance and enable rapid skill adoption.

What are the size limits for skill documentation?

Keep SKILL.md under 500 lines total, and the description field under 1024 characters. These constraints ensure skills remain focused, maintainable, and aligned with documentation discipline standards.

Related Skills