feedbacklisted

# 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 skills share this flow, across three trigger points: - **Evo handoff** — invoked from `/ievo:evo` Step 5.6 after a lesson was captured that looks like it's about the iEvo plugin itself, or from its Step 5.65 after a lesson Step 5.6 left local instead reads as a generally-reusable engineering practice (the two are mutually exclusive by Step 5.65's own gate, so a given lesson triggers at most one). Either way 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:e