test-skill

Validate skill directories by detecting SKILL.md and extracting frontmatter metadata.

7.5k|1.4k|Updated Dec 8, 2024
One-click install
npx skills add https://github.com/tailcallhq/forgecode --skill test-skill-tailcallhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-skill
Source: https://github.com/tailcallhq/forgecode/tree/main/crates/forge_repo/src/fixtures/skills_with_resources/test-skill
Command: npx skills add https://github.com/tailcallhq/forgecode --skill test-skill-tailcallhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a minimal framework for testing skill files and their associated resources within a repository.

Core Features & Use Cases

  • Resource-aware testing: validates the presence of SKILL.md and linked resources, ensuring consistency between metadata and assets.
  • Dry-run verification: allows quick checks of a skill's structure without executing code.
  • Use Case: When validating new skills in a PR, ensure the test-skill directory includes SKILL.md and at least one resource file.

Quick Start

Validate the test-skill directory to confirm SKILL.md exists and resources are accessible.

Frequently Asked Questions about test-skill

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

FAQPage Schema
How do I validate skill metadata and resources in a repository?

To validate skill metadata and resources, detect a root SKILL.md file and extract its frontmatter. This process confirms linked assets like scripts or references are accessible and compatible with the body instructions.

What is the best way to test a skill file without executing its scripts?

Dry-run verification allows quick checks of a skill's structure without executing code. It validates the presence of SKILL.md and ensures linked resources are accessible and consistent with the declared metadata.

How does frontmatter extraction work for repository resources?

Frontmatter extraction identifies a root SKILL.md file and parses its name and description fields. This produces a structured metadata set including tagline, complexity, category, and keywords for repository validation.

Do I need a SKILL.md file to validate repository metadata?

Yes, a SKILL.md file is required to validate repository metadata. The skill identifies and validates self-contained units by detecting this root file and extracting its frontmatter to ensure resource compatibility.

Can I use this validation for repository areas with optional assets?

Yes, validation applies to repository areas containing optional resources like scripts, references, or assets. It ensures these resources are only processed when referenced by SKILL.md and compatible with body instructions.