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

Bias Fairness Assessment

ASecurity

Assess an AI model, feature, or dataset for bias and fairness across groups — representational and allocative harms, disparate performance, and skewed refusals — using appropriate fairness metrics, and recommend mitigations. Use when evaluating whether an AI system treats people equitably.

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

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add jassics/awesome-claude-security --skill bias-fairness-assessment --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Bias Fairness Assessment?

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

Security grade badge for Bias Fairness Assessment
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jassics-bias-fairness-assessment/badge)](https://www.skillsdirectory.com/skills/jassics-bias-fairness-assessment)

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: bias-fairness-assessment
description: >-
  Assess an AI model, feature, or dataset for bias and fairness across groups —
  representational and allocative harms, disparate performance, and skewed
  refusals — using appropriate fairness metrics, and recommend mitigations. Use
  when evaluating whether an AI system treats people equitably.
---

# Goal

A fairness assessment that identifies where the system performs or behaves
disparately across groups, quantifies it with suitable metrics, and proposes
mitigations — distinguishing the *type* of harm.

# Frame the harm type first

- **Allocative** — the system influences resource/opportunity decisions (hiring,
  lending, housing, moderation, healthcare). Fairness of *outcomes* matters most.
- **Representational** — the system depicts/describes groups (stereotyping,
  erasure, demeaning content, quality-of-service gaps). Fairness of *treatment*.

# Steps

1. **Identify groups and context** — protected/sensitive attributes relevant to the
   use case and jurisdiction; note intersectional groups. Define what "fair" means
   *here* (it's context-dependent and metrics can conflict).
2. **Choose metrics** to match the harm:
   - Allocative: demographic parity, equalized odds, equal opportunity, predictive
     parity, calibration — pick by which error is most harmful; they trade off.
   - Representational/generative: disparate refusal rate, sentiment/toxicity skew,
     stereotype rate, quality (accuracy/helpfulness) parity across groups.
3. **Measure** on a representative, consented dataset (watch for unrepresentative or
   skewed data — that's itself a finding). Report gaps with confidence.
4. **Diagnose sources** — data imbalance, label bias, proxy features, objective
   mismatch, feedback loops.
5. **Recommend mitigations** — data/representation fixes, reweighting/constraints,
   threshold adjustment, post-processing, human review, scope limits — and note
   residual disparity and metric trade-offs.

# Output

A fairness report: harm type · groups · metric · measured disparity · likely source
· mitigation · residual/trade-off. Use `security-reporting`; visualize gaps with
`security-diagramming:infographic`.

# Notes

There is no single "fair" — metrics conflict and the right choice depends on which
error harms people most in this context. State the chosen definition and why.
Beware proxies: removing a protected attribute doesn't remove bias carried by
correlated features.

Attribution

jassicsjassics
View sourceSee grades on GitHubMore from jassics →
SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

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 Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

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

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

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
View all in ai-agents →