{{name}}

Scaffolds new Skill units with standardized SKILL.md, provenance, and evaluation files.

22|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/Lynricsy/HyperSkills --skill name-lynricsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: {{name}}
Source: https://github.com/Lynricsy/HyperSkills/tree/main/templates/skill
Command: npx skills add https://github.com/Lynricsy/HyperSkills --skill name-lynricsy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Authoring a new Skill from scratch often leads to inconsistent structure, missing provenance records, and untested behavior. This template enforces a single standard for SKILL.md frontmatter, section layout, upstream attribution, and evaluation scenarios so every new Skill starts complete and reviewable. ## Core Features & Use Cases - Standardized SKILL.md skeleton: Provides placeholder-driven frontmatter (name, description, version, category) plus prescribed sections for scope, core rules, workflows, topic router, and output format. - Upstream provenance tracking: Ships a SOURCES.yaml schema for recording repo and docs upstreams with pinned commits, licenses, and contribution notes. - Built-in evaluation scaffolding: Includes an evals.json template requiring positive trigger scenarios and at least one near-miss negative case. - Use Case: When adding a new Skill to a curated library, copy this template, fill in the placeholders, and immediately have a structure that passes structural CI checks and supports behavior evaluation. ## Quick Start Copy the templates/skill directory, replace every {{name}}, {{version}}, and {{category}} placeholder, and fill in the TODO fields to author a new Skill.

Frequently Asked Questions about {{name}}

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

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

Copy the templates/skill directory, rename it to your skill name, and replace the {{name}}, {{version}}, and {{category}} placeholders in SKILL.md and SOURCES.yaml. Then fill in the scope, core rules, workflows, and evaluation TODOs.

What files are required in a valid Skill unit?

A valid Skill unit requires a SKILL.md at its root with YAML frontmatter containing at least a name and description. Optional directories like references/, scripts/, and assets/ hold on-demand resources referenced by the instructions.

What should go in the SKILL.md description field?

The description is a single short routing sentence of 1-160 characters stating the task and key technology in third person. Detailed coverage, exclusions, and procedures belong in the body sections, not the description.

How do I track upstream sources for a Skill?

Record each upstream in SOURCES.yaml with its kind (repo or docs), repository, consulted paths, ref, pinned 40-character commit, license, and relation (merged or reference). The commit field is filled automatically by the check_upstream.py pinning tool.

Why does the evals template require a negative test case?

The near-miss negative case verifies the Skill does not trigger on similar but out-of-scope requests, preventing false activations. Each Skill needs at least three scenarios total, including at least one case where the Skill must not be invoked.