prompt-feedback-skill
Skill0 starsChanged 32 days agoMITView on GitHub
Provide structured feedback on the user's messages in the conversation using the "good / more / next action" framework.
1 other project uses a version of this.
Other versions1 project uses a version of this.
Word for word · 1
- tsubasaogawa/prompt-feedback-skill★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- ai-credit-efficient-reviewSkill
- branch-tldrSkill
- drafting-tweet-from-todaySkill
- finding-unused-customizationsSkill
- hacker-news-digest-jaSkill
- japanese-tech-writingSkill
- natural-japaneseSkill
- pr-branch-composition-checkSkill
- resume-improverSkill
- semantic-commit-helperSkill
- session-stockerSkill
- syncing-forked-skillsSkill
- tf-destroy-plan-inverterSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
next action: must be exactly one concrete step (a question, metric, or command).
- Distinctive: line 19
No extra sections. Keep it concise and actionable.
≈ “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
Instructions
Analyze all user messages in this conversation (user messages only; prioritize latest intent on conflict) and provide structured feedback focused on improving the prompt. Always respond in the same language as the user.
Rules
- Internally synthesize all user messages into one consolidated instruction (do not output).
- Identify good (strengths), more (missing info), and next action (one concrete step).
- Unresolvable contradictions → list under more.
- next action must be exactly one concrete step (a question, metric, or command).
- No extra sections. Keep it concise and actionable.
Output format
Respond, then save to ~/.local/share/prompt-feedback-skill/YYYYMMDD-HHMMSS.md using the machine's local timezone (e.g., date +%Y%m%d-%H%M%S without -u; mkdir -p when the directory does not exist).
Saved file adds a # <one-line summary> header before the sections below.
## good
- ...
## more
- ...
## next action
- ...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.