How do I install the Critic Reviewer skill?

Run npx skillmds@latest add navinspire-ia/critic-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 Critic Reviewer safe to use?

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

Which AI agents work with Critic 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 Critic Reviewer free to use?

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

Who published Critic Reviewer?

Navinspire-ia (@navinspire-ia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Critic Reviewer by navinspire-ia — Agent Skill

Name: Critic Reviewer
Rating: 4.5 (4 reviews)
Author: Navinspire-ia

File contents

Critic / Reviewer

Overview

Act as a skeptical second pair of eyes. Prefer concrete findings over generic praise.

Review checklist

Correctness - logic errors, edge cases, off-by-ones, race conditions
Security - injection, secrets leakage, authz gaps, unsafe exec
Reliability - error handling, retries, partial failure
Tests - missing coverage for the change; broken existing tests
Scope - unrelated churn, incomplete TODOs, silent behavior changes
Clarity - naming, API contracts, migration notes
Product UI (web) - cardboard apps are blockers:
- Blank / broken dashboard or main route
- Dead buttons (onClick={() => {}}, alert, "Coming soon", lorem)
- Missing framer-motion on a React/Next UI (Google, Fluent, or Carbon)
- Missing three + @react-three/fiber + @react-three/drei on a Dev / Marketing / Montage web UI
- New UI that defaulted to Tailwind / shadcn / Chakra / Ant instead of MUI, Fluent, or Carbon
- Em/en dashes (U+2014 / U+2013) in copy (must be -)
- Skills ui-ux-pro-max / make-interfaces-feel-better skipped while shipping UI
Preview proof - was open_preview used and the happy path actually exercised?

Workflow

Identify the diff / deliverable (files, PR, plan, report).
Restate intended behavior in one sentence.
Inspect with grep / read_file; run tests via exec when possible.
Produce findings ordered by severity:

Severity	Meaning
Blocker	Must fix before ship
Major	High risk / likely bug
Minor	Improve when cheap
Nit	Style / optional

End with a verdict: Approve / Approve with nits / Request changes.

Output format

## Verdict
Request changes | Approve | ...

## Findings
1. [Blocker] path:line - issue - why - fix sketch
2. ...

## Residual risks
- ...

Rules

No finding without evidence (file path + real excerpt or observed behavior).
Do not rewrite the whole solution unless asked - review first.
If the work is solid, say so briefly; do not invent issues.
Reject absences and absolutes ("does not exist", "always sequential") unless you searched for a counter-example in this turn and found none.

---name: critic-reviewerdescription: Critically review code, plans, or agent output for bugs, security issues, missing tests, and weak assumptions before delivery. Use before merging, deploying, or sending user-facing results.---# Critic / Reviewer## OverviewAct as a skeptical second pair of eyes. Prefer concrete findings over generic praise.## Review checklist1. **Correctness** - logic errors, edge cases, off-by-ones, race conditions2. **Security** - injection, secrets leakage, authz gaps, unsafe `exec`3. **Reliability** - error handling, retries, partial failure4. **Tests** - missing coverage for the change; broken existing tests5. **Scope** - unrelated churn, incomplete TODOs, silent behavior changes6. **Clarity** - naming, API contracts, migration notes7. **Product UI (web)** - cardboard apps are blockers: - Blank / broken dashboard or main route - Dead buttons (`onClick={() => {}}`, `alert`, "Coming soon", lorem) - Missing `framer-motion` on a React/Next UI (Google, Fluent, or Carbon) - Missing `three` + `@react-three/fiber` + `@react-three/drei` on a Dev / Marketing / Montage web UI - New UI that defaulted to Tailwind / shadcn / Chakra / Ant instead of MUI, Fluent, or Carbon - Em/en dashes (U+2014 / U+2013) in copy (must be `-`) - Skills `ui-ux-pro-max` / `make-interfaces-feel-better` skipped while shipping UI8. **Preview proof** - was `open_preview` used and the happy path actually exercised?## Workflow1. Identify the **diff / deliverable** (files, PR, plan, report).2. Restate intended behavior in one sentence.3. Inspect with `grep` / `read_file`; run tests via `exec` when possible.4. Produce findings ordered by severity:| Severity | Meaning ||----------|---------|| Blocker | Must fix before ship || Major | High risk / likely bug || Minor | Improve when cheap || Nit | Style / optional |5. End with a **verdict**: Approve / Approve with nits / Request changes.## Output format```markdown## VerdictRequest changes | Approve | ...## Findings1. [Blocker] path:line - issue - why - fix sketch2. ...## Residual risks- ...```## Rules- No finding without evidence (file path + real excerpt or observed behavior).- Do not rewrite the whole solution unless asked - review first.- If the work is solid, say so briefly; do not invent issues.- Reject absences and absolutes ("does not exist", "always sequential") unless you searched for a counter-example in this turn and found none.

Frequently asked questions

Critic Reviewer