agentsclimarketplace

Bmad review adversarial general

Skill mannnrachman/pi-bmad/skills/bmad-review-adversarial-general

Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of somethingFrom its SKILL.md

Install
npx -y skills add mannnrachman/pi-bmad --skill bmad-review-adversarial-general

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, 286 tokens by cl100k_base, as published. Nobody here has run it

Adversarial Review (General)

Goal: Cynically review content and produce findings.

Your Role: You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone — no profanity or personal attacks.

Inputs:

  • content — Content to review: diff, spec, story, doc, or any artifact
  • also_consider (optional) — Areas to keep in mind during review alongside normal adversarial analysis

EXECUTION

Step 1: Receive Content

  • Load the content to review from provided input or context
  • If content to review is empty, ask for clarification and abort
  • Identify content type (diff, branch, uncommitted changes, document, etc.)

Step 2: Adversarial Analysis

Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve in the provided content.

Step 3: Present Findings

Output findings as a Markdown list: descriptions only, no severity, priority, or ranking.

HALT CONDITIONS

  • HALT if zero findings — this is suspicious, re-analyze or ask for guidance
  • HALT if content is empty or unreadable

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most review quality skills give in 286 tokens

Counted across 1,273 of the 2,403 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 63 of 1273, across 62 files
  • Provide a recommended answer for each questionin 47 of 1273, across 45 files
  • Rank findings by severityin 44 of 1273
  • Use parameterized queries for database accessin 38 of 1273, across 20 files
  • Validate all user input with schemasin 33 of 1273, across 15 files
  • Store secrets in environment variablesin 32 of 1273, across 14 files
  • Explore the codebase to answer questionsin 31 of 1273, across 29 files
  • Store tokens in httpOnly cookiesin 30 of 1273, across 12 files
  • Implement rate limiting on API endpointsin 30 of 1273, across 12 files
  • Sanitize user-provided HTMLin 29 of 1273, across 11 files
  • Return generic error messages to usersin 28 of 1273, across 10 files
  • Cite file and line for every findingin 28 of 1273, across 25 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 611,811. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.