template-skill

Initialize new Skill units with standardized frontmatter and folder scaffolds.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/luan-thnh/hrm-auto-extension --skill template-skill-luan-thnh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-skill
Source: https://github.com/luan-thnh/hrm-auto-extension/tree/main/.opencode/skills/template-skill
Command: npx skills add https://github.com/luan-thnh/hrm-auto-extension --skill template-skill-luan-thnh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a ready-to-use scaffold for new Skill units, standardizing frontmatter and folder structure.

Core Features & Use Cases

  • Standard frontmatter with required fields (name, description)
  • Optional directories (scripts/), (references/), and (assets/) to extend the skill
  • Consistent metadata generation across multiple skills

Quick Start

Create a new skill directory and fill in the name and description in SKILL.md, then add optional components as needed.

Frequently Asked Questions about template-skill

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

FAQPage Schema
How do I scaffold a new skill unit with consistent metadata and folder structure?

To scaffold a new skill unit, use a template that initializes a standardized YAML frontmatter and folder structure. This generates a root SKILL.md with required name and description fields, alongside optional scripts/, references/, and assets/ directories.

What is the best way to standardize markdown frontmatter across multiple documentation projects?

Standardizing markdown frontmatter across multiple projects requires a shared scaffold that enforces required metadata fields. This template initializes each new unit with consistent YAML frontmatter, ensuring standardized name and description inputs across all files.

Do I need any specific dependencies to generate a markdown skill scaffold?

No dependencies are required to generate the markdown skill scaffold. The template operates independently to create the initial folder structure and YAML frontmatter, allowing you to populate the scripts/, references/, and assets/ directories without external tools.

Can I use this template to create optional directories like references and assets?

Yes, you can use this template to create optional directories. It initializes scripts/, references/, and assets/ folders alongside the root SKILL.md, allowing you to populate them as needed for extended documentation or code execution.

When should I use a standardized scaffold for skill documentation instead of manual setup?

You should use a standardized scaffold when creating multiple skills that require consistent metadata. It prevents manual setup errors by automatically generating the required YAML frontmatter and directory structure, ensuring uniformity across all skill units.

What are the limitations of using a basic template for skill scaffolding?

The limitation of this basic template is that it only provides an initial scaffold with required frontmatter and empty directories. It does not include pre-built components or advanced reasoning logic, requiring you to manually populate the scripts, references, and assets.