aif-feedback
Skill0 starsChanged 7 months agoMITView on GitHub
Collect structured user feedback on aiframework-generated output. Saves to tools/learnings/feedback.jsonl for integration with /aif-evolve.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- aif-analyzeSkill
- aif-enhanceSkill
- aif-evolveSkill
- aif-ingestSkill
- aif-learnSkill
- aif-pulseSkill
- aiframework-learnSkill
- aiframework-reviewSkill
- aiframework-shipSkill
- aif-readySkill
- aif-researchSkill
- aif-reviewSkill
- aif-shipSkill
- aif-statusSkill
- retroSkill
- sheal-askSkill
- sheal-checkSkill
- sheal-driftSkill
- sheal-retroSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
After a user has run aiframework on a project
- Distinctive: line 14
When a user reports dissatisfaction with generated output
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Collect Feedback
Gather structured feedback from the user about their experience with aiframework-generated output. This data feeds into /aif-evolve for continuous improvement.
When to Use
- After a user has run aiframework on a project
- When a user reports dissatisfaction with generated output
- Periodically to collect improvement signals
Step 0: Telemetry (silent, non-blocking)
aiframework-telemetry skill_invoked skill=aif-feedback 2>/dev/null || trueStep 1: Ask 5 Questions
Present these questions one at a time, waiting for each answer:
- CLAUDE.md Quality (1-5): "How useful is the generated CLAUDE.md for your daily work?"
- Accuracy (1-5): "How accurate were the detected stack, domains, and commands?"
- Missing Context (free text): "What important context about your project is missing from the output?"
- Noise (free text): "What generated content is unhelpful or distracting that you'd remove?"
- Top Wish (free text): "If you could improve one thing about aiframework, what would it be?"
Step 2: Save Feedback
Append a JSON line to tools/learnings/feedback.jsonl:
jq -n --arg d "$(date +%Y-%m-%d)" --arg q SCORE --arg a SCORE --arg mc "ANSWER" --arg n "ANSWER" --arg tw "ANSWER" --arg p "$(basename "$(pwd)")" \
'{date:$d, claude_md_quality:($q|tonumber), accuracy:($a|tonumber), missing_context:$mc, noise:$n, top_wish:$tw, project:$p}' >> tools/learnings/feedback.jsonlStep 3: Acknowledge
Thank the user and explain:
- Feedback is stored locally in
tools/learnings/feedback.jsonl - Running
/aif-evolvewill incorporate this feedback into improvement recommendations - Patterns across feedback entries drive CLAUDE.md and rule evolution
Integration with /aif-evolve
The evolve skill reads feedback.jsonl alongside *-learnings.jsonl to:
- Identify recurring complaints (noise, missing context)
- Prioritize improvements by frequency and severity
- Track quality scores over time
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

