bias-detection-design
Designing review workflows to surface and mitigate bias in AI outputs.
Interpreting implicit and explicit feedback — edits, regenerations, abandonment.
$ npx -y skills add owl-listener/ai-design-skills --skill user-satisfaction-signals --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/user-satisfaction-signalsContext preview
The summary Claude sees to decide when to auto-load this skill.
Interpreting implicit and explicit feedback — edits, regenerations, abandonment.
name: user-satisfaction-signals description: Interpreting implicit and explicit feedback — edits, regenerations, abandonment.
Users rarely tell you directly whether they're satisfied. Most satisfaction signals are implicit — buried in behavior patterns that you have to design systems to capture and interpret.
These are signals users give intentionally:
These are behavioral signals that indicate satisfaction or dissatisfaction: **Positive signals:**
**Negative signals:**
**Ambiguous signals:**
Raw signals need interpretation:
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.