User Satisfaction Signals

Interpreting implicit and explicit feedback — edits, regenerations, abandonment.

207 stars 37 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/ai-design-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/ai-design-skills --skill user-satisfaction-signals
Manual install
git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git /tmp/ai-design-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ai-design-skills/claude-plugin/evaluation/skills/user-satisfaction-signals ~/.claude/skills/user-satisfaction-signals

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# User Satisfaction Signals
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.
## Explicit Satisfaction Signals
These are signals users give intentionally:
- **Thumbs up/down**: Direct quality rating
- **Star ratings**: Graded satisfaction
- **Written feedback**: Comments about what worked or didn't
- **NPS or satisfaction surveys**: Periodic overall assessment
- **Feature requests**: Signals of engagement even when expressing a gap
## Implicit Satisfaction Signals
These are behavioral signals that indicate satisfaction or dissatisfaction:
**Positive signals:**
- Using the output as-is (no edits)
- Copying the output
- Returning to use the feature again
- Increasing usage over time
- Trying more advanced features
**Negative signals:**
- Regenerating the response (asking the AI to try again)
- Editing the output heavily
- Rephrasing the same request multiple times
- Abandoning mid-task
- Decreasing usage over time
- Switching to manual methods
**Ambiguous signals:**
- Long sessions (engaged or struggling?)
- Many turns (deep work or frustrated iteration?)
- Silence after a response (satisfied or confused?)
## Designing Signal Collection
- **Instrument the product**: Track edits, regenerations, copy events, session duration, and return patterns
- **Minimise explicit feedback burden**: Don't ask for ratings on every response
Read the full skill on GitHub

Details

Skill name
user-satisfaction-signals
Path
claude-plugin/evaluation/skills/user-satisfaction-signals/SKILL.md
License
MIT
Repo updated
9 June 2026

FAQ

What does the User Satisfaction Signals skill do?

Interpreting implicit and explicit feedback — edits, regenerations, abandonment.

How do I install the User Satisfaction Signals skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/ai-design-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is User Satisfaction Signals popular?

It lives in Owl-Listener/ai-design-skills, which has 207 GitHub stars and 37 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.