beta

Tests installation and validation of multiple skills from one directory.

111|9|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Peiiii/skild --skill beta-peiiii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beta
Source: https://github.com/Peiiii/skild/tree/main/examples/sample-skills/beta
Command: npx skills add https://github.com/Peiiii/skild --skill beta-peiiii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This beta skill provides a minimal, dependency-free blueprint to test the end-to-end lifecycle of Skill units, including discovery, activation, and basic execution, without requiring external tooling.

Core Features & Use Cases

  • Lightweight placeholder to validate the install and validation workflows for skills located in a single directory.
  • Useful for testing that multiple skills can be installed and activated from the same folder and that the validation path executes without error.
  • Example Use Case: a developer confirms the toolchain correctly detects a Skill's frontmatter and loads its activation instructions.

Quick Start

Install this skill directory and run validation to confirm the end-to-end setup.

Frequently Asked Questions about beta

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

FAQPage Schema
How do I validate a directory-based skill installation end-to-end?

To validate a directory-based skill installation end-to-end, install the skill directory and run validation to confirm the toolchain detects the SKILL.md frontmatter and executes the activation path without error.

What is a testbed skill used for in a workflow?

A testbed skill in a workflow is a minimal, dependency-free blueprint used to test the end-to-end lifecycle of skill units, including discovery, activation, and basic execution without external tooling.

Does skill validation require external dependencies?

Skill validation does not require external dependencies; this testbed operates entirely without external tooling, needing only a root SKILL.md with YAML frontmatter defining name and description.

Can I test multiple skills installed from the same directory?

You can test multiple skills installed from the same directory by using this lightweight placeholder to validate that multiple skills install, activate, and execute their validation paths without error.

How do I confirm a toolchain correctly detects SKILL.md frontmatter?

To confirm a toolchain correctly detects SKILL.md frontmatter, install this testbed skill directory and run the validation workflow to verify the toolchain loads the activation instructions from the YAML frontmatter.