s4-unreachable-reference

Identify orphaned reference files not linked to SKILL.md entries.

3|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/kitaekatt/plugins-kit --skill s4-unreachable-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s4-unreachable-reference
Source: https://github.com/kitaekatt/plugins-kit/tree/main/tests/skills-kit/golden_corpus/fixtures/skill/s4-unreachable-reference
Command: npx skills add https://github.com/kitaekatt/plugins-kit --skill s4-unreachable-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill serves as a diagnostic fixture to verify the reachability of reference documentation within the golden corpus testing framework.

Core Features & Use Cases

  • Reachability Testing: Validates that the system correctly identifies orphaned reference files that are not linked to a SKILL.md entry.
  • Fixture Validation: Provides a controlled environment to test failure paths in the documentation indexing system.
  • Use Case: Use this to confirm that your plugin registry correctly flags unreachable documentation during the build or validation phase.

Quick Start

Run the s4-unreachable-reference skill to trigger a reachability check on the current documentation corpus.

Frequently Asked Questions about s4-unreachable-reference

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

FAQPage Schema
How do I check for orphaned reference files in my documentation corpus?

Reachability testing validates structural integrity by scanning the documentation corpus to identify orphaned reference files not linked to a SKILL.md entry. This fixture confirms the system correctly flags unreachable documentation during automated testing workflows.

What is reference documentation reachability testing?

Reference documentation reachability testing is a validation process that scans cross-references between SKILL.md files and the references directory. It verifies structural integrity by identifying orphaned files within the golden corpus that lack proper indexing links.

How do I test failure paths for documentation indexing systems?

You can test failure paths for documentation indexing by running a controlled fixture validation that triggers orphaned reference file detection. This simulates unreachable documentation scenarios to confirm your plugin registry correctly flags structural errors during the build phase.

Does the reachability fixture require any specific dependencies to run?

The reachability fixture requires no external dependencies to run. It relies solely on an internal fixture system to scan and verify cross-references between SKILL.md files and the references directory within your plugin metadata management workflow.

When should I use a fixture to validate plugin metadata?

You should use a fixture to validate plugin metadata during the build or quality assurance phase to ensure no orphaned reference files exist. It is specifically applied when verifying cross-references and structural integrity within the golden corpus testing framework.