template-skill

Create a ready-to-edit Skill skeleton with standardized frontmatter metadata.

141|20|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/julianromli/opencode-template --skill template-skill-julianromli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-skill
Source: https://github.com/julianromli/opencode-template/tree/main/skill/template-skill
Command: npx skills add https://github.com/julianromli/opencode-template --skill template-skill-julianromli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Starter Skill defines the minimal structure for creating new Skills, guiding teams to provide a proper name, description, and optional resources in a consistent format.

Core Features & Use Cases

  • Standardized metadata: Enforces frontmatter with name and description for discoverability.
  • Extensible resources: Supports optional scripts/, references/, and assets/ directories for additional context.
  • Quick-start ready: Includes a ready-to-edit Quick Start instruction to bootstrap usage.

Quick Start

Customize the frontmatter (name and description) and add optional resources as needed to tailor the Skill for your project.

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 new skill with YAML frontmatter and consistent metadata?

To create a new skill with consistent metadata, use a starter kit that enforces YAML frontmatter with mandatory name and description fields, ensuring discoverability across projects.

What is the minimal structure required for building OpenCode skills?

The minimal structure for OpenCode skills requires frontmatter metadata containing name and description fields, alongside a ready-to-edit Quick Start instruction to bootstrap usage.

Can I include optional scripts and references directories in my skill skeleton?

Yes, the skill skeleton supports optional scripts, references, and assets directories to provide extensible resources and additional context for your customized project.

What is the best way to standardize metadata across multiple custom skills?

The best way to standardize metadata is using a reusable starter skill skeleton that enforces mandatory frontmatter fields and a consistent directory structure for all team members.

Do I need to configure dependencies before using a starter skill for rapid customization?

No, the starter skill has zero dependencies and requires no configuration before use; simply customize the frontmatter and add optional resources as needed for your project.