skill-authoring-majo

Standardize reusable Agent Skills with canonical templates and progressive-disclosure guidelines.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/markjoshwel/skills --skill skill-authoring-majo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring-majo
Source: https://github.com/markjoshwel/skills/tree/main/skill-authoring-majo
Command: npx skills add https://github.com/markjoshwel/skills --skill skill-authoring-majo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating consistent, reusable Agent Skills is hard without a clear pattern and structure. This Skill provides a proven template and workflow to turn repeatable tasks into portable, well-scoped skills.

Core Features & Use Cases

  • Proposes a kebab-case naming convention and frontmatter schema (name, description, license, metadata)
  • Outlines a three-level progressive disclosure design (discovery, activation, deep dive)
  • Includes templates and references for Skill authors to follow across projects
  • Use cases include converting workflows, patterns, and experiences into skills, maintaining AGENTS.md alignment, and enabling cross-project reuse.

Quick Start

Create a new Skill directory named my-topic-majo with SKILL.md frontmatter following the template and add a references/ directory for deeper guidance.

Frequently Asked Questions about skill-authoring-majo

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

FAQPage Schema
What is progressive disclosure in agent skills and how does it structure SKILL.md?

To create reusable agent skills, you establish a kebab-case naming convention and generate a SKILL.md file with compliant frontmatter including name, description, license, and metadata. You then organize content into a three-level structure with an optional references directory.

How do I create reusable agent skills with a standardized template?

To create reusable agent skills, you establish a kebab-case naming convention and generate a SKILL.md file with compliant frontmatter including name, description, license, and metadata. You then organize content into a three-level structure with an optional references directory.

What frontmatter schema is required for automated skill validation and discovery?

The frontmatter schema required for automated skill validation and discovery includes name, description, license, and metadata fields like author and version. This structured metadata enables automated systems to parse, validate, and discover compliant agent skills.

Does the skill authoring template enforce specific naming conventions and directory structures?

Yes, the skill authoring template enforces kebab-case naming conventions for skill directories and mandates a structured directory layout. It requires a SKILL.md file for primary content and an optional resources folder for deeper guidance and references.

When should I use a three-level progressive disclosure design for agent skills?

You should use a three-level progressive disclosure design when developing cross-project agent skills that require onboarding new patterns. It structures information into discovery, activation, and deep dive tiers to ensure skills remain testable and well-scoped.