How do I install the Solid Intent Router skill?

Run npx skillmds@latest add tomevault-io/solid-intent-router in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Solid Intent Router safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Solid Intent Router?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Solid Intent Router free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Solid Intent Router?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Solid Intent Router by tomevault-io

Name: Solid Intent Router
Author: tomevault-io

Solid Intent Router

Route SolidJS user intent to the correct macro and domain subskill with deterministic keyword precedence and fallback rules. Use when selecting which Solid skill should execute first. Use when this capability is needed.

tomevault-io 4a6d471 2 files · 2.8 KB Updated Sep 17, 2026

File contents

solid-intent-router

Trigger

Use this skill when a request could match multiple SolidJS skills and deterministic routing is required.

Required Inputs

Raw user prompt.
Optional file/diff context if present.
Optional runtime hint (core/router/start/meta).

Workflow

Evaluate explicit package signals first (solid-router, solid-start, solid-meta).
Apply deterministic precedence from tools/gemini-mcp-extension/skill-routing-map.md.
Select one primary macro skill and one secondary domain subskill.
If confidence is low, choose the closest macro skill and annotate missing input.

Failure Modes

Conflicting package signals: route to solid-design-patterns + best-fit domain subskill.
No recognizable signal: default to solid-component-builder + solid-reactivity-core-expert.
Missing prompt text: fail and request prompt.

Output Contract

Return output matching IntentRoutingOutput schema with primary_skill, secondary_skill, confidence, rationale, and citations (doc_id, claim).

Validation

node tools/scripts/validate-skills.mjs --skill solid-intent-router
node tools/scripts/run-smoke-evals.mjs

Key Corpus References

Use these doc_id values with the read_corpus_doc MCP tool:

solid-core.reference.basic-reactivity.create-signal — core signal API (default fallback)
solid-router.solid-router.index — router package overview
solid-start.solid-start.index — SolidStart package overview
solid-meta.solid-meta.index — solid-meta package overview

References

../../tools/gemini-mcp-extension/skill-routing-map.md
../../references/solidjs-normalized/manifest.jsonl
../../references/solidjs-normalized/taxonomy.json

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: solid-intent-routerdescription: Route SolidJS user intent to the correct macro and domain subskill with deterministic keyword precedence and fallback rules. Use when selecting which Solid skill should execute first. Use when this capability is needed.---# solid-intent-router## TriggerUse this skill when a request could match multiple SolidJS skills and deterministic routing is required.## Required Inputs- Raw user prompt.- Optional file/diff context if present.- Optional runtime hint (core/router/start/meta).## Workflow1. Evaluate explicit package signals first (`solid-router`, `solid-start`, `solid-meta`).2. Apply deterministic precedence from `tools/gemini-mcp-extension/skill-routing-map.md`.3. Select one primary macro skill and one secondary domain subskill.4. If confidence is low, choose the closest macro skill and annotate missing input.## Failure Modes- Conflicting package signals: route to `solid-design-patterns` + best-fit domain subskill.- No recognizable signal: default to `solid-component-builder` + `solid-reactivity-core-expert`.- Missing prompt text: fail and request prompt.## Output ContractReturn output matching `IntentRoutingOutput` schema with `primary_skill`, `secondary_skill`, confidence, rationale, and `citations` (`doc_id`, `claim`).## Validation- `node tools/scripts/validate-skills.mjs --skill solid-intent-router`- `node tools/scripts/run-smoke-evals.mjs`## Key Corpus ReferencesUse these `doc_id` values with the `read_corpus_doc` MCP tool:- `solid-core.reference.basic-reactivity.create-signal` — core signal API (default fallback)- `solid-router.solid-router.index` — router package overview- `solid-start.solid-start.index` — SolidStart package overview- `solid-meta.solid-meta.index` — solid-meta package overview## References- `../../tools/gemini-mcp-extension/skill-routing-map.md`- `../../references/solidjs-normalized/manifest.jsonl`- `../../references/solidjs-normalized/taxonomy.json`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lvcoi) — claim your Tome and manage your conversions.

Frequently asked questions