specification-by-example

Locate and verify canonical SKILL.md files and optional supporting files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ctimmerman-prog/ai-config-opencodeai-first-to-others --skill specification-by-example
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specification-by-example
Source: https://github.com/ctimmerman-prog/ai-config-opencodeai-first-to-others/tree/main/.cursor/skills/specification-by-example
Command: npx skills add https://github.com/ctimmerman-prog/ai-config-opencodeai-first-to-others --skill specification-by-example

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This wrapper helps teams locate and verify the canonical skill specification by pointing to the canonical SKILL.md and loading any supporting files in the same folder. It ensures you can confirm the skill's identity by reading the first heading.

Core Features & Use Cases

  • Locate the canonical skill at the specified path and open its SKILL.md.
  • Load optional supporting files in the same folder (examples, templates) if present.
  • Verify correctness by reporting the first heading read from the canonical file, or alerting if unreadable.
  • Use case: when integrating or documenting skills to ensure consistency and traceability across environments.

Quick Start

Open the canonical file at .opencode/skills/specification-by-example/SKILL.md and verify its first heading.

Frequently Asked Questions about specification-by-example

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

FAQPage Schema
How do I verify a canonical skill specification from an example-based wrapper?

To verify a canonical skill specification, open the canonical SKILL.md file at the specified path and read its first heading. This confirms the skill's identity and ensures consistency and traceability across environments.

What is the best way to locate supporting files for a skill specification?

Locate supporting files for a skill specification by opening the canonical SKILL.md and loading optional files in the same folder. This includes examples, templates, scripts, references, and assets that may accompany the skill.

How does frontmatter validation work for skill documentation?

Frontmatter validation for skill documentation ensures a Markdown frontmatter exists containing the name and description. This metadata confirms the skill's identity and enables proper skill discovery across environments.

Why does my skill specification verification alert that the canonical file is unreadable?

Skill specification verification alerts when the canonical SKILL.md file is unreadable because it cannot confirm the skill's identity by reading the first heading. Check the specified path to ensure the file exists and is accessible.

Do I need a specific folder structure to document skills from example-based wrappers?

You need a folder structure that places the canonical SKILL.md at the specified path with optional supporting files in the same folder. This structure ensures the wrapper can locate the specification and load any examples or templates present.

When do I need to trace and validate canonical skill specifications across environments?

You need to trace and validate canonical skill specifications when integrating or documenting skills across environments. This ensures consistency and traceability by confirming the skill's identity through the first heading in the SKILL.md file.