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.

examplesfeedback-log-template.md

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

Feedback log — template + filled example

Keep the log in one file at a path you choose (for example feedback-log.md in your product folder). One entry per feedback item, including NO ACTION items with the reason. The log is internal, never customer-facing. The filled entry below is illustrative, written for this skill — not a real customer's words.

Blank template

DATE: YYYY-MM-DD | SOURCE: email / comment / review / refund request / DM
VERBATIM: "[customer's exact words — short quote]"
CLASS: QUESTION / CONFUSION / OBJECTION / BUG / MISSING CONTENT / EXPECTATION GAP / FEATURE REQUEST / POSITIVE SIGNAL / REFUND SIGNAL
ROOT CAUSE: [product / listing copy / onboarding / missing file / wrong expectation — one line]
ACTION: PRODUCT FIX / FAQ FIX / CONTENT IDEA / SALES PAGE FIX / ONBOARDING FIX / NO ACTION
STATUS: open / done
VERIFIED: [yes — how you re-tested the exact scenario | no — still open, why]

Filled example entry

DATE: 2026-11-16 | SOURCE: email
VERBATIM: "I can't find the templates — where are they?"
CLASS: CONFUSION
ROOT CAUSE: onboarding — the contents page does not point to page 6, where the templates live
ACTION: ONBOARDING FIX
STATUS: done
VERIFIED: yes — opened the updated file, followed the contents page, reached the templates in 2 clicks

A second filled example (refund signal)

DATE: 2026-11-16 | SOURCE: email
VERBATIM: "This isn't what I expected — can I get my money back?"
CLASS: REFUND SIGNAL
ROOT CAUSE: expectation gap — the listing's headline implied done-for-you writing; the product is templates
ACTION: SALES PAGE FIX (rewrote the headline to say "templates you customise") + fix-first refund offered per the stated terms
STATUS: done
VERIFIED: yes — re-read the full listing against the product files; refund processed under the 30-day fix-first terms; customer confirmed receipt

A NO ACTION example (still logged)

DATE: 2026-11-16 | SOURCE: comment
VERBATIM: "Could you add a version for agencies?"
CLASS: FEATURE REQUEST
ROOT CAUSE: n/a — new scope the product never claimed
ACTION: NO ACTION — out of scope for this product; noted as a possible future product, not a fix
STATUS: done
VERIFIED: n/a — no product change to verify; customer replied to with an acknowledgement

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