satisfaction-feedback
Skill104 starsChanged 10 months agoApache-2.0View on GitHub
Handle user satisfaction feedback. When users respond with "satisfied"/"unsatisfied", update FAQ usage count or record BADCASE. Trigger words: satisfied/unsatisfied/resolved/not resolved/thanks/满意/不满意/解决了/没解决/谢谢.
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 26
Use file locks: Must use SharedKBAccess file locks when updating FAQ.md and BADCASE.md
- Distinctive: line 27
Concurrency safety: Avoid data conflicts when multiple users operate simultaneously
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Satisfaction Feedback Processing
Process user satisfaction feedback and update FAQ or record issues based on the answer source.
Trigger Words
Satisfied: satisfied, resolved, thanks, understood, ok, got it, clear, I see, 满意, 解决了, 谢谢, 明白了, 好的, 懂了, 清楚了, 知道了 Unsatisfied: unsatisfied, not resolved, wrong, incorrect, doesn't work, 不满意, 没解决, 不对, 错了, 不行
Processing Logic
Process feedback based on answer source from previous round (metadata answer_source):
| Answer Source | Satisfied Feedback | Unsatisfied Feedback |
| FAQ | Increment usage count | Remove entry + Record BADCASE |
| Knowledge base file | Add to FAQ | Record BADCASE |
Key Principles
- Use file locks: Must use
SharedKBAccessfile locks when updating FAQ.md and BADCASE.md - Concurrency safety: Avoid data conflicts when multiple users operate simultaneously
- Status update: Set session_status to "resolved" after satisfied feedback
Detailed Operations
For FAQ add/delete/modify operation details, see FAQ_OPERATIONS.md
In this repository9 other files it gives its agents.
- backend/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- frontend/CLAUDE.mdCLAUDE.md
- skills/CLAUDE.mdCLAUDE.md
- batch-notificationSkill
- document-conversionSkill
- excel-parserSkill
- expert-routingSkill
- large-file-tocSkill
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.