Give Claude a Method It Can Reuse, Complete Resource Pack

Read inputs/invoice-chase-invoices.csv. Use September 21, 2026 as the reporting date. Show the overdue invoices that still have money owing, total the remaining balances, and draft reminders here for me to review. Use only the supplied file and do not send anything.

Read inputs/willow-desk-social-brief.md, prepare a one-week plan and draft the text in the conversation using only those facts. I am reviewing copy here, so leave sending, publishing and creating images out of this run.

Read feedback-skill-design-answers.md and inputs/customer-feedback.csv. Follow the six answers for this one feedback analysis. Show the report in this conversation. For this report, do not use or create a Skill, do not save a report file, do not change the feedback or contact anyone, and leave the final business priority decision with me.

Use the six answers in feedback-skill-design-answers.md, the two files in inputs/, the checked feedback report, and any corrections we just reviewed in this conversation to create a project Skill named customer-feedback-analyzer at .claude/skills/customer-feedback-analyzer/SKILL.md. Preserve repeatable steps and checks for future feedback batches, not this batch's IDs, counts or conclusions. Do not replace an existing Skill. Explain unfamiliar parts of the new file and stop before testing it.

Read the customer-feedback-analyzer folder. Explain what it contains, then install the complete Skill in this project's .claude/skills folder. Keep any existing Skill of that name unchanged and tell me if there is a conflict. Show me the installed path when finished.

/customer-feedback-analyzer Analyze inputs/customer-feedback.csv and return the report here in the conversation. Preserve the feedback IDs and exact supporting excerpts. Count each ID once within a theme, distinguish frequently mentioned problems from potentially serious reports, and propose up to 3 actions with reasons. Leave the final choice to me. Do not edit the input file or contact anyone.

Analyze the customer feedback file inside the inputs folder, show recurring themes with IDs and excerpts, separate serious isolated reports and suggest what I should investigate next.

When the user requests a detailed evidence check, read `references/evidence-checks.md` before finalising the report.

Update the skill as per the comment.

test the skill with a detailed evidence check

/customer-feedback-analyzer Analyze inputs/customer-feedback.csv and tell me what we should improve. Return the report here and leave the source file unchanged.

Analyse inputs/customer-feedback.csv and give me a report. Tell me what I should investigate next.

Analyse inputs/customer-feedback.csv and give me a report. Tell me what I should investigate next.

/customer-feedback-analyzer Analyze inputs/customer-feedback.md and tell me what we should improve. Return the report here and leave the source file unchanged.

Compare the customer-feedback-analyzer Skill before and after this repair, using the saved CSV and Markdown requests and reports. What did the repair fix? Did the revised Skill lose anything the earlier Markdown run did well? Check coverage of all 12 IDs, theme evidence and counts, exact supporting quotations, the wording of the sharp-edge report, and whether the final priority decision stays with me. Point to the source comments and report passages behind each conclusion. Do not change the Skill yet.

Files: the original Skill is skill-before-repair/SKILL.md. The repaired Skill is .claude/skills/customer-feedback-analyzer/SKILL.md. The inputs are inputs/customer-feedback.csv and inputs/customer-feedback.md. The requests are in saved-requests/. Three reports are in saved-reports/. The fourth report is the Markdown report you produced earlier in this chat.