broken-calls

Validate that calls list SKILL.md targets reference existing skill definitions.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill broken-calls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: broken-calls
Source: https://github.com/usurobor/cnos/tree/main/schemas/fixtures/skill-frontmatter/invalid/broken-calls
Command: npx skills add https://github.com/usurobor/cnos --skill broken-calls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unit acts as a negative fixture to verify that calls referencing other SKILL.md targets point to existing SKILL.md definitions. If a referenced target is missing, the activation pipeline should reject the reference to prevent broken activation flows.

Core Features & Use Cases

  • Reference validation: detects broken or missing skill targets in the calls list.
  • Integrity enforcement: ensures all referenced skills exist before activation.
  • Testing utility: used to validate error handling during activation when inter-skill references are invalid.

Quick Start

Run the repository's validation on this skill to confirm that a missing target in the calls list triggers a failure.

Frequently Asked Questions about broken-calls

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

FAQPage Schema
How do I validate skill references in a CI pipeline to catch broken links?

Skill reference validation detects broken or missing targets in a calls list, ensuring referenced skills exist before activation. It prevents broken activation flows by enforcing presence of valid inter-skill references during the pipeline.

Why does skill activation fail when a referenced target is missing?

Activation fails because the validation pipeline rejects references to missing SKILL.md targets to prevent broken activation flows. This integrity enforcement ensures all inter-skill dependencies exist before the activation process can successfully complete.

How do I test error handling for invalid inter-skill references during activation?

Test error handling by using a negative fixture that includes calls referencing non-existent SKILL.md targets. Running repository validation on this fixture confirms that a missing target triggers a failure and surfaces the expected activation error.

What is a negative fixture for skill reference validation?

A negative fixture for skill reference validation is a test skill unit containing calls with intentionally broken or missing SKILL.md targets. It verifies that the activation pipeline correctly rejects invalid inter-skill references instead of failing silently.

Can I use this reference validation for repository-wide dependency checks?

Yes, you can apply this reference validation to repository validation workflows to ensure skills reference each other correctly across the entire project. It enforces that every entry in the calls list resolves to an existing skill definition during checks.