Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Ethics Data Audit

ASecurity

Audit a data collection, retention, or sharing decision against ethical standards. Use when the user is making decisions about what data to collect, how long to keep it, who can access it, or who it's shared with. TRIGGERS: 'audit this data decision', 'is this data practice ok', 'data ethics check', any change to data models, privacy controls, analytics instrumentation, data sharing agreements, or retention policies. Goes beyond legal compliance — evaluates whether the practice is ethical, no...

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsrustgo

Works with

cli

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill ethics-data-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ethics Data Audit?

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

Security grade badge for Ethics Data Audit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-ethics-data-audit/badge)](https://www.skillsdirectory.com/skills/rondoflow-ethics-data-audit)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: ethics-data-audit
description: "Audit a data collection, retention, or sharing decision against ethical standards. Use when the user is making decisions about what data to collect, how long to keep it, who can access it, or who it's shared with. TRIGGERS: 'audit this data decision', 'is this data practice ok', 'data ethics check', any change to data models, privacy controls, analytics instrumentation, data sharing agreements, or retention policies. Goes beyond legal compliance — evaluates whether the practice is ethical, not just lawful."
---

# Ethics Data Audit

Legal compliance sets the floor. This audit asks whether your data practices clear a higher bar: are they *ethical*?

The distinction matters. GDPR-compliant practices can still be extractive. Lawful data collection can still violate trust. This audit evaluates data decisions through two lenses that legal frameworks tend to underweight: **deontological** (what do users have a right to, regardless of what the terms allow?) and **care ethics** (what do you owe the people whose data you hold, given the relationship and the vulnerability involved?).

---

## Your Process

**Step 1: Define the data practice**
What data is being collected, retained, shared, or used? Be specific: what fields, what volume, what purpose, who can access it, how long is it kept, where does it go?

**Framing check:** Confirm the specific data practice before continuing. State what you've identified — the actual data being handled, its stated purpose, and the decision or change under review — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the data practice, its purpose, and the decision being audited]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Deontological Assessment — Rights and Duties**
Users have rights that don't disappear because they clicked "I agree." Examine:

- **Informed consent**: Do users genuinely understand what's being collected and why? Would they understand if you explained it plainly, without legal language?
- **Purpose limitation**: Is the data being used only for the purpose users would reasonably expect?
- **Right to exit**: Can users meaningfully withdraw, delete, or limit their data? Is that easy or deliberately difficult?
- **Data as means**: Is data being used to serve users — or to serve the business *at the expense of* users?

Flag any duty being violated, even if legally covered.

**Step 3: Care Ethics Assessment — Relationship and Vulnerability**
Data relationships are not neutral transactions. Examine:

- **Asymmetry**: The organisation knows vastly more about users than users know about the organisation. Does the practice exploit that asymmetry?
- **Vulnerability**: Are any users in this dataset particularly vulnerable (minors, people under financial stress, people in sensitive contexts)? Does the practice account for that?
- **Trust**: If users knew exactly what you were doing with their data, would they feel the relationship was honourable?
- **Harm potential**: What is the worst plausible outcome if this data were breached, misused, or sold? Who bears that harm?

**Before synthesising:** State what each method surfaced in one sentence each. Use `AskUserQuestion`:
- **Question:** "Here's what each method found: [one bullet for deontological findings — the duties most at risk; one bullet for care ethics findings — the relationship and vulnerability concerns most at risk]. Before I synthesise into a verdict, does any direction stand out, or is anything missing?"
- **Header:** "Synthesis direction"
- **Options:**
  - **Synthesise as planned** — methods covered the ground
  - **Weight deontological concerns** — user wants rights and duties to lead the verdict
  - **Weight care ethics concerns** — user wants relationship and vulnerability to lead the verdict
  - **Add a missing angle** — user will name a dimension not yet covered

**Step 4: Produce the audit**

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Consent and harm potential only** — Skip necessity, proportionality, and retention sections
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output Format

**Data Practice Being Audited:**
[What data, what purpose, what handling]

**Deontological Findings**
| Duty/Right | Status | Notes |
|---|---|---|
| Informed consent | ✅ / ⚠️ / ❌ | [explanation] |
| Purpose limitation | ✅ / ⚠️ / ❌ | [explanation] |
| Right to exit | ✅ / ⚠️ / ❌ | [explanation] |
| Data as means | ✅ / ⚠️ / ❌ | [explanation] |

**Care Ethics Findings**
| Dimension | Status | Notes |
|---|---|---|
| Power asymmetry | ✅ / ⚠️ / ❌ | [explanation] |
| Vulnerable populations | ✅ / ⚠️ / ❌ | [explanation] |
| Trust test | ✅ / ⚠️ / ❌ | [explanation] |
| Harm potential | ✅ / ⚠️ / ❌ | [explanation] |

**Verdict**
[2–3 sentences: is this practice ethical, what are the key concerns, what would need to change]

**Recommended Actions**
- [Specific change or safeguard, if any]

---

## Notes

This audit does not replace legal review. It supplements it. A practice can pass this audit and still require legal sign-off. A practice that fails this audit should not be excused by legal compliance.

If the audit turns up significant concerns, consider escalating to `ethics-council` for a full multi-framework analysis.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Data practices audited. What's next?"
- **Header:** "Next"
- **Options:**
  - `/ethics-consent-review` — Review consent for data practices found in the audit
  - `/ethics-impact-scan` — Scan broader impact of the data practices
  - `/logic-check` — Validate the reasoning about data use
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 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', ...

693161 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.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, 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.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →