write-the-intel-brief

Solid

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. Applies to regulated compliance reporting, litigation and disclosure, board and investment committee reporting, and law-enforcement referral. Reference at useosint.com/skills/write-the-intel-brief.

Code & Development 20 stars 2 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
44
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Write the intel brief The report is the only part of the investigation anyone else sees, so it is the only part that can be wrong in public. The failure that destroys credibility isn't a missed source — it's a sentence that reads as fact and is actually an inference. "The account is operated from Lisbon" versus "posting times cluster in UTC+0/+1, consistent with Iberian working hours." One survives cross- examination. ## Step 1 — Sort every claim into observation, inference, or assessment Three categories, never blurred, ideally visually distinct in the text. - **Observation** — what you saw, with source and timestamp. "The registry record retrieved 2024-03-11 lists A. Kestrel as director." - **Inference** — a logical step from observations, with the step shown. "The same registrant email appears on both domains, so they were registered by one party." - **Assessment** — your analytic judgement, carrying probability and confidence. "We assess it is likely the two companies are commonly controlled." Any sentence where you cannot say which category it belongs to is a sentence that has smuggled a conclusion into the evidence. Rewrite it. Verbs betray the category: *is, lists, shows* for observation; *indicates, implies* for inference; *we assess, we judge* for assessment. Watch out for "appears to be", which pretends to be observation and is inference. **Done when** every claim is tagged and no inference is written in the grammatical form of an observation. ## St...

Details

Author
useosint
Repository
useosint/osint-skills
Created
2 weeks ago
Last Updated
2 weeks ago
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

talent-intelligence-brief-writer

Write a self-contained talent-intelligence research brief that can be handed to an analyst with zero prior context. Use this skill whenever the user wants to commission market research, a talent map, a market map, a labor-market or supply/demand study, a competitor headcount/attrition scan, a compensation benchmark, a location/build-vs-buy analysis, or DEI availability data for a hiring decision — even if they just say "find out what the market looks like" or "brief our analyst." Turns a JD + ICP + hiring-manager intake (or whatever the user has) into a precise, decision-anchored research request. Refuses to write a vague "tell me about the market" topic brief.

0 Updated 1 weeks ago
AI-Enablement-Academy
AI & Automation Listed

write-planning-brief

Distill a completed planning discussion and its cited evidence into a durable, plan-ready local brief without reopening the interview. Use at the end of talk-it-through or when a conversation must become reliable input for write-a-prd or to-plan.

18 Updated 2 weeks ago
SrdjanCoric
AI & Automation Listed

sitrep

Report in military brief format, BLUF first. Use whenever the user says "investigate", "report", "resolve", "assess", "tell me", "what happened", "status", or sends a screenshot expecting you to read and act on it. Enforces bottom line in the first sentence, bad news above good news, evidence beside every claim, stated confidence, and a named gap for anything unverified. Run clarity.py before sending.

0 Updated yesterday
openhonest