
user-satisfaction-signals
Interpreting implicit and explicit feedback — edits, regenerations, abandonment.
- Installs
- 127
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/ai-design-skills --skill user-satisfaction-signals- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads user-satisfaction-signals automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Contextualise signals: A regeneration during creative brainstorming means something different than a regeneration during fact-finding
- Segment by task type: Satisfaction patterns vary by what the user is trying to do
- Combine signals: No single signal is reliable. Look for patterns across multiple signals.
From Signals to Insights
Raw signals need interpretation:
- Signal clustering: Which negative signals appear together? That pattern indicates a specific problem.
- Trend analysis: Are signals improving or degrading over time?
- Cohort comparison: Do new users show different signals than experienced users?
- Correlation with outcomes: Which signals best predict task success or retention?
Design Artefacts
- Signal inventory (explicit and implicit) with collection methods
- Signal interpretation guidelines
- Satisfaction dashboard specifications
- Signal-to-insight analysis frameworks
- Feedback collection touchpoint map
FAQ
What does the user-satisfaction-signals skill do?
Interpreting implicit and explicit feedback — edits, regenerations, abandonment.
How do I install user-satisfaction-signals?
Run npx skills add https://github.com/owl-listener/ai-design-skills --skill user-satisfaction-signals in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/user-satisfaction-signals/ (personal) or .claude/skills/user-satisfaction-signals/ (project).
Which AI agents can use user-satisfaction-signals?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is user-satisfaction-signals safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains user-satisfaction-signals?
It is published by owl-listener in owl-listener/ai-design-skills. It has 127 recorded installs.
More from owl-listener/ai-design-skills
system-prompt-structure
owl-listener/ai-design-skills
Anatomy of effective system prompts — role, context, constraints, format.
guardrail-design
owl-listener/ai-design-skills
Open the skill to read its SKILL.md instructions.
constraint-specification
owl-listener/ai-design-skills
Defining output format, length, tone, and content boundaries within prompts.
generative-ui
owl-listener/ai-design-skills
Designing interfaces where AI generates UI components dynamically.
conversation-patterns
owl-listener/ai-design-skills
Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.
progressive-disclosure
owl-listener/ai-design-skills
Revealing AI capability gradually to match user mental models.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.