skill-system-router
Skill System Router
Deprecated compatibility surface. skill-system-cli now owns the router runtime module used by sk, while this skill remains available so existing router docs, policy references, and legacy entrypoints do not break during the transition.
You are the Router. This skill teaches you how to orchestrate other skills.
Router is an internal orchestration layer. The public user-facing entrypoint remains sk from skill-system-cli.
How It Works
User goal → Read skills-index.json → Match capabilities → Read skill manifest
→ (Complex goal: plan with workflow) → Check policy → Execute entrypoints → Parse JSON output → Decide next step → Log
Step 0: Installer Bootstrap Check (First Run Only)
Check if the project's AGENTS.md contains ## Skill System.
More from arthur0824hao/skills
skill-system-memory
Persistent shared memory for AI agents backed by PostgreSQL (fts + pg_trgm, optional pgvector). Includes compaction logging and maintenance scripts.
99skill-system-soul
Agent behavioral profiles that standardize how different LLMs behave. Load this skill when you need to: (1) adopt a specific behavioral mode for a task, (2) switch between creative/strict/talkative modes, (3) ensure consistent behavior across different models. Profiles define personality, decision heuristics, communication style, and quality standards.
67skill-system-postgres
Postgres-backed observability and policy store for the skill system. Provides tables for policy profiles (effect allowlists), skill execution runs, and step-level events. Use when setting up the skill system database or querying execution history.
63skill-system-insight
Deprecated compatibility shim for observe-and-evolve flows. skill-system-soul is now the canonical owner; this skill remains as a redirect surface for existing commands, docs, and tests.
62skill-system-workflow
Pure planning engine. Converts goals into DAGs with Mermaid visualization. Ticket lifecycle has moved to skill-system-tkt.
62skill-system-behavior
BDD-style behavior specification engine for the skill system. Use when: (1) defining a new skill's behavior before implementation, (2) validating a spec against the schema, (3) generating a behavior contract (Mermaid DAG) from a spec, (4) running structural acceptance tests against a built skill. Workflow: Spec → Test → Develop → Contract.
51