story-feedback-sentiment
Skill0 starsChanged 7 months agoMITView on GitHub
Design a post-release feedback-sentiment-monitoring strategy for a user story — sources, sentiment indicators, categories, alert rules, response templates, and reporting cadence. Use when the user asks how to monitor user reception, track sentiment, handle feedback, or set up post-launch listening.
In this repository26 other files it gives its agents.
- story-a11y-linterSkill
- story-agentic-aiSkill
- story-alternative-solutionsSkill
- story-auto-documentationSkill
- story-bias-auditSkill
- story-business-valueSkill
- story-doc-driftSkill
- story-edge-casesSkill
- story-failure-scenariosSkill
- story-gherkinSkill
- story-implementationSkill
- story-investSkill
- story-kickoffSkill
- story-nonfunctionalSkill
- story-persona-empathySkill
- story-pii-scannerSkill
- story-qaSkill
- story-questionsSkill
- story-requirements-breakdownSkill
- story-securitySkill
- story-stakeholder-impactSkill
- story-summarySkill
- story-synthetic-dataSkill
- story-telemetry-predictorSkill
- story-user-journeySkill
- story-visual-regressionSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 17
If none of the above, ask the user to paste the story or point to a file.
- Distinctive: line 46
Consider different user segments.
- Distinctive: line 50
Avoid feedback fatigue — don't over-survey.
- Distinctive: line 51
Consider cultural/regional sentiment differences.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
User Feedback Sentiment Strategy
Design a strategy for monitoring user feedback after a feature ships to detect whether it hit the mark.
Input
Take the user story from whichever of these is available first:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md— read the file first. - The current editor selection or most recently referenced story in the conversation.
- If none of the above, ask the user to paste the story or point to a file.
Instructions
You are an expert in customer experience, feedback analysis, and sentiment monitoring.
Feedback Sources:
- App Store Reviews — iOS App Store, Google Play, rating changes, volume trends.
- Support Channels — tickets, chat transcripts, email, phone summaries.
- Social Media — Twitter/X mentions, Reddit, LinkedIn, community forums.
- In-App — feedback widgets, feature ratings, bug reports, feature requests.
- Surveys — NPS, CSAT, CES, feature-specific surveys.
Sentiment Framework:
- Positive — praise, thanks, expansion requests, recommendations, increased engagement.
- Negative — complaints, frustration, feature-removal requests, unfavorable competitor comparisons, bug reports.
- Neutral — usage questions, factual comparisons, improvement suggestions, doc requests.
Tagging Strategy: feature-specific tags; release version tags; sentiment tags; user-segment tags.
Alert Thresholds: sudden spike in negative sentiment; rating drop below threshold; support ticket volume increase; social-media crisis indicators.
Response Strategy: acknowledge promptly; escalate appropriately; close the feedback loop; track resolution impact.
Guidelines:
- Focus on actionable feedback.
- Balance quantitative and qualitative signals.
- Consider different user segments.
- Plan for both immediate and long-term monitoring.
- Include escalation paths for critical feedback.
- Design for continuous improvement.
- Avoid feedback fatigue — don't over-survey.
- Consider cultural/regional sentiment differences.
- Track sentiment trends over time, not just snapshots.
- Connect feedback to specific feature components.
Output format
Render as markdown in the chat:
- Title: "Feedback Sentiment Strategy for [Feature]"
- Intro — 2–3 sentences on monitoring approach
- Feature Tags — keywords to search for this feature across channels
- Feedback Sources — 3–5 sources to monitor (which and why)
- Sentiment Indicators — positive / negative / neutral signals specific to this feature
- Feedback Categories — common feedback types expected
- Monitoring Strategy — tools, cadence, ownership
- Alert Rules — when to escalate (specific thresholds)
- Response Templates — short reusable responses to common positive / negative / neutral patterns
- Analysis Cadence — how often to review (daily / weekly / release checkpoints)
- Success Signals — what positive feedback looks like for this feature
- Failure Signals — red flags to watch for
- Reporting Recommendations — how to report insights
- Summary — 2–3 sentences on expected user reception
No JSON.
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.

