feedback-writer

Records user corrections and Skill execution failures as structured feedback entries with capability scores.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/iJosueeh/amauta --skill feedback-writer-ijosueeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback-writer
Source: https://github.com/iJosueeh/amauta/tree/main/.opencode/skills/feedback-writer
Command: npx skills add https://github.com/iJosueeh/amauta --skill feedback-writer-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When users correct AI behavior or a Skill execution fails, those signals are usually lost. This Skill captures them as structured, deduplicated feedback entries with quantitative scores so an evolution engine can later turn them into concrete improvements. ## Core Features & Use Cases - Signal Detection & Recording: Identifies five signal types (user corrections, uncovered scenarios, repetitive operations, quality issues, capability assessments) and writes them as topic files under a feedback directory. - Deduplication & Indexing: Checks FEEDBACK-INDEX.md before writing, merging recurring failure modes instead of creating duplicates. - Four-Dimension Scoring: Every entry carries Precision, Coverage, Efficiency, and Satisfaction scores (1-5) with anti-inflation rules, plus a failure_class field (skill-defect, execution-lapse, unset) for routing. - Use Case: A user says "the Skill never mentioned X" after a failed run. The feedback-observer dispatches this Skill, which creates a scored feedback entry with a RED observation line, updates the index, and returns a confirmation to the main agent. ## Quick Start Ask the agent to record feedback about the correction you just made so it can be scored and indexed for future improvement.

Frequently Asked Questions about feedback-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record user corrections as structured feedback for an AI agent?▼

Invoke the feedback-writer flow when a correction signal is observed. It checks FEEDBACK-INDEX.md for duplicates, writes a topic file with context and four capability scores, updates the index, and returns a confirmation to the main agent.

What signals trigger a feedback entry in an agent self-evolution loop?▼

Five signal types trigger recording: user corrections, uncovered scenarios where the Skill improvised, repetitive operations requested more than three times, recurring quality issues, and post-execution capability assessments. Tool or environment frustration is explicitly excluded.

How are Precision, Coverage, Efficiency, and Satisfaction scores assigned?▼

Each dimension is scored 1-5 using a defined rubric, with anti-inflation caps: any correction caps Precision at 3, improvisation caps Coverage at 3, multiple rounds cap Efficiency at 3, and change requests cap Satisfaction at 3.

Does feedback-writer fix the underlying bug that caused the failure?▼

No. It only records the signal with a failure_class field for routing. Fixing bugs is delegated to a bug-fixer Skill, and evolving rules from feedback patterns is handled by the evolution-engine.

Why does duplicate feedback get merged instead of creating new entries?▼

Recording the same failure mode repeatedly inflates occurrence counts without adding information. The Skill checks FEEDBACK-INDEX.md first and increments the occurrences counter on the existing topic instead of writing a duplicate file.