How do I install the Woz Feedback skill?

Run npx skillmds@latest add withwoz/woz-feedback in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Woz Feedback safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Woz Feedback?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Woz Feedback free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Woz Feedback?

WithWoz (@withwoz) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Woz Feedback by withwoz — Agent Skill

Name: Woz Feedback
Author: WithWoz

File contents

WOZCODE feedback & bug reports

TRIGGER when: user says "send feedback", "share feedback", "i wish woz", "feature request", "report a bug", "woz is broken", "file a bug", or runs /woz-feedback.

Decide the type from the user's words: broken behavior is a bug; feature requests and general thoughts are feedback.

If the user already described their feedback or bug in their message, use it directly. If they invoked /woz-feedback with no content (or said something too vague to act on), ask them — for feedback: "What would you like to share with the WOZCODE team?"; for a bug: "What broke? What did you do, what happened, and what did you expect?" — then wait for their reply before submitting.

Derive subject (one-line headline, ~80 chars max) and body (the full message, verbatim) from the user's words. Don't paraphrase or add boilerplate.

Submit by piping a JSON envelope to stdin. Use a single-quoted heredoc (<<'WOZ_FEEDBACK') so the shell does NO expansion — user text like $(cmd) or backticks is passed through literally and cannot execute. JSON-encode subject and body so embedded ", \\, or newlines survive.

For general feedback (feature requests, thoughts) — this is the default, omit type:

node --no-warnings=ExperimentalWarning ${CLAUDE_PLUGIN_ROOT}/scripts/wozcode-cli.cjs feedback <<'WOZ_FEEDBACK'
{"subject":"<json-escaped subject>","body":"<json-escaped body>"}
WOZ_FEEDBACK

For a bug report, add "type":"BUG" so it routes to bug triage:

node --no-warnings=ExperimentalWarning ${CLAUDE_PLUGIN_ROOT}/scripts/wozcode-cli.cjs feedback <<'WOZ_FEEDBACK'
{"type":"BUG","subject":"<json-escaped subject>","body":"<json-escaped body>"}
WOZ_FEEDBACK

The CLI auto-attaches CLAUDE_CODE_SESSION_ID, anonymous telemetry id (unless the user opted out via WOZCODE_TELEMETRY_DISABLED=true), OS release, architecture, and Node.js runtime version. The email is auto-filled from the logged-in account.

On exit 0: tell the user "✅ Sent. Thanks." On non-zero: relay the error verbatim and mention support@withwoz.com as a fallback.

---name: woz-feedbackdescription: Send feedback or a bug report to the WOZCODE team. Bug reports are tagged for triage and auto-attach session context (session id, anonymous id, OS, arch, Node version).---# WOZCODE feedback & bug reportsTRIGGER when: user says "send feedback", "share feedback", "i wish woz", "feature request", "report a bug", "woz is broken", "file a bug", or runs `/woz-feedback`.Decide the type from the user's words: broken behavior is a **bug**; feature requests and general thoughts are **feedback**.If the user already described their feedback or bug in their message, use it directly. If they invoked `/woz-feedback` with no content (or said something too vague to act on), ask them — for feedback: "What would you like to share with the WOZCODE team?"; for a bug: "What broke? What did you do, what happened, and what did you expect?" — then wait for their reply before submitting.Derive `subject` (one-line headline, ~80 chars max) and `body` (the full message, verbatim) from the user's words. Don't paraphrase or add boilerplate.Submit by piping a JSON envelope to stdin. Use a single-quoted heredoc (`<<'WOZ_FEEDBACK'`) so the shell does NO expansion — user text like `$(cmd)` or backticks is passed through literally and cannot execute. JSON-encode `subject` and `body` so embedded `"`, `\\`, or newlines survive.For general feedback (feature requests, thoughts) — this is the default, omit `type`:```bashnode --no-warnings=ExperimentalWarning ${CLAUDE_PLUGIN_ROOT}/scripts/wozcode-cli.cjs feedback <<'WOZ_FEEDBACK'{"subject":"<json-escaped subject>","body":"<json-escaped body>"}WOZ_FEEDBACK```For a bug report, add `"type":"BUG"` so it routes to bug triage:```bashnode --no-warnings=ExperimentalWarning ${CLAUDE_PLUGIN_ROOT}/scripts/wozcode-cli.cjs feedback <<'WOZ_FEEDBACK'{"type":"BUG","subject":"<json-escaped subject>","body":"<json-escaped body>"}WOZ_FEEDBACK```The CLI auto-attaches `CLAUDE_CODE_SESSION_ID`, anonymous telemetry id (unless the user opted out via `WOZCODE_TELEMETRY_DISABLED=true`), OS release, architecture, and Node.js runtime version. The email is auto-filled from the logged-in account.On exit 0: tell the user "✅ Sent. Thanks." On non-zero: relay the error verbatim and mention `support@withwoz.com` as a fallback.

Frequently asked questions

Woz Feedback