good-skill

Validate Skill Units via SKILL.md frontmatter and repository tests.

116|51|Updated May 8, 2026
One-click install
npx skills add https://github.com/LegalQuants/lq-ai --skill good-skill-legalquants
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: good-skill
Source: https://github.com/LegalQuants/lq-ai/tree/main/api/tests/fixtures/skills_with_bad/good-skill
Command: npx skills add https://github.com/LegalQuants/lq-ai --skill good-skill-legalquants

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill Unit enables consistent discovery and validation of modular AI skills by ensuring a metadata-first contract via SKILL.md frontmatter and a clear, executable body.

Core Features & Use Cases

  • Validates presence of a SKILL.md frontmatter with name and description.
  • Supports optional resources (scripts, references, assets) to extend behavior without compromising discovery.
  • Provides a structured metadata surface for automated tooling and repository audits.

Quick Start

Inspect the Skill Unit directory to confirm a SKILL.md frontmatter with name and description.

Frequently Asked Questions about good-skill

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

FAQPage Schema
How do I validate skill discovery in a markdown repository?

You can validate skill discovery by checking that a SKILL.md frontmatter exists with strict name and description fields, then applying tests to repository fixtures to confirm proper activation context and optional resources.

What frontmatter fields are required for skill validation?

Required frontmatter fields for skill validation include a strict name and description within the SKILL.md file, ensuring a metadata-first contract that enables consistent discovery and automated repository audits.

How do I test repository fixtures for skill activation context?

To test repository fixtures for skill activation context, apply validation tests to the filesystem to confirm proper discovery, verify Markdown body usage for operational guidance, and extract dependency and component metadata.

Can I include optional scripts and assets without breaking skill discovery?

Yes, you can include optional resources such as scripts, references, and assets to extend behavior without compromising discovery, provided the required SKILL.md frontmatter name and description fields remain intact.

Why does markdown validation fail when frontmatter is missing a description?

Markdown validation fails when frontmatter lacks a description because the skill enforces a strict metadata-first contract requiring both name and description fields to confirm proper unit discovery and activation context.