Skip to content
Back to skills

Privacy Threat Model

ASecurity

Threat-model privacy harms including overcollection, linkage, inference, unauthorized secondary use, excessive retention, disclosure, re-identification, and abusive insider/tool access.

  • 16 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 11, 2026
ai-agentsrust

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add Dadmin88/hermes-profile-packs --skill privacy-threat-model --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Privacy Threat Model?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Privacy Threat Model
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dadmin88-privacy-threat-model/badge)](https://www.skillsdirectory.com/skills/dadmin88-privacy-threat-model)

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

Download with Pro
SKILL.md
---
name: privacy-threat-model
description: Threat-model privacy harms including overcollection, linkage, inference, unauthorized secondary use, excessive retention, disclosure, re-identification, and abusive insider/tool access.
---
# Privacy Threat Model

Use when this procedure is the primary professional method needed for the assignment.

## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using data flow map, threat actors, analytics/model behavior, access roles, exports, vendors, and product features. Do not fill material gaps with assumptions when they can change the result.
3. Identify people/data/purposes, map trust boundaries and powerful joins, enumerate misuse/accidental paths, score harms and detectability, then design minimization and control mitigations.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

## Quality gate
Mitigations reduce privacy harm at the data or architecture layer rather than relying only on policy text.

Attribution

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

Loading comments…