bad-invocable-skill

Validate boolean invocability and required metadata in SKILL.md frontmatter.

376|31|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/avifenesh/agnix --skill bad-invocable-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bad-invocable-skill
Source: https://github.com/avifenesh/agnix/tree/main/tests/fixtures/invalid/skills/string-boolean-invocable
Command: npx skills add https://github.com/avifenesh/agnix --skill bad-invocable-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and validate skills that declare boolean-based invocability, ensuring the frontmatter includes a valid 'name' and 'description' while flagging non-boolean or ambiguous invocable indicators.

Core Features & Use Cases

  • Validates presence of essential metadata (name, description) in SKILL.md.
  • Detects and flags non-boolean or ambiguous invocable values in frontmatter.
  • Useful for QA pipelines that verify skill definitions before activation in a larger automation system.

Quick Start

Validate that the SKILL.md in this directory adheres to the required frontmatter schema and does not allow non-boolean invocable values.

Frequently Asked Questions about bad-invocable-skill

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

FAQPage Schema
How do I validate the boolean invocability flag in SKILL.md frontmatter?

To validate the boolean invocability flag in SKILL.md frontmatter, check that the metadata includes a valid name and description while flagging any non-boolean or ambiguous invocable values.

What happens when frontmatter contains a non-boolean invocable value in skill fixtures?

When frontmatter contains a non-boolean or ambiguous invocable value in skill fixtures, the validation fails and flags the issue, ensuring only proper boolean values are accepted for invocability.

How do I check that required metadata like name and description exists in SKILL.md?

To check that required metadata like name and description exists in SKILL.md, validate the frontmatter to confirm the presence of these essential fields before processing the invocability flag.

Can I use frontmatter validation for skill fixtures in QA pipelines?

Yes, you can use frontmatter validation for skill fixtures in QA pipelines to verify skill definitions, detect misformatted invocability, and ensure required metadata exists before activating them in larger automation systems.

Why does my skill metadata validation fail on ambiguous invocable indicators?

Skill metadata validation fails on ambiguous invocable indicators because the invocability flag must be a proper boolean value; any non-boolean representation triggers a failure to prevent misformatted metadata.