broken-skill

Simulate packager failure from a missing interface field in SKILL.md.

2.4k|224|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/yaojingang/yao-meta-skill --skill broken-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: broken-skill
Source: https://github.com/yaojingang/yao-meta-skill/tree/main/tests/fixtures/package_missing_interface_field
Command: npx skills add https://github.com/yaojingang/yao-meta-skill --skill broken-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill is a broken fixture designed to test the packager's failure when the interface field is missing.

Core Features & Use Cases

  • Test Case: Simulates a scenario where the packager encounters an error due to the absence of the interface field in the SKILL.md file.
  • Use Case: This Skill can be used to verify that the packager correctly handles missing interface fields and reports the error accordingly.

Quick Start

Run the broken-skill to observe the packager's error handling for a missing interface field.

Frequently Asked Questions about broken-skill

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

FAQPage Schema
How do I test packager error handling for a missing interface field in a skill package?

You can test packager error handling for a missing interface field by running a broken skill package fixture. This simulates the absent field scenario to verify the packager detects the error and reports the failure correctly.

What happens when the interface field is missing from a skill package during packaging?

When the interface field is missing from a skill package, the packager should trigger an error handling mechanism. This broken fixture simulates that exact failure scenario to verify the packager correctly detects the absent field and reports the error.

Why does my skill package fail to package when the interface field is absent?

Your skill package fails to package when the interface field is absent because the packager requires this field for valid processing. This mechanism is designed to catch incomplete skill packages and report the missing interface field error accordingly.

How do I verify that the packager reports errors correctly for incomplete skill packages?

To verify that the packager reports errors correctly for incomplete skill packages, run a test case simulating a missing interface field. This broken fixture allows you to observe the packager's error handling and reporting mechanisms in action.

Can I use a broken test case to check skill package validation for missing fields?

Yes, you can use a broken test case to check skill package validation for missing fields. This specific fixture simulates a missing interface field, allowing you to verify the packager correctly handles the error and reports the absence accordingly.