/woz-feedback
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).
$ npx -y skills add WithWoz/wozcode-plugin --skill woz-feedback --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/woz-feedback
Context preview
The summary Claude sees to decide when to auto-load this skill.
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).
SKILL.md
woz-feedback.SKILL.mdname: woz-feedback
description: 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).
allowed-tools: Bash(node *)
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_FEEDBACKFor 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_FEEDBACKThe 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.
Read more
name: woz-feedback description: 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). allowed-tools: Bash(node *)
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_FEEDBACKFor 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_FEEDBACKThe 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.
Smarter tools for Claude Code that reduce token usage and cost. Replaces built-in file tools with optimized alternatives — fewer tokens per tool call means cheaper sessions that compound over time.
Repo: WithWoz/wozcode-plugin
Other skills on woz.
woz-recall
Search past Claude Code sessions to recall commands, solutions, and context from prior conversations. TRIGGER on 'remember when', 'last time', 'we did this…
woz-savings
Show the WOZCODE savings report — calls saved, time saved, tokens saved, and lifetime totals.

