write-the-intel-brief
SolidTurn 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.
Install
Quality Score: 81/100
Skill Content
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
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.
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.
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.