agentleFS
Sign inStart free
griffinhillygriffinhilly/claude-code-synthesis/skills/red-team/SKILL.md

red-team

Skill67 starsChanged 4 months agoMITView on GitHub

Adversarial stress-test of code, a plan, or an argument. Three critics attack, one defender rebuts, a referee judges, then a hostile auditor attacks the synthesis itself.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use architecture, wizard and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 3 projects that use this

  • AWSSkill

    wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

    Also in 3 projects that use this

  • GoogleSkill

    codebase-design

    Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

    Also in 4 projects that use this

  • GoogleSkill

    domain-modeling

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

    Also in 4 projects that use this

  • MicrosoftSkill

    grill-with-docs

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 5 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the dialectic-review skill in review mode with the hostile auditor enabled by default.

    line 11
  2. Very specific:

    If $ARGUMENTS contains --no-audit — run /dialectic-review $ARGUMENTS (strip --no-audit before passing through.

    line 16
  3. Very specific:

    Follow the full three-phase review process, then the Phase 4 Hostile Auditor defined in the dialectic-review SKILL.md.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Red Team

Run the dialectic-review skill in review mode with the hostile auditor enabled by default. Read ~/.claude/skills/dialectic-review/SKILL.md for argument parsing and ~/.claude/skills/dialectic-review/review-prompts.md for the phase prompts. Any /dialectic-review flag is valid here — it passes straight through.

Audit default: Unless the user passed --no-audit in $ARGUMENTS, append --audit to the invocation. This is what differentiates /red-team from plain /dialectic-review --mode review: red-team always closes the loop by attacking its own synthesis.

Invocation:

  • If $ARGUMENTS contains --no-audit — run /dialectic-review $ARGUMENTS (strip --no-audit before passing through; plain review mode, no auditor).
  • Otherwise — run /dialectic-review --audit $ARGUMENTS.

Follow the full three-phase review process, then the Phase 4 Hostile Auditor defined in the dialectic-review SKILL.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free