gengar-skill-authoring

Enforce SKILL.md frontmatter and structure constraints for in-repo Gengar skills.

Updated May 4, 2026
One-click install
npx skills add https://github.com/JamesFincher/gengar --skill gengar-skill-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gengar-skill-authoring
Source: https://github.com/JamesFincher/gengar/tree/main/skills/software-development/hermes-agent-skill-authoring
Command: npx skills add https://github.com/JamesFincher/gengar --skill gengar-skill-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents malformed or non-discoverable SKILL.md files by specifying the exact validator requirements, conventions, and repository placement rules for authoring in-repo skills.

Core Features & Use Cases

  • In-repo SKILL.md authoring guidance: Covers where to create or edit SKILL.md under skills/<category>/<name>/ and how it differs from user-local skills.
  • Frontmatter and structure constraints: Explains required YAML fields, formatting rules, description length limits, and body non-emptiness requirements.
  • Quality and consistency conventions: Recommends peer-matched sections, typical sizing targets, and verification steps to ensure the skill is ready for commit and discovery.

Quick Start

Use this skill to write a new in-repo SKILL.md at skills/software-development/<your-skill-name>/SKILL.md that starts with valid YAML frontmatter containing name and description.

Frequently Asked Questions about gengar-skill-authoring

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

FAQPage Schema
How do I create a valid SKILL.md file for an in-repo skill?

To create a valid SKILL.md file, place it under skills/<category>/<name>/ and start with YAML frontmatter containing required name and description fields, followed by a non-empty Markdown body.

What are the required frontmatter fields for SKILL.md validation?

SKILL.md frontmatter validation requires correct YAML delimiters with a present name and description within length limits, plus a non-empty operational Markdown body to pass repository validator checks.

How does repository placement affect skill discovery?

Repository placement affects skill discovery by requiring SKILL.md files to reside strictly in skills/<category>/<name>/ directories, ensuring the repository validator can correctly locate and index the skill.

What should I include in an in-repo skill to avoid validation errors?

To avoid validation errors, include correct YAML delimiters, a name and description within size constraints, a non-empty Markdown body, and verification steps like describing when to use the skill and potential pitfalls.

Can I use user-local skill formats for in-repo skills?

User-local skills differ from in-repo skills, which must strictly follow repository conventions by placing SKILL.md under skills/<category>/<name>/ with proper YAML frontmatter and structural constraints.

Why does my SKILL.md fail the repository validator?

Your SKILL.md fails the repository validator if it lacks correct YAML delimiters, has missing or oversized name and description fields, or contains an empty operational Markdown body violating strict formatting constraints.