skills.rest
lemu
lemuCOMMUNITY
Explore all skills by this author →
GitHub

template-skill

Scaffold new Claude skills with SKILL.md frontmatter and optional resource directories.

Updated Oct 22, 2025
Search Tags:#automation#yaml#metadata#developer-tools#frontmatter#skill-template
One-click install
npx skills add https://github.com/lemu/sea-prototype-template --skill template-skill-lemu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: template-skill
Source: https://github.com/lemu/sea-prototype-template/tree/main/.agents/skills/template-skill
Command: npx skills add https://github.com/lemu/sea-prototype-template --skill template-skill-lemu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a ready-to-use scaffold for defining new Claude skills, enabling teams to standardize entry points and metadata.

Core Features & Use Cases

  • Standardized Skill Unit skeletons with name and description frontmatter
  • Optional directories for scripts, references, and assets
  • Clear guidance for documenting and reusing skills across projects

Quick Start

Fill in the frontmatter name and description in SKILL.md and add the instructional content below.

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 standard YAML frontmatter template for new developer tools?▼

A standard YAML frontmatter template requires defining the name and description metadata in a SKILL.md file to establish a consistent entry point for new developer tools. This scaffold ensures standardized documentation across modular units.

What is a Skill Unit scaffold and when do I need YAML frontmatter for it?▼

A Skill Unit scaffold is a ready-to-use structure for defining modular automation components. You need YAML frontmatter when building standardized developer tools that require scalable documentation and consistent metadata extraction.

Can I organize scripts, references, and assets into optional directories for my metadata template?▼

Yes, the metadata template recognizes optional scripts, references, and assets directories. These directories enable scalable documentation by allowing teams to separate instructional content from supporting resources.

What is the best way to standardize entry points and metadata for team automation workflows?▼

The best way to standardize entry points is using a SKILL.md scaffold with YAML frontmatter, extracting name and description fields consistently. This approach ensures compliance across team workflows and enables modular skill reuse.

Do I need any dependencies to define a new skill scaffold with YAML frontmatter?▼

No dependencies are required to define a new skill scaffold. The template operates independently by extracting name and description from SKILL.md frontmatter and recognizing optional resource directories without external packages.

Related Skills

Explore More Software Engineering Skills→
lDuanglDuang

template-skill

Generate skill.meta.json and registry fields from SKILL.md frontmatter.

Community
Basic
BuilderIOBuilderIO
3

create-skill

Document and scaffold new skills with a standard SKILL.md structure.

Official
Basic
mkgs-databricks-demosmkgs-databricks-demos
1

databricks-mlflow-evaluation

Locate root SKILL.md files and extract YAML frontmatter metadata into YAML documents.

Official
Advanced
reason-healthcarereason-healthcare
12

<skill-name>

Define front-matter-driven Skill units with entry points for rh-skills workflows.

Official
Advanced