Use when the user is unsure which LVTD skill or marketplace plugin fits their problem, asks what skill to use, describes a cross-domain workflow, or needs help choosing among installed or source LVTD skills.
SkillScore68Maintained
Automatic
◆AI Engineer pack
Last verified 8/16/2026
What it changes
Passed 11 of 16 test cases with the skill, and 8 of 16 without it.
Without skill50%
With skill68%
Checks it passed that the model alone missed
Selects developer-docs as the primary skill
Classifies the skill as a direct-install skill
Selects make-product-viral as the primary skill
and 5 more in the full report
7 fixed8 passed either way4 still failing3 broke
Pass-rate lift
+18 pp
Tokens
+18%
Agent turns
0%
Response time
-54%
Model gemini-3.6-flashMeasured 8/16/2026v115 of 22 cases passed with skill · 16 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
When dist/registry.json is absent or stale during in-repo routing, which files should be inspected as the source of truth for skill frontmatter and plugin groupings?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies frontmatter in skills/*/SKILL.md as a metadata source
Missed
Passed
Identifies scripts/marketplace-utils.mjs for plugin grouping rules
Missed
Passed
case-11 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md110 linessingle file
LVTD Skills Router
Use this skill to choose the smallest useful set of LVTD skills for the user's
problem. Route by domain, outcome, and evidence needed. Prefer one primary
skill; add secondary skills only when they cover a separate concern in the same
workflow.
Source Of Truth
When working inside this repository, do not hand-maintain a static catalog in
this skill. Use generated metadata:
Run npm run build:registry if dist/registry.json is missing or stale.
Read dist/registry.json.
Use each skill's name, description, category, tags, and
hosts.codex.plugin or hosts.claudeCode.plugin.
Treat skills without a hosts.*.plugin value as direct-install skills.
When the generated registry is not available, inspect source frontmatter in
skills/*/SKILL.md and plugin grouping rules in scripts/marketplace-utils.mjs.
When using an installed plugin outside this repository, route from the installed
skills and plugin metadata available in the current client.
Routing Workflow
Restate the user's concrete task in one phrase.
Search skill names, descriptions, tags, and plugin names for that task.
Choose the most specific matching skill whose description directly covers the
current request.
If several skills match, prefer the one closest to the user's actual work:
implementation over strategy, diagnosis over broad planning, framework-specific
over framework-neutral when the framework is known.
Name the marketplace plugin only when the user asks what to install or when
the matching skill is unavailable in the current client.
Continue with the selected skill when the user asked for work, not just advice.
Useful Registry Queries
List current marketplace plugins and included skills: