How do I install the Solid Reviewer skill?

Run npx skillmds@latest add tomevault-io/solid-reviewer 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 Reviewer safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Solid Reviewer?

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 Reviewer free to use?

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

Who published Solid Reviewer?

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

Solid Reviewer by tomevault-io — Agent Skill

Name: Solid Reviewer
Author: tomevault-io

Solid Reviewer

Review SolidJS diffs for correctness, reactivity safety, SSR/hydration risk, and maintainability with deterministic severity ordering. Use when auditing PRs or producing final review findings. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

solid-reviewer

Trigger

Use this skill for PR/diff audits where findings must be prioritized and mapped to concrete remediation.

Required Inputs

Diff or changed files.
Runtime context (client, SSR, SolidStart server usage if applicable).
Known risk constraints (performance budget, accessibility requirements, release urgency).

Workflow

Triage by severity in strict order: correctness, performance, maintainability, accessibility.
Validate reactive boundaries first: derivations vs effects, dependency explosion, stale closures.
Evaluate control flow and async completeness (loading, empty, error, success).
Check SSR/hydration and browser-only assumptions in render paths.
Ensure every finding includes file reference and concrete fix direction.
Return validation commands relevant to touched surface.

Failure Modes

Missing diff context: fail and request files or patch.
Findings without reproducible impact: downgrade to question or remove.
Suggestions without file-level anchor: invalid until anchored.
No findings detected: explicitly state "No findings" and list residual test gaps.

Output Contract

Return output matching ReviewOutput schema at ../../skills/contracts/review-output.schema.json with:

summary, findings, open_questions, validation_commands.
findings ordered by severity and containing file (and line when available).
citations: every standards claim must include normalized doc_id + claim.

Validation

node tools/scripts/validate-skills.mjs --skill solid-reviewer
node tools/scripts/validate-output-contracts.mjs

References

../../references/solidjs-normalized/manifest.jsonl
../../references/solidjs-normalized/taxonomy.json
../../references/solidjs/review-checklist.md
../../references/solidjs/control-flow.md
../../references/solidjs/performance-ssr.md

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

---name: solid-reviewerdescription: Review SolidJS diffs for correctness, reactivity safety, SSR/hydration risk, and maintainability with deterministic severity ordering. Use when auditing PRs or producing final review findings. Use when this capability is needed.---# solid-reviewer## TriggerUse this skill for PR/diff audits where findings must be prioritized and mapped to concrete remediation.## Required Inputs- Diff or changed files.- Runtime context (client, SSR, SolidStart server usage if applicable).- Known risk constraints (performance budget, accessibility requirements, release urgency).## Workflow1. Triage by severity in strict order: correctness, performance, maintainability, accessibility.2. Validate reactive boundaries first: derivations vs effects, dependency explosion, stale closures.3. Evaluate control flow and async completeness (`loading`, `empty`, `error`, `success`).4. Check SSR/hydration and browser-only assumptions in render paths.5. Ensure every finding includes file reference and concrete fix direction.6. Return validation commands relevant to touched surface.## Failure Modes- Missing diff context: fail and request files or patch.- Findings without reproducible impact: downgrade to question or remove.- Suggestions without file-level anchor: invalid until anchored.- No findings detected: explicitly state "No findings" and list residual test gaps.## Output ContractReturn output matching `ReviewOutput` schema at `../../skills/contracts/review-output.schema.json` with:- `summary`, `findings`, `open_questions`, `validation_commands`.- `findings` ordered by severity and containing `file` (and `line` when available).- `citations`: every standards claim must include normalized `doc_id` + `claim`.## Validation- `node tools/scripts/validate-skills.mjs --skill solid-reviewer`- `node tools/scripts/validate-output-contracts.mjs`## References- `../../references/solidjs-normalized/manifest.jsonl`- `../../references/solidjs-normalized/taxonomy.json`- `../../references/solidjs/review-checklist.md`- `../../references/solidjs/control-flow.md`- `../../references/solidjs/performance-ssr.md`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lvcoi) — claim your Tome and manage your conversions.

Frequently asked questions