Back to Skills

write-the-intel-brief

Turn findings into a defensible intelligence product — BLUF key judgements, standardised estimative probability language, per-claim sourcing with timestamps and archived copies, separated observation, inference and assessment, documented negative findings and gaps, chain of custody and hashing, and redaction of uninvolved parties. Use when writing an intelligence report, due-diligence memo, evidence pack or executive summary, or when asked to write up an investigation so it survives challenge. A

13stars1forksUpdated 8/13/2026

Security Assessment

Safe(92/100)
Security Score92/100

About write-the-intel-brief

write-the-intel-brief is a report-writing methodology skill for turning investigation findings into a defensible intelligence product that survives challenge. It targets the specific failure that destroys credibility: a sentence that reads as fact but is actually an inference. The core discipline is sorting every claim into observation, inference, or assessment — kept visually distinct — with verb cues (is/lists/shows vs. indicates/implies vs. we assess/we judge) so conclusions are never smuggled into the evidence.

It then requires per-claim sourcing: each retained claim carries its specific source or exact tool query, a UTC retrieval timestamp, a source-reliability grade, and an archived snapshot, with chain-of-custody and SHA-256 hashing for anything that might become evidence. Reports are written BLUF — lead with the key judgements answering the objective question, each as one sentence carrying an estimative term and a confidence level — on the assumption the reader stops after the first half page. A standardized probability ladder (almost certainly, highly likely, likely, roughly even chance, unlikely, highly unlikely, remote) is used consistently and never mixed with raw percentages, and a reference file lists banned vague terms (possibly, may/might/could, suggests) with better replacements. Probability and confidence are treated as two independent axes, both stated with reasons.

It is aimed at analysts and investigators producing regulated compliance reports, due-diligence and investment-committee memos, litigation and disclosure materials, evidence packs, and law-enforcement referrals. This is a purely defensive, methodology-and-template skill about rigor, sourcing, and honest calibration — it generates no offensive capability and touches no sensitive systems, making it benign.

FAQ

What is the central rule?

Sort every claim into observation, inference, or assessment and keep them distinct, so no inference is ever written in the grammatical form of a fact; any sentence you can't categorize has smuggled a conclusion into the evidence and must be rewritten.

How must sources be handled?

Every retained claim needs a specific source or exact tool query, a UTC retrieval timestamp, a reliability grade, and an archived snapshot; potential evidence additionally needs chain of custody and a cryptographic hash (e.g., sha256sum), with originals kept untouched.

How does it handle uncertainty language?

It mandates a single standardized estimative-probability ladder used consistently, bans vague terms like 'possibly' and 'may/might/could', forbids mixing a probability band with a number in the same sentence, and treats probability and confidence as two separately stated axes.

Who is it for?

Analysts writing intelligence reports, due-diligence and investment-committee memos, evidence packs, executive summaries, litigation and disclosure materials, and law-enforcement referrals that must withstand cross-examination.

All Files

3 files
reference/estimative-language.md5.3 KB
View
SKILL.md12.3 KB
View
reference/report-template.md5.2 KB
View

Install write-the-intel-brief

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill