← ClaudeAtlas

feedbacklisted

Report a problem with the pellet-expert plugin as a GitHub issue: a wrong or unhelpful answer, a missing topic, an unsafe suggestion, a confusing reply. Use when the user says an answer was wrong, asks how to report a problem, or invokes /pellet-expert:feedback. Shows the exact text first and posts only with the user's yes.
savnik/lindner-sommerauer-pellet-expert · ★ 0 · Data & Documents · score 60
Install: claude install-skill savnik/lindner-sommerauer-pellet-expert
# Report a problem with pellet-expert This is the only part of the plugin that sends anything anywhere. It posts a public GitHub issue at https://github.com/savnik/lindner-sommerauer-pellet-expert/issues, and only after the user has seen the exact text and said yes. ## Rules that never bend 1. **Show the complete issue text before anything is posted.** Title, labels, body. Then ask. No yes, no post. 2. **Nothing from the installation record goes in verbatim.** The record is private. Take at most three generic facts from it, and only if relevant: model (e.g. SL-P 12), firmware version string, and the layout in one phrase (e.g. "one mixed circuit, hot-water tank, no buffer"). Never settings values, dates, event history, or the record's open questions. 3. **No identifiers.** No names, addresses, phone numbers, email addresses, serial numbers, installer or company names, file paths, or usernames. If the user's own words contain any, remove them and say so. 4. **Say that the issue is public.** Once, plainly, before asking for the yes. 5. **The user can edit.** If they change the text, use their version, still subject to rules 2 and 3. ## What goes in the issue Build the body from the conversation. Keep it under 300 words. Sections: - **What I asked** — the user's question, verbatim if it contains no identifiers, otherwise paraphrased. - **What the plugin answered** — two or three sentences summarising the answer, including any anchors it cited (e.