skill-router

# Skill Router Scan a repo. Know what the current work needs. Recommend only that. Keep the wiki and graph as the durable catalog behind the decision. ## Scope The router manages runtime recommendations for: - skills - agents - MCP servers Harnesses are separate catalog entities. They are recommended when a user wants to run ctx with a non-Claude-Code host, local model, or API model. Once attached, the harness calls the same skills/agents/MCP recommendation engine. ## Problem Every loaded helper costs tokens, attention, and operational surface area. Most sessions need a small top-scored bundle from the shipped graph, not every entity ctx knows about. Loading too much: - wastes context on irrelevant instructions, - causes misfires when a helper matches the wrong task, - slows the agent loop, and - creates conflicting instructions. ## Architecture ```text ctx/ |-- src/scan_repo.py # Repo scanner -> stack profile |-- src/ctx/core/resolve/resolve_skills.py # Profile -> load/unload manifest |-- src/ctx/core/resolve/recommendations.py # Shared scoring/ranking engine |-- src/ctx/adapters/ # Claude Code hooks + generic tools |-- src/harness_install.py # Custom-model harness install flow `-- graph/wiki-graph-runtime.tar.gz # Shipped graph/wiki runtime ``` The router has three halves: 1. **Scanner** - analyzes a repo and produces stack/task evidence. 2. **Resolver** - scores graph/wiki entities and...