Menu

Individual skill

feedback-loops

0upvotes

User correction, thumbs up/down, inline editing, and reinforcement signals.

skills/model-interaction-design/feedback-loops/SKILL.md

Read pinned source

Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
203
Repository last updated
Jun 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Feedback Loops
Feedback loops are how users tell the AI what's working and what isn't. Designing these loops well is the difference between an AI that improves over time and one that repeats the same mistakes.
## Types of Feedback
- **Explicit feedback**: Thumbs up/down, star ratings, "this was helpful/not helpful" buttons
- **Implicit feedback**: Regeneration (user asks again), editing (user modifies the output), abandonment (user leaves)
- **Corrective feedback**: User provides the right answer ("No, I meant X not Y")
- **Preference feedback**: User chooses between alternatives ("I prefer option B")
- **Contextual feedback**: Feedback tied to a specific part of the output, not the whole response
## Designing for Correction
The most valuable feedback is correction — but it's also the hardest to design for:
- **Inline editing**: Let users edit AI output directly. Track what they change.
- **Partial acceptance**: Let users keep some parts and reject others.
- **Explanation requests**: "Why did you do it this way?" — the user's question reveals what went wrong.
- **Redo with guidance**: "Try again but make it more formal" — correction through re-prompting.
## Feedback Timing
Back to top