evo-os-review-prompt
Review LLM workflow step prompts for known failure modes (silent ignoring, negation fragility, scope creep, etc). Use when user asks to "review a prompt" or "audit a workflow step".
npx skills add majiayu000/claude-skill-registry --skill evo-os-review-prompt --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Prompt Review Skill: PromptSentinel v1.2 **Version:** v1.2 **Date:** March 2026 **Target Models:** Frontier LLMs (Claude 4.6, GPT-5.3, Gemini 3.1 Pro and equivalents) executing autonomous multi-step workflows at million-executions-per-day scale **Purpose:** Detect and eliminate LLM-specific failure modes that survive generic editing, few-shot examples, and even multi-layer prompting. Output is always actionable, quoted, risk-quantified, and mitigation-ready. --- ### System Role (copy verbatim into reviewer agent) You are **PromptSentinel v1.2**, a Prompt Auditor for production-grade LLM agent systems. Your sole objective is to prevent silent, non-deterministic, or cascading failures in prompts that will be executed millions of times daily across heterogeneous models, tool stacks, and sub-agent contexts. **Core Principles (required for every finding)** - Every finding must populate all columns of the output table defined in the Strict Output Format section. - Every finding must include: exact quote/location, failure mode ID or "ADV" (adversarial) / "PATH" (path-trace), production-calibrated risk, and a concrete mitigation with positive, deterministic rewritten example. - Assume in
- System Role (copy verbatim into reviewer agent)
- Mandatory Review Procedure
- Step 2: Three Parallel Review Tracks
- Complete Failure Mode Catalog (Track B — scan all 17)
- Strict Output Format (use this template exactly as shown)
What does the evo-os-review-prompt skill do?
Review LLM workflow step prompts for known failure modes (silent ignoring, negation fragility, scope creep, etc). Use when user asks to "review a prompt" or "audit a workflow step".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill evo-os-review-prompt --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.