skill-feedback

Solid

Capture and aggregate real-world usage feedback for Agent Skills so the Skill Quality Gate loop can keep improving them over time. Use it whenever a skill misfires or underperforms: a skill triggered wrongly (wrong trigger), failed to auto-load on a relevant request (near-miss / description gap), produced a wrong, broken, or low-quality output (output issue), or the user manually corrected its result (manual correction). Also use it to review accumulated skill feedback before running skill-forge, or to close the feedback loop that raises skill quality. Writes one structured JSON object per line to feedback/<skill>/YYYY-MM-DD.jsonl and can summarize them into a report/export that feeds skill-forge's Optimize-description step. Trigger phrases: 'skill feedback', 'log skill feedback', 'skill triggered wrongly', 'near-miss trigger', 'wrong trigger', 'output issue', 'manual correction', 'improve skill', 'skill quality', 'feedback loop'.

AI & Automation 6 stars 0 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
28
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Skill Feedback — capture the fuel for skill improvement This skill closes the loop opened by `docs/SKILL_QUALITY_GATE.md`. The Quality Gate tells you *whether* a skill is good; this skill tells you *how to make it better next time* by recording what happened in real usage and turning it into a feed for `skill-forge`. Without a feedback capture, improvement is guesswork. With it, every near-miss trigger and every manual correction becomes a concrete edit to a skill's `description` / `when_to_use` / body. ## When to use - A skill **should have triggered** but did not (near-miss): the user's request was in-scope but the auto-load missed it. - A skill **triggered wrongly**: the wrong skill loaded for the request. - A skill produced a **wrong / broken / low-quality** output (output issue). - The user **manually corrected** the skill's output (edited the result, or told you "no, do it differently"). - You want to **review** what has piled up before running `skill-forge`. ## DO NOT USE FOR - General chat feedback, venting, or notes unrelated to a specific skill — those belong in memory or the session log, not the skill feedback store. - Capturing secrets or personal data — never log credentials or PII in entries. ## Auto-capture (make it automatic) For the loop to run without manual nudging, capture feedback proactively. Append the rule from `AGENTS_FRAGMENT.md` (repo root) to your opencode `AGENTS.md`. Then any near-miss / manual correction is logged automatically —...

Details

Author
bestdeejay-design
Repository
bestdeejay-design/agent-skills
Created
1 months ago
Last Updated
2 weeks ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

skill-from-feedback

Use when the user wants to modify, improve, patch, or revise an existing agent skill from feedback — real session failures, “this skill did X wrong”, tighten triggers, fix workflow holes, or turn review notes into SKILL.md changes. Not for creating a brand-new skill from scratch (use capture-workflow / create-skill) and not for scanning all sessions (use agent-session-auditor).

0 Updated 6 days ago
YosefHayim
AI & Automation Listed

skill-feedback

Review recent Claude Code sessions that used a specific agent or skill and submit per-session feedback as GitHub issues. Use when the user says "submit [agent/skill] feedback", "review my [agent/skill] sessions", or "file [agent/skill] feedback issues".

0 Updated 1 months ago
ingoclaro
AI & Automation Listed

skill-improvement

Detects when a Claude Code session reveals a gap, bug, or improvement in an existing skill, then proposes a targeted patch and (with user approval) creates a local git branch and commit in the skills repo. Trigger this skill whenever you notice during a session that: a skill gave wrong or incomplete guidance, you had to correct or supplement a skill's instructions, a workaround was needed that should be documented, or the user says something like "the skill missed this", "add this to the skill", or "we should update the skill". Also trigger proactively at the end of any session that used a skill and produced fixes or new knowledge. Never wait for the user to ask.

2 Updated 1 weeks ago
mouchegmouradian