AgentStack
SKILL verified MIT Self-run

Vibe Devil Advocate Review

skill-ash1794-vibe-engineering-devil-advocate-review · by ash1794

Challenges recommendations, designs, or synthesis by adversarial review across 5 dimensions. Use before shipping any significant recommendation or design document.

No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-ash1794-vibe-engineering-devil-advocate-review

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Vibe Devil Advocate Review? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

vibe-devil-advocate-review

Before shipping a recommendation, challenge it. The goal is to find weaknesses BEFORE they become production incidents.

When to Use This Skill

  • Before sending a design document for approval
  • Before shipping a recommendation that combines multiple inputs
  • Before merging a large feature branch
  • When you feel "too confident" about a solution
  • User asks for a review or second opinion

When NOT to Use This Skill

  • Trivial changes (typo fixes, formatting)
  • When the user explicitly says "just ship it"
  • During brainstorming (don't kill ideas before they form)
  • For code review of small PRs (use vibe-quality-loop instead)

The 5 Dimensions

Challenge the work across:

  1. Consistency — Do all parts agree with each other? Are there contradictions?
  2. Completeness — What's missing? What edge cases are unaddressed? What blind spots exist?
  3. Actionability — Is every recommendation concrete and measurable? Can someone actually do this?
  4. Alignment — Does this match the stated goals, constraints, and user needs?
  5. Risk — What could go wrong? What are the second-order effects? What's the blast radius of failure?

Steps

  1. Read the artifact thoroughly — don't skim
  2. For each dimension, actively try to find problems. Assume there ARE problems.
  3. Score each dimension 1-5 (1=critical issues, 5=solid)
  4. List specific issues with evidence
  5. Deliver verdict: APPROVE / REVISE (with required changes) / REJECT (with blocking issues)

Output Format

Devil's Advocate Review

| Dimension | Score | Issues Found | |-----------|-------|-------------| | Consistency | X/5 | [count] | | Completeness | X/5 | [count] | | Actionability | X/5 | [count] | | Alignment | X/5 | [count] | | Risk | X/5 | [count] |

Critical Issues

  1. [Issue with evidence]

Warnings

  1. [Non-blocking concern]

Verdict: APPROVE / REVISE / REJECT

[Rationale]

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.