Customer Feedback Intake Review
Published by sylphxai in skills
What this skill does
Design and audit customer feedback intake across support tickets, sales calls, app reviews, surveys, NPS, communities, cancellation reasons, feature requests, bug reports, and product analytics. Use when teams need to turn noisy feedback into evidence, prioritization input, roadmap decisions, and customer follow-up without overreacting to anecdotes.
Add Customer Feedback Intake Review to your agent
Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.
Install with a prompt
Paste this into a compatible coding agent:
add this skill "customer-feedback-intake-review" from https://github.com/sylphxai/skillsInstall with the CLI
Run this command in a controlled environment after reviewing the repository:
npx skills add https://github.com/sylphxai/skills --skill customer-feedback-intake-reviewSkill instructions
Customer Feedback Intake Review
Use this skill to convert a customer feedback intake, dedupe, routing, prioritization evidence, roadmap loops, and close-the-loop communication question into a concrete artifact with owners, gates, metrics, and recovery paths.
Workflow
- Identify feedback sources, customer segments, revenue/user impact, product area, owner, decision cadence, and follow-up promise.
- Read
references/customer-feedback-intake-patterns.md. - Classify feedback as bug, usability friction, feature request, pricing objection, churn reason, praise, risk signal, or research lead.
- Define intake fields, taxonomy, dedupe, severity, evidence score, routing, prioritization handoff, and close-the-loop workflow.
- Produce feedback state machine, signal decision table, event schema, triage checklist, and anti-anecdote guardrails.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not let loudness, logo size, or recency become the only priority signal.
- Do not promise delivery dates from intake unless roadmap owners explicitly commit.
- Do not merge bugs, support confusion, feature requests, and churn reasons into one undifferentiated backlog.
- Do not store sensitive customer comments without redaction, consent, and access control.
Output format
Feedback context:
Source / segment / product area / promise:
Feedback system:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |
Taxonomy and evidence:
- <item> -> <policy, metric, edge case, support note>
Close-the-loop and governance:
- <trigger> -> <action, communication, owner>
Files included
- agents/openai.yaml
- references/customer-feedback-intake-patterns.md
- SKILL.md