bias-detection-design
Designing review workflows to surface and mitigate bias in AI outputs.
Defining what "good" looks like for AI outputs — accuracy, relevance, helpfulness.
$ npx -y skills add owl-listener/ai-design-skills --skill output-quality-rubrics --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/output-quality-rubricsContext preview
The summary Claude sees to decide when to auto-load this skill.
Defining what "good" looks like for AI outputs — accuracy, relevance, helpfulness.
name: output-quality-rubrics description: Defining what "good" looks like for AI outputs — accuracy, relevance, helpfulness.
Without a rubric, quality evaluation is subjective and inconsistent. A rubric defines what "good" means in concrete, measurable terms — so different evaluators reach the same conclusions.
For each dimension, define a scale: **Example — Accuracy (1-5):**
Not all dimensions matter equally for every use case:
Define weights when creating the rubric. Make the priorities explicit.
A rubric is only useful if evaluators use it consistently:
Part of the Designer Skills suite. Install this collection and four more with one command in Claude Code: /plugin marketplace add Owl-Listener/designer-skills This repo still works on its own. The suite just gives everyone one front door.
Designing review workflows to surface and mitigate bias in AI outputs.
Designing for informed user consent, opt-out, and human override.
When and how AI should escalate to humans, refuse, or ask for clarification.
Defining behavioral boundaries — what the AI should and shouldn't do.
Proactively identifying failure modes, misuse, and unintended consequences.
Showing users what the AI knows, doesn't know, and how confident it is.