__SLUG__

Generate agent skill projects from a template with valid SKILL.md entrypoints.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill slug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: __SLUG__
Source: https://github.com/guardiatechnology/design-system/tree/main/.ahrena/framework/templates/skill-project-sample
Command: npx skills add https://github.com/guardiatechnology/design-system --skill slug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill project template eliminates guesswork by providing a ready-to-fill directory structure and required entrypoint so you can scaffold a new agent skill consistently.

Core Features & Use Cases

  • Standardized skill entrypoint: Ensures every generated skill includes a root SKILL.md with required frontmatter fields (name, description, and metadata).
  • Deterministic organization: Provides clear sections and placeholders for when to use, inputs, workflow, tools/scripts/widgets bindings, references, and edge cases.
  • Progressive disclosure support: Includes a references/REFERENCE.md target for detailed technical material loaded on demand.

Quick Start

Use the template by running kata-init-skill with a kebab-case slug and then replace all placeholders in SKILL.md (and any other files) before publishing the resulting skill.

Frequently Asked Questions about __SLUG__

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

FAQPage Schema
How do I scaffold an agent skill project with a valid SKILL.md entrypoint?

To scaffold an agent skill project, run kata-init-skill with a kebab-case slug to generate a directory structure enforcing a valid SKILL.md entrypoint with required YAML frontmatter. Replace all placeholders in the generated files before publishing.

What is the required structure for an agentskills.io SKILL.md metadata file?

An agentskills.io SKILL.md requires YAML frontmatter with name, description, and metadata fields conforming to the specification schema_version. The body needs sections for inputs, workflow, tools binding, and references.

How do I organize workflow steps and tools when designing a new agent skill?

Organizing workflow steps and tools uses a deterministic template providing clear sections for inputs, workflow design, tools/scripts/widgets wiring, and edge cases, ensuring consistent structure across all generated skills.

Can I include on-demand technical references in my skill project directory?

Yes, you can include on-demand technical references through the references/REFERENCE.md target, which supports progressive disclosure by loading detailed technical material only when needed during execution.

Do I need to manually replace placeholders in the generated skill template?

Yes, you must manually replace all placeholders in SKILL.md and any other generated files before publishing the resulting skill to ensure the directory conforms to the agentskills.io specification.

What happens if I omit required YAML frontmatter fields in my SKILL.md file?

Omitting required YAML frontmatter fields like name, description, and metadata invalidates the skill project structure, preventing it from conforming to the agentskills.io specification schema_version.