skills-authoring

Generate and update SKILL.md frontmatter and templates for AI agent skills.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/galligan/skillstash --skill skills-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-authoring
Source: https://github.com/galligan/skillstash/tree/main/.agents/skills/skills-authoring
Command: npx skills add https://github.com/galligan/skillstash --skill skills-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates or updates skills with proper YAML frontmatter, progressive disclosure, and best practices per the open Agent Skills specification. Supports simple, tool-restricted, multi-file, and script-based skills. Use when creating new skills, authoring skills, extending agent capabilities, or when --create-skill or --new-skill flag is mentioned.

Core Features & Use Cases

  • Templates supported: from templates/:
    • simple-skill.md - Single SKILL.md file
    • tool-restricted-skill.md - Limited tool access
    • multi-file-skill.md - With supporting files
    • script-based-skill.md - Includes executable scripts
  • Name pattern: kebab-case and must match directory
  • Frontmatter validation: name, description, and optional fields
  • Supporting files: Add references/, scripts/, or assets/ when needed
  • Progressive disclosure: keep SKILL.md lean; move details to supporting files
  • Validation aids: ensures compatibility with Agent Skills specification

Quick Start

  1. Pick a template from templates/ (e.g., simple-skill.md).
  2. Generate the skill directory name (lowercase, hyphens only) and ensure it matches name in frontmatter.
  3. Write SKILL.md with frontmatter and instructions.
  4. Optionally add references/, scripts/, or assets/ to extend capabilities.

Frequently Asked Questions about skills-authoring

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

FAQPage Schema
How do I create a new AI agent skill with proper frontmatter?

Create a skill by selecting a template from `templates/` (simple, tool-restricted, multi-file, or script-based), generate a kebab-case directory name matching the frontmatter `name` field, write SKILL.md with YAML frontmatter and instructions, then optionally add `references/`, `scripts/`, or `assets/` directories. The frontmatter must include name, description, and follow Agent Skills specification requirements.

What's the difference between simple, tool-restricted, multi-file, and script-based skill templates?

Simple skills use a single SKILL.md file. Tool-restricted skills limit agent tool access. Multi-file skills include supporting files in `references/`, `scripts/`, or `assets/`. Script-based skills include executable scripts. Choose based on your skill's complexity and whether it needs external resources or tool constraints.

How do I structure supporting files and progressive disclosure in a skill?

Keep SKILL.md lean with core instructions and frontmatter, then move detailed content to supporting files: `references/` for documentation, `scripts/` for executables, `assets/` for other resources. Progressive disclosure ensures the skill page remains scannable while details are available when needed, following Agent Skills specification best practices.

What validation does the skill authoring process enforce?

Skill authoring validates YAML frontmatter syntax, enforces third-person descriptions, requires trigger keywords, checks kebab-case naming conventions, verifies tool restrictions are compatible across tools, and ensures directory names match the frontmatter `name` field. Validation confirms compliance with the open Agent Skills specification.

Can I use this for extending existing agent capabilities?

Yes. The skill authoring process supports creating new skills and updating existing ones with proper frontmatter, progressive disclosure, and Agent Skills specification compliance. Use it when adding new agent capabilities or when flags like `--create-skill` or `--new-skill` are invoked.

What naming conventions must my skill directory and frontmatter follow?

Skill names must be lowercase kebab-case (hyphens only, no underscores or spaces) and the directory name must exactly match the `name` field in SKILL.md frontmatter. This ensures consistency and cross-tool compatibility within the Agent Skills ecosystem.