skill-name

Define reusable Skill entries with SKILL.md frontmatter for Claude Code and Codex workflows.

2|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/yzlin/supaviber --skill skill-name-yzlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-name
Source: https://github.com/yzlin/supaviber/tree/main/.templates/skill-template
Command: npx skills add https://github.com/yzlin/supaviber --skill skill-name-yzlin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This template provides a standardized entry point for creating Skill units, ensuring every Skill is discoverable via SKILL.md frontmatter and loaded consistently by Claude Code and Codex.

Core Features & Use Cases

  • Standard frontmatter with mandatory fields (name, description) to enable reliable indexing.
  • A well-structured Markdown body that guides agent execution and operational steps.
  • Optional directories (scripts/, references/, assets/) for extended functionality without breaking discovery.

Quick Start

Create a new skill directory (e.g., skill-name), add SKILL.md at its root with appropriate frontmatter, and implement the core description and instructions. Optionally add scripts/, references/, and assets/ as needed to extend the skill's capabilities.

Frequently Asked Questions about skill-name

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

FAQPage Schema
How do I define a reusable AI workflow for Claude Code and Codex?

To define a reusable AI workflow, create a repository directory containing a SKILL.md file with mandatory name and description frontmatter, enabling consistent discovery and activation by Claude Code and Codex agents.

What is the SKILL.md frontmatter structure needed for skill discovery?

The SKILL.md frontmatter structure requires at least the name and description fields to enable reliable indexing. Optional metadata fields can also be included to provide additional context for agent execution.

How do I structure a skill definition to extend AI agent capabilities?

Structure a skill definition by writing a well-structured Markdown body in SKILL.md for operational steps, and optionally add scripts/, references/, and assets/ directories to extend AI agent capabilities without breaking discovery.

Can I use repository-based skill definitions without adding scripts or assets?

Yes, you can use repository-based skill definitions with only the SKILL.md file. The scripts/, references/, and assets/ directories are completely optional and only needed when extended functionality is required.

What is the best way to ensure my custom AI workflow is loaded consistently by Codex?

The best way to ensure consistent loading by Codex is providing a standardized entry point via SKILL.md frontmatter with mandatory name and description fields, ensuring reliable indexing across development environments.

Do I need dependencies to build AI-driven workflows with a skill template?

No, you do not need dependencies to build AI-driven workflows with this skill template. It requires only a SKILL.md file with appropriate frontmatter to establish a standardized entry point for discovery.