Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Outbreak Investigation

ASecurity

Field epidemiology outbreak response — case definitions, epidemic curves, analytic studies, and control measures.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgotestingdatabase

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill outbreak-investigation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Outbreak Investigation?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Outbreak Investigation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-outbreak-investigation/badge)](https://www.skillsdirectory.com/skills/aicodedecode-outbreak-investigation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: outbreak-investigation
description: Field epidemiology outbreak response — case definitions, epidemic curves, analytic studies, and control measures.
category: scientific
---

## Overview

outbreak-investigation covers the classic field-epidemiology sequence for responding to disease
outbreaks: verifying the outbreak, establishing case definitions, describing by time/place/person,
generating hypotheses, testing them analytically, and implementing control measures. It follows the
CDC's established steps while emphasizing the judgment calls — particularly when data are
incomplete and decisions can't wait for perfect evidence.

## When to use

- Responding to a cluster of illness: is this an outbreak?
- Writing case definitions (confirmed/probable/suspected) with the right sensitivity-specificity
  trade-off.
- Building epidemic curves and interpreting their shapes.
- Descriptive epidemiology: time, place, person analyses.
- Analytic studies: retrospective cohort and case-control for identifying sources.
- Implementing and evaluating control measures.
- Writing outbreak reports and after-action reviews.

## Core concepts

- **Verify first.** Confirm the diagnosis (lab confirmation on initial cases), confirm the
  outbreak (cases exceed expected — check baseline rates, changes in surveillance, diagnostic
  practices, and population denominators before declaring one). Many "outbreaks" are surveillance
  artifacts.
- **Case definitions.** Clinical + laboratory + epidemiologic criteria, with tiers:
  suspected (sensitive, for case finding), probable (clinical + epi link), confirmed (lab).
  Definitions evolve as knowledge grows — version and date every revision, and reclassify cases
  when definitions change.
- **Line lists.** One row per case: identifiers, demographics, onset date, symptoms, exposures,
  lab results, outcome. The line list is the outbreak database — build it early, update it
  continuously, protect it.
- **Epidemic curves.** Histogram of onset dates. Point-source (single peak, narrow), continuous
  common-source (plateau), propagated (successive taller peaks one incubation period apart).
  The curve's shape is often the fastest hypothesis generator — learn to read it.
- **Time/place/person.** Person: attack rates by age, sex, occupation, risk factors. Place: spot
  maps, attack rates by location/ward/table. Time: epi curve. Attack rates (ill/exposed) are the
  core descriptive measure — always with denominators.
- **Hypothesis generation.** Case interviews (open-ended initially, then focused questionnaires),
  site visits, and the descriptive patterns. Talk to the first few cases in depth — they often
  reveal the exposure.
- **Analytic testing.** Retrospective cohort (defined exposed population: compute attack rates
  and relative risks per exposure — e.g. food items at a banquet) or case-control (no defined
  population: odds ratios). For foodborne outbreaks, the cohort design with food-specific attack
  rates is standard; stratify to handle confounding between foods eaten together.
- **Control measures.** Source-directed (remove the vehicle, close the venue), transmission-
  directed (isolation, hygiene, vector control), and host-directed (prophylaxis, vaccination).
  Implement on epidemiologic evidence — waiting for definitive proof while people get sick is a
  failure, but document the evidence basis for each measure.
- **Communication.** Regular updates to stakeholders, public messaging that's honest about
  uncertainty, and a final report with lessons learned. Outbreaks are public events; the
  epidemiology is only half the job.

## Practical workflow

1. **Prepare.** Assemble team, review background rates, gather case reports.
2. **Verify.** Confirm diagnoses; compare against expected numbers.
3. **Case definition + case finding.** Draft definition; find cases actively (not just
   passively reported ones — mild cases are systematically missed).
4. **Line list.** Build and maintain; assign onset dates carefully (onset, not report date).
5. **Describe.** Epi curve, spot map, attack rates by person/place/time.
6. **Hypothesize.** From descriptive patterns + case interviews + site knowledge.
7. **Test.** Cohort or case-control study; compute RR/OR with CIs; consider dose-response.
8. **Control.** Implement measures matched to the evidence; monitor the epi curve for effect.
9. **Report.** Methods, findings, control measures, lessons; archive data for future outbreaks.

## Common pitfalls

- Declaring an outbreak from a surveillance artifact (new test, new reporting rule).
- Onset dates replaced by report dates (distorts the epi curve).
- Case definitions that drift without versioning.
- Passive case finding missing mild cases (biases severity and attack rates).
- Confounded food analyses (eaten-together items) without stratification.
- Waiting for perfect evidence before control measures.
- No final report — the next outbreak team relearns everything.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →