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

Seroprevalence Surveys

ASecurity

Designing and analyzing seroprevalence studies — sampling, assay validation, and adjusting for test performance.

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

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill seroprevalence-surveys --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Seroprevalence Surveys?

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

Security grade badge for Seroprevalence Surveys
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-seroprevalence-surveys/badge)](https://www.skillsdirectory.com/skills/aicodedecode-seroprevalence-surveys)

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: seroprevalence-surveys
description: Designing and analyzing seroprevalence studies — sampling, assay validation, and adjusting for test performance.
category: scientific
---

## Overview

seroprevalence-surveys covers population surveys measuring antibodies (or other biomarkers) to
estimate how many people have been infected or vaccinated. It focuses on the three things that
make or break serosurveys: representative sampling, validated assays, and correct statistical
adjustment for imperfect test sensitivity and specificity.

A serosurvey with a convenience sample and an unvalidated assay produces a number that is worse
than useless — it looks authoritative while being wrong.

## When to use

- Designing serosurveys: sampling frames, sample size, stratification.
- Choosing and validating serologic assays for population use.
- Adjusting seroprevalence for test sensitivity/specificity (Rogan-Gladen).
- Accounting for antibody waning and its effect on estimates.
- Interpreting seroprevalence vs reported cases (the ascertainment ratio).
- Residual-sera vs population-based designs: trade-offs.

## Core concepts

- **Sampling is everything.** Probability-based sampling (stratified random, cluster) from a
  defined population is the gold standard. Convenience samples (blood donors, clinic patients,
  volunteers) are biased in predictable directions — blood donors are healthier, clinic patients
  sicker. If you must use residual sera, characterize the source population and weight to the
  target population.
- **Sample size.** Driven by expected prevalence and desired precision, with design-effect
  inflation for cluster sampling. Low expected prevalence needs larger samples and, critically,
  high-specificity assays (see below).
- **Assay validation for the use case.** Clinical diagnostic validation (sick vs healthy) does
  not equal population-survey validation. You need sensitivity/specificity estimated in samples
  resembling the survey population, including mild/asymptomatic infections and relevant
  cross-reactive conditions. Validate independently — don't trust the kit insert alone.
- **The specificity catastrophe.** At 2% true prevalence, a test with 98% specificity yields
  ~50% false positives among positives. Low-prevalence serosurveys live or die on specificity.
  Mitigations: two-assay orthogonal testing algorithms (screen + confirm), and statistical
  adjustment.
- **Rogan-Gladen adjustment.** True prevalence = (apparent + spec − 1) / (sens + spec − 1).
  Use it always, with uncertainty propagated (Bayesian methods that incorporate uncertainty in
  sens/spec are better than plug-in). Report both apparent and adjusted estimates.
- **Antibody waning.** Seroprevalence underestimates cumulative infection because antibodies
  wane below detection. The longer since the epidemic wave, the bigger the gap. Model waning
  explicitly (using longitudinal assay data) or present estimates as lower bounds with the
  caveat stated.
- **Distinguishing infection from vaccination.** Use assays targeting antigens absent from the
  vaccine (e.g. nucleocapsid vs spike for most COVID vaccines) — or collect vaccination
  histories. Conflating the two answers a different question than the one asked.
- **Ascertainment ratio.** Seroprevalence ÷ reported cases estimates the undercount factor.
  It's a powerful advocacy number but sensitive to all the above errors — present with
  uncertainty.

## Practical workflow

1. **Define the estimand.** Cumulative infection? Recent infection? In which population, at what
   time?
2. **Sample.** Probability-based design, stratified by age/geography; target sample size with
   design effect; plan for non-response (track and weight).
3. **Validate the assay.** Independent validation panel; estimate sens/spec with CIs; consider
   two-assay algorithms for low-prevalence settings.
4. **Collect.** Standardized questionnaire (symptoms, exposures, vaccination); cold-chain and
   lab QC; blinded testing.
5. **Analyze.** Weight to population; Rogan-Gladen/Bayesian adjustment for test performance;
   stratify by age, sex, geography, time; account for waning where data allow.
6. **Report.** Apparent and adjusted prevalence with 95% CIs, assay validation details,
   sampling design and response rates, waning caveats, ascertainment ratio with uncertainty.

Example adjustment sketch:
```r
# Bayesian adjustment propagating sens/spec uncertainty
# apparent ~ Binomial(n, prev*sens + (1-prev)*(1-spec))
# priors on sens, spec from validation study counts
```

## Common pitfalls

- Convenience samples presented as population estimates.
- Unvalidated assays, especially low-specificity tests in low-prevalence settings.
- No adjustment for test performance (reporting apparent prevalence as truth).
- Ignoring antibody waning (underestimating cumulative infections).
- Infection vs vaccination conflated.
- Non-response bias unaddressed (who refuses blood draws is non-random).
- Overprecise estimates from small samples with wide sens/spec uncertainty.

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 →