AnnualReports — Claude Code skill: cybersecurity annual reports
One catalog of cybersecurity annual reports: it finds the report that answers a question, fetches its page, and compares trends across vendors with sources attached.
MIT 1 installs ★ 19,959 updated 2026-10-28
npx skills add danielmiessler/LifeOS --skill annualreports -a claude-codeWhat AnnualReports does
One indexed catalog of annual cybersecurity reports: CrowdStrike, Mandiant, IBM, Verizon, Microsoft, CISA, OWASP, Wiz, Palo Alto and more, sorted into categories such as threat intel, ransomware, breaches, AppSec, cloud, AI, identity and pentest. A seed catalog ships with the skill: 492 reports in 21 categories, so listing and fetching work on a fresh install.
Three modes. UPDATE rewrites Data/sources.json from the awesome-annual-security-reports list on GitHub and prints only counts of added and removed reports. ANALYZE builds a cross-vendor answer where each figure carries vendor, year and report, and names the vendors absent from it. FETCH saves a page summary under Reports/<vendor>/.
The tools are .ts scripts launched with bun, so without bun the commands under Tools/ do not run. No account or secret is needed; most full PDFs sit behind vendor registration, so expect a report page rather than a file. Requests identify themselves as LifeOS-AnnualReports/1.0 with the contact address from Config.md when one is set.
What it helps with
- Pull the Verizon DBIR and get its link
- Compare ransomware numbers across vendors for one year
- Refresh the source catalog from the upstream GitHub list
- Save a vendor report page as a summary
- List which vendors are missing from an analysis
Example prompts for the agent
- Update the annual reports and tell me how many were added and removed.
- Analyze ransomware reports across vendors.
- Fetch the latest IBM report and save the summary.
How to install AnnualReports
1Skills CLI (Vercel)
npx skills add danielmiessler/LifeOS --skill annualreports -a claude-code2Manually: put the files in place
~/.claude/skills/AnnualReports/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/AnnualReports/
1Skills CLI (Vercel)
npx skills add danielmiessler/LifeOS --skill annualreports -a codex2Manually: put the files in place
.agents/skills/AnnualReports/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add danielmiessler/LifeOS --skill annualreports -a cursor2Manually: put the files in place
.cursor/skills/AnnualReports/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install danielmiessler/LifeOS LifeOS/install/skills/AnnualReports2Manually: put the files in place
.github/skills/AnnualReports/SKILL.md1Skills CLI (Vercel)
npx skills add danielmiessler/LifeOS --skill annualreports -a gemini-cli2Platform CLI
gemini skills install https://github.com/danielmiessler/LifeOS --path LifeOS/install/skills/AnnualReportsManually: put the files in place
.devin/skills/AnnualReports/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add danielmiessler/LifeOS --skill annualreports -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about AnnualReports
How do I install AnnualReports in Claude Code?
Run npx skills add danielmiessler/LifeOS --skill AnnualReports -a claude-code. The skill lands at ~/.claude/skills/AnnualReports/SKILL.md.
What does AnnualReports do?
It keeps an index of annual cybersecurity reports and runs in three modes: refreshing the source list, analysing trends across vendors, and fetching one report with a summary.
Does it replace a live threat feed?
No. It works from annual reports, not from event streams or live CVE lookup. Reports also lag: the 2026 editions describe 2025 data.
Source text
SKILL.md · MIT
---
name: AnnualReports
metadata:
short-description: "Find, fetch, update, and analyze cybersecurity annual reports and breach or threat trends. Excludes real-time feeds and live CVE lookup."
version: 1.0.9
evals:
deterministic:
- command: "bun skills/AnnualReports/Tools/UpdateSources.ts --dry-run | grep -Eq 'Total parsed: [1-9]'"
lane: integrity
falsifier: "the upstream README cannot be fetched, or its entry format drifted so the parser yields zero reports"
manual:
reason: "Source freshness and cross-report synthesis depend on the requested live report set and cannot be proven safely from a static fixture."
falsifier: "The delivered analysis omits the consulted reports, attributes a figure to the wrong report year, or leaves a requested fetch unavailable without reporting it."
description: "Aggregate several hundred cybersecurity annual reports from CrowdStrike, Mandiant, IBM, Verizon, Microsoft, CISA, OWASP, Wiz, Palo Alto across 19+ categories (threat intel, ransomware, breaches, AppSec, cloud, AI, identity, pentest). Intents: UPDATE, ANALYZE, FETCH. USE WHEN annual reports, threat reports, vendor reports, ransomware trends, breach stats, DBIR, IBM Cost of Breach, threat landscape, CISO report, CVE trends. NOT FOR real-time threat feeds or live CVE lookup."
---
# AnnualReports - Security Report Aggregation
**Contents:** Ideal State · Anti-criteria · Intent Routing · Tool contract · Data & Config · Gotchas · Examples
Keeps one indexed catalog of several hundred annual cybersecurity reports, fetches the ones that answer a question, and synthesizes trends across vendors with every figure traceable to its source.
**Source:** [awesome-annual-security-reports](https://github.com/jacobdjwilson/awesome-annual-security-reports)
## Ideal State
- UPDATE leaves `Data/sources.json` refreshed from the upstream awesome-annual-security-reports GitHub list, and the counts of added and removed reports are reported.
- FETCH leaves a summary of the requested vendor report page saved under `Reports/<vendor>/`, with a note that most full PDFs need registration, and a listing request returns the reports in the asked category with their direct URLs; a requested fetch that could not be completed is reported as unavailable.
- An ANALYZE answer names the vendors consulted, and also the ones absent from the answer. A ransomware synthesis that skipped Sophos says so, because the gap changes how much weight the numbers carry.
- In an ANALYZE answer, every figure carries its vendor, its year, and the report it came from, and where vendors disagree, the disagreement is named and both numbers stand.
- The publication lag is stated once (2026 reports cover 2025 data) so a trend read isn't mistaken for this-minute data.
## Anti-criteria
- Never silently average disagreeing vendors' numbers into one clean figure that no source actually published.
- Never attribute a figure to the wrong report year, and never ship a stat without its vendor, year and report.
- Never leave a requested fetch unavailable without reporting it.
- Never conflate different vendors' terminology: each vendor has their own threat actor naming conventions.
## Intent Routing
The skill is one intent with three modes, UPDATE, ANALYZE and FETCH, each run through a tool in § Tool contract.
| File | Read when |
|------|-----------|
| `Setup.md` | first install, the optional PREFERENCES.md, proving the tools work |
## Tool contract
| Mode | Trigger | Tool |
|------|---------|------|
| UPDATE | "update the annual reports", refresh report sources from GitHub | `Tools/UpdateSources.ts` |
| ANALYZE | "analyze X reports", trends/insights across vendors | `Tools/ListSources.ts` + content analysis |
| FETCH | "download/fetch report Y", specific vendor report | `Tools/FetchReport.ts` |
```bash
# Update sources from GitHub
bun run ${LIFEOS_SKILL_DIR}/Tools/UpdateSources.ts
# List all sources (no argument prints every category with its current count)
bun run ${LIFEOS_SKILL_DIR}/Tools/ListSources.ts [category]
bun run ${LIFEOS_SKILL_DIR}/Tools/ListSources.ts --search <term> # match vendor or report name
bun run ${LIFEOS_SKILL_DIR}/Tools/ListSources.ts --vendor <name> # every report from one vendor
# Fetch a specific report (vendor and name match as case-insensitive substrings)
bun run ${LIFEOS_SKILL_DIR}/Tools/FetchReport.ts <vendor> <report-name>
bun run ${LIFEOS_SKILL_DIR}/Tools/FetchReport.ts --url <url> # fetch a page not in the catalog
bun run ${LIFEOS_SKILL_DIR}/Tools/FetchReport.ts --list-cached # list summaries already saved under Reports/
```
## Data & Config
Optional user preferences live at `<configRoot>/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/AnnualReports/PREFERENCES.md` (configRoot is `$CLAUDE_CONFIG_DIR` when set, else `~/.claude`). When it exists, apply it over the defaults; when it does not, the defaults stand. The skill needs no account or secret. First install and the proof commands: [Setup.md](Setup.md).
A seed catalog ships with the skill, so ListSources and FetchReport work on a fresh install; UPDATE refreshes it from upstream. If the catalog is deleted, the tools exit with the instruction to run `Tools/UpdateSources.ts`.
- `Data/sources.json` - All report sources with metadata (ships as a seed, rewritten by `Tools/UpdateSources.ts`)
- `Reports/` - Downloaded report files (created by `Tools/FetchReport.ts` on first fetch)
## Gotchas
- **Category counts drift with the upstream list.** `Tools/ListSources.ts` prints the current ones. The shipped seed (parsed 2026-10-14) holds 492 reports across 21 categories.
- **UPDATE reports counts, never entries.** It prints `New reports` and `Removed reports` counts only, and `--diff` lists only new category keys. Report the counts as printed and never present a list of changed entries the tool did not print.
- **A failed fetch saves nothing.** A fetch error, an HTTP error status, a PDF URL or an unknown report prints the reason to stderr and exits 1, with no summary file written. Report the reason as unavailable.
- **Requests declare this tool.** FetchReport sends `LifeOS-AnnualReports/1.0`, plus the `contact` address from `Config.md` when set (see `Setup.md`), so a vendor site can see who is fetching.
## Examples
```
User: "Update the annual reports"
→ UPDATE
→ Data/sources.json matches the upstream README, and the counts of added and removed reports are reported
```
```
User: "What threat reports are available?"
→ FETCH listing
→ The Global Threat Intelligence category's reports, each with its vendor and direct URL
```
```
User: "Analyze ransomware reports"
→ ANALYZE
→ A cross-vendor trend analysis where every figure names its vendor, year and report, and the vendors left out are named
```
© danielmiessler · MIT · danielmiessler/LifeOS