wise-feedbacklisted

# /wise-feedback — file a feedback issue against the marketplace ## Why this skill exists The wise plugin ships dozens of skills and workflows that users exercise many times a day. When one of them misbehaves — a workflow gets stuck, a skill returns a surprising result, a prompt is thin — the friction of "switch to browser, open github.com/e1024kb/wise-claude, click New Issue, fill three sections, remember to assign and label" is enough to swallow most of the feedback silently. This skill closes the gap. A single `/wise-feedback` (optionally with a short free-form note) captures the environment, drafts the issue body, previews it, and creates the issue via `gh issue create` — already assigned to [@e1024kb](https://github.com/e1024kb) and tagged `feedback`. ### Design principle — feedback is about the plugin, not the project The single most important framing rule for this skill: **the issue subject is the wise plugin, not the user's project.** The user is reporting that a `/wise-*` skill or workflow needs to be improved or fixed; what they happened to be doing in their own codebase when the problem surfaced is incidental. In practice that means: - The **prompt** and the **session signal** the skill draws from should describe the misbehaving wise component (which skill, which step, what it did wrong, what was expected), not the user's task at the time. - The **Environment** section keeps one project breadcrumb — the public git remote URL of the cwd, rendered as `