Index of every page on this site: llms.txt
All skills
Run it yourself

Turn every customer question, comment, objection, or refund into a classified, routed, fixed, and verified improvement: capture verbatim feedback, classify it into one of nine labels, find the root cause, fix at the smallest effective level, verify by re-testing the exact customer scenario, and log it. Use for any customer feedback about a digital product or its content.

  • 4 files
  • 17.9 KB
  • Updated 5 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/jokerhtml/needcraft-skills/feedback-loop

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

README.md

≈547 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Feedback Loop

Turn every customer question, comment, objection, or refund into a classified, routed, fixed, and verified improvement.

What it is

A seven-step loop — capture, classify, root-cause, decide, fix, verify, log — with nine defined classification labels, a worked guide to telling close labels apart, a response template, SLA guidance, and a feedback-log template with a filled example entry.

Who it is for

A solo creator or small team selling a digital product (guide, template, course, or similar) who answers their own support mail and wants every message to either improve the product or improve the listing — and to be able to prove which one it was.

How to use

  1. Read SKILL.md — the process, the nine label definitions, the response template, and the SLA guidance.
  2. Write down your refund terms before your first sale (the skill recommends a fix-first shape inside a 30-day window; your terms are yours to set).
  3. Create a feedback log at a path you choose. Copy the blank template from examples/feedback-log-template.md.
  4. For each feedback item: capture it verbatim, classify it into exactly one label, check the listing before blaming the product, fix at the smallest effective level, verify by re-testing the exact customer scenario, and log it.

Example

examples/feedback-log-template.md contains a blank log template and one filled example entry (a CONFUSION item: a customer could not find the templates). The example entry is illustrative, written for this skill — not a real customer's words.

Install

Copy this folder into your skills directory and reference it by name whenever customer feedback arrives. No build step, no API key, no account needed — just a support inbox, the product files, and the listing.

License

MIT — see the license in the skill frontmatter.

Disclaimer

This skill classifies and routes feedback; it does not decide product strategy and it does not set your refund terms or legal position. Escalate refund disputes, legal or compliance concerns, and fundamental-misrepresentation feedback to the product owner or qualified advice instead of resolving them alone.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 90f40b1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 5 days ago
Other metadata
metadata
{
  "version": "1.0.0",
  "date": "2026-11-16",
  "author": "Muhammad Saad Ranjha / NeedCraft"
}

README badge

README badge for jokerhtml/needcraft-skills/feedback-loop