sage-skill-development

Define a standard specification for Sage Skill units with YAML frontmatter.

12|1|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/majiayu000/sage --skill sage-skill-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sage-skill-development
Source: https://github.com/majiayu000/sage/tree/main/.sage/skills/sage-skill-development
Command: npx skills add https://github.com/majiayu000/sage --skill sage-skill-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines the standard for creating and organizing Sage Skills, ensuring consistent discovery, activation, and interoperability across Skill units.

Core Features & Use Cases

  • Provides a formal frontmatter schema (name, description, when_to_use, allowed_tools) and clear structure for SKILL.md.
  • Enables compatibility between Sage Skills and Claude Code format, including auto/manual triggering and metadata fields.
  • Serves as a reference for teams to design new Skills and audit existing Skill implementations.

Quick Start

Read the SKILL.md to understand the required fields and how to structure a new Skill unit, then create or modify a Skill directory accordingly.

Frequently Asked Questions about sage-skill-development

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

FAQPage Schema
How do I structure frontmatter for Claude Code agent skills?

Frontmatter for Claude Code agent skills requires mandatory YAML name and description fields, while optional when_to_use and allowed_tools fields control auto or manual triggering.

What is the standard format for writing a SKILL.md file?

The standard SKILL.md format requires YAML frontmatter with name and description fields to ensure consistent discovery, and supports optional components like scripts and references within the Skill directory.

How does skill discovery and activation work in Sage?

Skill discovery and activation in Sage works by scanning project and user discovery paths, matching frontmatter metadata to trigger conditions, and loading associated components like scripts and assets when present.

Can I use optional resource directories when developing a skill?

Yes, you can use optional resource directories when developing a skill to populate components like scripts, references, and assets, which are loaded by the agent when the skill is activated.

What are the limitations of the Sage skill development specification?

The specification is limited to governing frontmatter fields and resource directories for Skill units, meaning it does not define complex execution logic but strictly enforces mandatory name and description metadata.