Skip to main content
skillspec index and skillspec route are the core skill-discovery primitives. index builds a local SQLite catalog from one or more harness skill roots. route scores candidate skills from that catalog against a task query and returns an authoritative routing decision. These are runtime skill discovery commands, not source analysis, workspace recon, or skill import. When the router is installed and enabled, use skillspec router index refresh instead of skillspec index directly, so visibility controls and preparedness checks run too.

skillspec index

Builds the local SQLite skill catalog used by skillspec route and the optional skill router. Directory paths resolve to skill-index.sqlite.
Running skillspec index directly prints warnings that explain router state: no installed router config means standalone manual lookup only; disabled router mode means the index will not affect implicit skill selection until skillspec router enable; enabled router mode should use skillspec router index refresh so visibility controls and preparedness checks run too.

Example


skillspec route

Scores candidate skills from the index and returns an authoritative routing decision: use_skill, bypass, or ambiguous.

Route decisions

bypass and ambiguous leave selected null and include bypass_reason (no_candidates, low_confidence, ambiguous_match, no_activation_anchor, policy_passthrough).

Scoring and deduplication

  • Duplicate physical installs of the same logical skill are collapsed before the match gate.
  • --current-harness and --current-root only choose the preferred physical copy after logical selection.
  • Managed skill-router packages are always excluded from candidates.
  • If a router policy profile is active, policy can prefer, allow, suppress, or forbid generic targets (skill:<name>, tag:<tag>, source:<source>, has_skill_spec:<true|false>) before the match gate.
  • Output includes base_score, policy_score, policy_reason, and policy when a policy was applied.

Examples


skillspec skills subcommands

Inspect and manage installed skills.

skills audit

Audits routing metadata for overlong descriptions (over 800 characters), vague descriptions, missing negative boundaries, and duplicate names.

skills set-visibility

Sets one skill’s conceptual visibility using native Codex/Claude controls and records a reversible manifest.

skills disable / skills enable

Convenience wrappers for set-visibility.
  • disable sets the skill to off (excluded from router results when the manifest is used).
  • enable sets the skill to implicit.

To understand why a query routes or does not route to a skill, use skillspec router policy explain --query <text> — it returns the full route report with matched policy rules and score changes.
  • skillspec router index refresh — Rebuild the index with router-managed visibility controls applied.
  • skillspec router index status — Check for new, changed, or missing skills in the index.
  • skillspec route — Query the catalog after building the index.
  • skillspec visibility plan/apply/restore — Manage harness-native visibility independently.