skill-one

Identify minimal Skill Units with SKILL.md frontmatter containing name and description.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jaydubya818/New_baseline --skill skill-one-jaydubya818
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-one
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/compound-engineering/tests/fixtures/sample-plugin/skills/skill-one
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill skill-one-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This sample skill provides a minimal, self-contained Skill Unit to illustrate the required discovery structure, frontmatter, and body loading.

Core Features & Use Cases

  • Establishes a SKILL.md frontmatter with a name and description to enable discovery and indexing.
  • Demonstrates how a Skill Unit can house optional resources (scripts, references, assets) without breaking validity.
  • Serves as a reference for testing tooling that extracts metadata and validates Skill Unit structure.

Quick Start

Activate this sample skill to understand the required Skill Unit format and metadata.

Frequently Asked Questions about skill-one

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

FAQPage Schema
What is a SKILL.md frontmatter and how does it work for skill discovery?

A SKILL.md frontmatter is a metadata block that exposes a skill's name and description to enable discovery and indexing by tooling that validates Skill Unit structures.

How do I create a minimal Skill Unit that passes validation?

To create a minimal Skill Unit, establish a SKILL.md frontmatter containing a name and description, then optionally populate resource directories with scripts, references, or assets for runtime use.

Does a valid Skill Unit require scripts and assets directories?

A valid Skill Unit does not require scripts and assets directories; it only mandates a frontmatter with name and description, while resource directories are optional and can be populated as needed.

What's the best way to structure repository metadata for skill indexing?

The best way to structure repository metadata for skill indexing is using a self-contained SKILL.md frontmatter that defines the name and description, allowing tooling to extract metadata and validate the structure.

Can I use a Skill Unit to test metadata extraction and frontmatter validation tooling?

Yes, you can use a sample Skill Unit to test metadata extraction and frontmatter validation tooling because it serves as a reference demonstrating the required discovery structure and body loading.

Why does my skill discovery tooling fail to index a repository without frontmatter?

Skill discovery tooling fails to index a repository without frontmatter because a valid Skill Unit requires a SKILL.md file exposing a name and description to satisfy functional indexing requirements.