template-skill

Initialize reusable Claude skill units from SKILL.md frontmatter.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/stevessr/dotsfiles --skill template-skill-stevessr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-skill
Source: https://github.com/stevessr/dotsfiles/tree/main/dot_claude/private_plugins/private_marketplaces/anthropic-agent-skills/template
Command: npx skills add https://github.com/stevessr/dotsfiles --skill template-skill-stevessr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a ready-to-use starting point for creating new Claude skills, ensuring consistent discovery metadata and activation instructions.

Core Features & Use Cases

  • Standardized SKILL.md frontmatter required fields (name, description).
  • Optional resource directories (scripts, references, assets) to support real skills when needed.
  • Simple path-based organization enabling quick cloning and deployment.

Quick Start

Replace the placeholder content in SKILL.md with the specific skill's details and add any needed resources.

Frequently Asked Questions about template-skill

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

FAQPage Schema
How do I create a Claude skill with the correct metadata for discovery?

To create a Claude skill, you need a SKILL.md file with standardized frontmatter containing required name and description fields to enable consistent discovery and activation. This template enforces required metadata fields and flags any potential completeness issues.

What is the required frontmatter format for a SKILL.md file?

The required frontmatter format for a SKILL.md file uses YAML metadata, mandating fields like name and description to initialize the skill unit. Optional fields allow you to declare resource directories such as scripts, references, and assets.

How do I structure resource directories when building a new skill?

You structure resource directories using a simple path-based organization for optional components like scripts, references, and assets. This setup supports real skills when needed and enables quick cloning and deployment within a structured repository.

Can I use this skill template without adding any dependencies?

Yes, you can use this skill template without dependencies. It requires no external components, allowing you to quickly replace placeholder content in SKILL.md and add needed resources directly within your structured repository.

What is the best way to ensure my custom skill is discoverable?

The best way to ensure your custom skill is discoverable is by enforcing standardized SKILL.md frontmatter with required name and description metadata. This template checks for these fields and flags potential safety or completeness issues during initialization.