← ClaudeAtlas

feedbacklisted

Use this skill when the user says "send feedback", "report a bug", "this didn't work", "I want to suggest a feature", "where do I file an issue for iEvo", or after iEvo has done something the user would want to comment on. Submits feedback about the iEvo plugin — bug reports, feature requests, suggestions, or general comments. Posts as a GitHub issue in `ievo-ai/skills` via `gh` CLI.
ievo-ai/skills · ★ 0 · Data & Documents · score 72
Install: claude install-skill ievo-ai/skills
# Feedback Post user feedback as a GitHub issue in `ievo-ai/skills` so we can fix bugs, prioritize features, and improve the plugin. ## Step 0: Detect invocation context This skill has three flows: **(A) Generic feedback** — default. User invoked `/ievo:feedback` or expressed feedback intent freely. Go to Step 1. **(B) Skill-rejections feedback** — invoked from `/ievo:init` final feedback step (step 13 in v0.2.0+) with a list of skipped skills from the interview. The caller will provide context like: ``` The user just completed /ievo:init interview. They installed N skills and skipped these M skills: <list>. Collect reasons for the skips and submit as feedback to ievo-ai/skills, copying reasons forward as registry-improvement signal that can be relayed to vercel-labs/skills. ``` **(C) Pre-filled handoff** — the content to post is already known before this skill runs; two callers share this flow: - **Evo handoff** — invoked from `/ievo:evo` Step 5.6 after a lesson was captured that looks like it's about the iEvo plugin itself. The caller passes the **verbatim lesson text already known** (the same text appended to the overlay, in the user's original language). - **Extract-best-practices handoff** — invoked from `/ievo:extract-best-practices` Phase 5 after a newly authored skill/agent package looks marketplace-worthy. The caller passes a short summary plus the **full authored package content** (already English — agent-synthesized, not user free-text) as the pre-filled