my-skill

Validate standalone skill discovery and activation in plugin-free test environments.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/mandersogit/brynhild-harness --skill my-skill-mandersogit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-skill
Source: https://github.com/mandersogit/brynhild-harness/tree/main/tests/fixtures/skills/my-skill
Command: npx skills add https://github.com/mandersogit/brynhild-harness --skill my-skill-mandersogit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A standalone test skill used for general testing scenarios, useful for testing discovery and activation of Brynhild skills or for quick experimentation.

Core Features & Use Cases

  • Simple, self-contained skill for testing discovery and loading
  • Flexible prompts to validate skill activation
  • Lightweight structure suitable for experiments

Quick Start

Place this skill in your skills directory and trigger it with the name "my-skill" to verify that discovery and activation work as expected.

Frequently Asked Questions about my-skill

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

FAQPage Schema
How do I validate that standalone skills are discoverable and loadable in my environment?

Standalone skill discovery validates that skills stored directly in your skills directory are detectable and executable without plugin ecosystems. Place a skill in your skills directory and trigger it by name to verify discovery and activation work end-to-end, confirming YAML front matter (name, description, license, allowed-tools, metadata) and Markdown structure are correctly formatted.

What structure does a standalone skill need to follow for proper testing?

A standalone skill requires YAML front matter with name, description, license, and allowed-tools fields, followed by Markdown body content and step-by-step instruction sections. This layout enables the skill manifest to be parsed and executed in test environments with basic instruction sequencing and plugin-free operation.

Can I use a simple test skill to verify my skills directory setup works?

Yes, a lightweight standalone test skill validates your skills directory configuration and activation mechanisms. Deploy it to your skills directory to confirm that discovery, loading, and execution function correctly in plugin-free test environments without complex dependencies or components.

Why would I test skill discovery outside of plugin ecosystems?

Testing skill discovery outside plugin ecosystems ensures your skills are detectable and executable in minimal, isolated environments. This validation confirms functional and technical requirements are met for skill manifests, content layout, and instruction sequencing independent of plugin infrastructure.

What's the quickest way to verify a new skill works after placing it in the skills directory?

Trigger the skill by its name to verify discovery and activation. A simple standalone skill confirms basic instruction sequencing and YAML front matter parsing work correctly, giving immediate feedback on whether your skill is loadable and executable in the target environment.