test-skill-2

Validate Skill metadata, structure, and YAML frontmatter for discovery.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/jason-hchsieh/mycelium --skill test-skill-2-jason-hchsieh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-skill-2
Source: https://github.com/jason-hchsieh/mycelium/tree/main/test/fixtures/plugins/test-plugin-2/skills/test-skill-2
Command: npx skills add https://github.com/jason-hchsieh/mycelium --skill test-skill-2-jason-hchsieh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unit helps verify the skill discovery pipeline by providing a minimal, well-formed skill that can be scanned and registered.

Core Features & Use Cases

  • Provides a lightweight test scaffold to validate discovery indexing and categorization.
  • Demonstrates required frontmatter fields (name, description, category, capabilities) and basic content structure.
  • Serves as a reusable sanity check for plugin integration and QA processes.

Quick Start

Register this skill in the plugin suite to validate discovery.

Frequently Asked Questions about test-skill-2

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

FAQPage Schema
How do I validate skill discovery indexing within a plugin suite?

Validate skill discovery by registering a minimal, well-formed skill unit with correct YAML frontmatter and a root SKILL.md file. This triggers the plugin suite's indexing, categorization, and accessibility checks to verify the pipeline correctly scans and registers the metadata structure.

What YAML frontmatter fields are required for skill discovery pipelines?

Required YAML frontmatter fields for skill discovery include name, description, category, and capabilities. Providing these essential fields ensures the skill unit satisfies structural validation checks and can be properly scanned and categorized by the discovery pipeline.

How does a test skill verify plugin integration and QA processes?

A test skill verifies plugin integration by acting as a lightweight, reusable scaffold that triggers indexing and categorization checks. It demonstrates the required content structure and frontmatter fields, serving as a sanity check that the plugin suite accurately discovers and registers new skill units.

Can I use a minimal skill scaffold to check categorization and accessibility?

Yes, you can use a minimal skill scaffold to check categorization and accessibility. By registering a well-formed test skill with valid frontmatter, you can verify that the discovery pipeline correctly parses the metadata, assigns categories, and makes the skill accessible across test plugins.

Why does my skill discovery pipeline fail to index new plugin skills?

Skill discovery pipelines fail to index new plugins when the skill unit lacks correct YAML frontmatter or a valid root SKILL.md file. Ensuring essential metadata fields like name, description, category, and capabilities are present resolves structural validation errors and allows successful indexing.

Do I need dependencies to validate a skill discovery pipeline?

No dependencies are required to validate a skill discovery pipeline. The test skill operates as a standalone, lightweight scaffold with no external dependencies, relying solely on correct YAML frontmatter and a root SKILL.md file to trigger indexing and categorization checks.