abuseipdb-api
FreeAbuseIPDB API reference. IP reputation and abuse report lookups.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.
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.
Deliberately and rigorously construct the best possible case AGAINST the prevailing judgment:
Honestly evaluate:
## 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]
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
AbuseIPDB API reference. IP reputation and abuse report lookups.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Censys API v2 reference. Host reconnaissance and certificate data.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.