your-skill-name

Provides a reusable template for authoring new Skill units with frontmatter and contracts.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ooooooooooooooooooop/personal-ai --skill your-skill-name-ooooooooooooooooooop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: your-skill-name
Source: https://github.com/ooooooooooooooooooop/personal-ai/tree/main/_template
Command: npx skills add https://github.com/ooooooooooooooooooop/personal-ai --skill your-skill-name-ooooooooooooooooooop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? New Skill authors often lack a consistent starting structure, leading to missing frontmatter fields, unclear trigger conditions, and undefined output contracts. This template supplies a standardized skeleton so every new Skill starts with the required metadata and sections. ## Core Features & Use Cases - Standardized Frontmatter: Includes name, description, version, triggers, not_for, and depends_on fields ready to fill in. - Structured Body Sections: Provides usage scenarios, workflow steps, output contract, and verification sections. - Supporting Directories: Ships with scripts/, references/, and examples/ placeholders plus an agents/openai.yaml interface file. - Use Case: When creating a new Skill for a personal AI repository, copy this template, rename it, and replace the placeholder text with the Skill's actual behavior and triggers. ## Quick Start Copy the _template directory, rename it to your new Skill name, and fill in the frontmatter and sections of SKILL.md with your Skill's actual purpose and workflow.

Frequently Asked Questions about your-skill-name

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

FAQPage Schema
How do I create a new Skill from a template?

Copy the template directory, rename it to your Skill's name, then edit SKILL.md to replace the placeholder frontmatter (name, description, triggers) and fill in the usage scenarios, workflow, output contract, and verification sections.

What fields are required in SKILL.md frontmatter?

The frontmatter requires at minimum a name and description for discovery. This template also includes version, triggers, not_for, and depends_on fields to define activation conditions and exclusions.

What directories should a Skill unit contain?

A Skill unit can optionally include scripts/ for automation, references/ for in-depth documentation, and examples/ showing expected outputs. Only SKILL.md at the root is mandatory.

What is the agents/openai.yaml file used for?

The openai.yaml file defines the agent interface metadata, including display_name, short_description, and a default_prompt that tells the agent when to invoke the Skill.

When should I not use this template?

Do not use it as a functional Skill itself since all content is placeholder text. It only serves as a starting skeleton and must be fully customized before the Skill can perform any real task.