test-skill

Register and validate skill discovery and activation in the plugin system.

147|31|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/serpro69/claude-toolbox --skill test-skill-serpro69
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-skill
Source: https://github.com/serpro69/claude-toolbox/tree/main/cmd/generate-kodex/testdata/source-plugin/skills/test-skill
Command: npx skills add https://github.com/serpro69/claude-toolbox --skill test-skill-serpro69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This is a minimal test skill used to validate the discovery and loading of skills within the plugin system, ensuring basic metadata and activation flow.

Core Features & Use Cases

  • Lightweight smoke tests for skill loading and description rendering.
  • Demonstrates frontmatter-driven discovery and self-contained instruction bodies.
  • Useful for local development to sanity-check plugin behavior before adding real functionality.

Quick Start

Instruct the AI to run a basic test verification for the test-skill.

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 frontmatter presence in a plugin system?

You can validate skill metadata and frontmatter presence by registering a minimal test skill to check frontmatter discovery and name extraction. This smoke test verifies that the plugin system correctly loads self-contained instruction bodies during local development.

Can I run a smoke test for plugin activation flows during local development?

Yes, you can run a smoke test for plugin activation flows by instructing the AI to execute a basic test verification. This quickly checks whether a skill is correctly discovered and its description renders properly within the local plugin system.

What is frontmatter-driven discovery for Claude plugin tests?

Frontmatter-driven discovery is the mechanism where the plugin system reads skill metadata to register and load instructions. It requires a minimal, self-contained body and correct frontmatter presence to properly extract the skill name and description.

Do I need any dependencies to test skill loading and description rendering?

No dependencies are required to test skill loading and description rendering. The test skill is lightweight and self-contained, allowing you to sanity-check plugin behavior and frontmatter extraction directly in your local development environment.

When should I use a minimal test skill to check plugin behavior?

You should use a minimal test skill to check plugin behavior when you need to sanity-check discovery and loading before adding real functionality. It is applicable for local development scenarios to quickly validate basic activation flows and metadata rendering.