Repo Skills Router

SkillDatabases & data

Routes substantive ML, AI, data, scientific-computing, and software-engineering requests to the smallest useful set of managed repository skills. Invoke proactively when a request names or implies a package, framework, model family, dataset, modality, workflow, backend, deployment target, evaluation method, or implementation approach that may benefit from repository guidance, even if no repository is named. Narrow progressively from area to family to repository root: inspect only the one or two most likely area pages; compare candidates by capability, task surface, model/data format, training versus inference versus evaluation intent, runtime constraints, and root-skill description; then open only the selected root and relevant sub-skills, references, or scripts. Select multiple repositories only when each adds a distinct capability. Do not load the whole collection, treat dependencies or incidental integrations as capabilities, choose by name alone, or force a match when no exact taxonomy family applies.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Repo Skills Router skill

What this skill tells your AI

The instructions your AI receives, as published by vectorspacelab/arex-skill in skills/repositories/repo-skills-router/SKILL.md and read by ahel’s review.

Use this router for substantive requests where a managed repository skill may provide implementation guidance. It is a progressive-disclosure index, not a replacement for the selected repository skill.

Routing procedure

  1. Identify the user's dominant capability, workflow, data/model format, and runtime intent.
  2. Read only the one or two most likely area pages below.
  3. Compare the relevant family pages, especially when training, inference, evaluation, deployment, or similarly named repositories overlap.
  4. Open the selected repository root at ../repo-skills/<skill-id>/SKILL.md, then read only its relevant sub-skills, references, and scripts.
  5. If no exact family fits, do not force a repository match; continue with the general task context or report that the managed collection has no exact route.

A repository may appear in several families. Choose the smallest set of repository roots that directly covers the request, and do not load every candidate listed on a family page.

Area quick map

AreaPopulated familiesRepository membershipsArea page
Computer Vision21312
Biomedical AI1150
Generative Media13194
Speech and Audio556
Natural Language Processing978
LLM Applications16325
LLM Models, Training, and Alignment6149
Information Retrieval467
MLOps15116
Model Deployment and Optimization4114
Training Infrastructure12135
Reinforcement Learning582
Robotics and Embodied AI781
Autonomous Driving338
Graph Learning442
Scientific Computing16124
Data Science12152
Time Series Analysis753
Probabilistic and Causal Modeling420
Responsible AI421

Maintenance

The machine-readable files under references/index/ are the generated routing source of truth. Do not hand-edit area or family pages. For import, refresh, extension, or taxonomy changes, read references/maintenance.md and use the verified importer/updater transaction.

Signals

GitHub stars
278
Forks
21
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
repo-skills-router
Source
github.com/vectorspacelab/arex-skill