capability-router

Discovers and validates cold skills against a fingerprinted catalog before host loading.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sciman-top/skills-manager --skill capability-router-sciman-top
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capability-router
Source: https://github.com/sciman-top/skills-manager/tree/main/overrides/custom/capability-router
Command: npx skills add https://github.com/sciman-top/skills-manager --skill capability-router-sciman-top

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When a user explicitly names a skill that is absent from the currently visible skill metadata, or when no visible skill semantically covers a specialized request, the host AI has no safe way to find and load that capability. This Skill provides a bounded, read-only fallback that retrieves candidate skills from a local catalog and deterministically validates the exact dependency closure before anything is loaded. ## Core Features & Use Cases - Cold Discovery: Retrieves candidate skills from a local capability catalog using one or two functional domain hints (e.g., decision, engineering, coding, frontend), while keeping semantic selection with the host AI. - Deterministic Validation: Verifies catalog schema and fingerprint, entrypoint and package SHA-256 hashes, path containment, and the full dependency closure before authorizing a read of the validated files. - Execution Admission: Generates admission contracts and handoff files for native subagent execution (one-shot, parent-mediated, or multi-turn interview), with revalidation checks immediately before any controlled write. - Use Case: A user asks for an evidence-based design interview, but no visible skill covers interactive questioning. The host runs the router with the 'decision' domain hint, selects one candidate, validates its closure, and hands it to the appropriate native agent with a strict admission contract. ## Quick Start Ask the assistant to find and validate the named local skill that is missing from the visible skill list, passing the complete request and one functional domain hint.

Frequently Asked Questions about capability-router

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

FAQPage Schema
How do I load a skill that is not in the visible skill list?▼

Run the route-capability.ps1 script with the complete request, -AutoDiscover, and one or two functional domain hints to retrieve candidates. Then validate one exact candidate with -Candidate to check its hashes and dependency closure before the host reads the validated files.

When should the capability router be used instead of a visible skill?▼

Use it only when the user explicitly names a skill missing from visible metadata, or when the host has high confidence no visible skill covers the complete request. It is a bounded fallback, not a routine preflight or per-request middleware.

Does the router decide which skill to load semantically?▼

No. The router performs read-only retrieval and deterministic validation only; the host AI makes the semantic selection from the small candidate set. The catalog enforces decision_owner=host_ai and semantic_routing_performed=false.

What happens if the capability catalog is stale or malformed?▼

Malformed catalogs, fingerprint mismatches, duplicate identities, unknown domains, and invalid hashes produce structured fail-closed findings. Stale entrypoints or package hashes mark skills unavailable, and no candidate is authorized for loading.

Can the router execute a validated skill directly?▼

No. execution_authorization is always not_granted. Execution requires a separate parent-side admission contract handed to a native subagent such as cold-capability-runner or design-griller, with revalidation immediately before any controlled write.