本文へ移動
cccskills
無料GitHub で公開

devils-advocacy

Use when challenging a prevailing analytical judgment, the user asks "what is the opposing case?" / "argue the other side" / "play devil's advocate", or wants an assessment stress-tested before release. Takes the team's own lead judgment and builds the strongest case that it is wrong. A contrarian technique. It does not model what an adversary would do next, which is Red Team Analysis. Formerly /red-team-analysis.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Devil's Advocacy

A contrarian technique from the CIA Tradecraft Primer. It takes the team's own lead judgment as its input and argues that the judgment is wrong. Its output is a rebuttal.

It is not Red Team Analysis. Red teaming is an imaginative technique: it reasons as the adversary would, from the adversary's position and constraints, and produces adversary courses of action. This pack does not have a Red Team Analysis skill. Until version 2.0 this skill carried that name.

When consensus is strong, this technique deliberately argues the opposing position. The goal is not to be contrarian for its own sake — it's to find genuine weaknesses in the prevailing analysis before they become blind spots.

When to Use

  • Consensus is strong and unchallenged
  • High-stakes assessment (wrong conclusion = significant harm)
  • Analysis has been produced quickly under pressure
  • The same team that collected also analysed (potential tunnel vision)
  • Before publishing a product that will drive significant decisions

Procedure

Step 1: State the Prevailing Judgment

Write the current analytical consensus clearly and completely. Where the judgment rests on graded evidence from /quality-of-information-check, take the claim table with it: the weakest load-bearing claim is the first place to press.

Step 2: Argue Against It (With Maximum Effort)

Deliberately and rigorously construct the best possible case AGAINST the prevailing judgment:

  • What evidence is being overweighted?
  • What alternative explanations exist for the same evidence?
  • What evidence has been ignored or underweighted?
  • What assumptions are vulnerable? (cross-reference with key-assumptions-check)
  • What would a sophisticated adversary do to make us believe the prevailing judgment?
  • What historical cases looked similar but turned out differently?

Step 3: Assess the Opposing Case

Honestly evaluate:

  • Are any of the opposing arguments compelling enough to change the judgment?
  • Do they warrant lowering the confidence level?
  • Do they identify intelligence gaps that should be filled?
  • Do they suggest alternative hypotheses that should be tracked?

Step 4: Report

## Devil's Advocacy: [Prevailing Judgment]

### Prevailing Judgment
[The assessment being challenged]

### The Case Against
[The best case against the prevailing judgment]

#### Overweighted Evidence
- [Evidence that may be given too much weight, and why]

#### Alternative Explanations
- [Alternative explanations for the same evidence]

#### Ignored/Underweighted Evidence
- [Evidence pointing away from the prevailing judgment]

#### Vulnerable Assumptions
- [Assumptions the prevailing judgment depends on]

### Assessment of the Case Against
[How compelling is it?]
- **Compelling**: Prevailing judgment should be revised
- **Partially compelling**: Confidence should be lowered
- **Not compelling**: Prevailing judgment stands, but the exercise identified useful intelligence gaps

### Recommendations
- [Actions: revise judgment, lower confidence, collect against gaps, track alternative hypothesis]

Rules

  • Argue with genuine effort — a weak devil's advocate is worse than none
  • Separate the devil's advocate from the original analysis (different perspective, ideally different analyst)
  • The findings must be incorporated into the final product
  • A strong case against doesn't mean the original was wrong — it means we're more confident (or appropriately less confident) in the result

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

AbuseIPDB API reference. IP reputation and abuse report lookups.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

ach

無料

Analysis of Competing Hypotheses — structured technique for evaluating multiple explanations against evidence. Use when facing ambiguous attribution or multiple plausible scenarios. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Runs on ungraded evidence when asked, labelled as such, unweighted, and capped at Moderate confidence.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Use when documenting a named campaign across time and victims, the user asks to start or update a campaign record, or another skill identified a multi-incident cluster that warrants formal tracking. Provides the template (timeline, attribution, victimology, attack chain, Diamond Model mapping, IOC clusters) and the lifecycle from active to historical.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Use when the user asks about carding, BIN attacks, payment-card breach markets, fullz/CVV2 trade, autoshops (BidenCash, Brian's Club, Russianmarket, B1ack's Stash), or financial-fraud TTPs. Self-updating knowledge cell.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Censys API v2 reference. Host reconnaissance and certificate data.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Use when the user asks about Chinese state-sponsored cyber operations or specific PRC-aligned actors (APT41, Volt Typhoon, Mustang Panda, APT10, APT31, Salt Typhoon, etc.), MSS/PLA-attributed campaigns, or PRC sector targeting. Self-updating knowledge cell.

日本語の概要は準備中です。原文の説明を表示しています。

Liberty91LTD/cti-skills272026年9月30日 更新

Liberty91LTD のスキルをすべて見る

このスキルの問題を報告する