Send feedback about WBSO.ai to the team in one short API call. Works with or without a logged-in session — with an API key the feedback is linked to the user, otherwise it's anonymous.
When to use
Call this skill when:
- The user reports something that looks like a bug ("it crashes", "error with X", "that's not right")
- The user mentions an idea or feature request ("it would be useful if...", "could you...", "I'm missing...")
- The user has a question that cannot be answered from the skill context and that concerns the product itself
- The user gives a compliment about the platform
- The user explicitly says "I want to give feedback" or similar
Do not call it for:
- Questions about how to make an API call (solve those with the docs)
- Doubts about a WBSO estimate (that goes via
suggest-projector a normal conversation) - Questions you can simply answer yourself
Question style
Default plain text, as in the mainwbso skill. One question
at a time, short.
Step 1: Choose category
Based on what the user said, choose one of these categories:
| Category | When |
|---|---|
bug |
Something demonstrably does not work as it should |
idea |
Feature request, improvement point, "would be useful" |
question |
Question about the platform that you cannot answer |
compliment |
Positive feedback |
complaint |
Frustration or complaint about the platform (annoying, too slow, illogical) |
other |
Rest |
If in doubt, ask a short follow-up question. Otherwise: continue.
Step 2: Get message
If the user has just already said something concrete (the reason for this skill): use that as the message, optionally briefly cleaned up.
Otherwise, ask in plain text:
"What would you like to pass on? One or two sentences is enough."
Wait for free text. Take it over literally, without polish.
Preserve the line structure. Send the message as multi-line text with
real line endings (\n) when that helps readability: put
lists on separate lines and separate individual points with a blank line.
Do not flatten a structured message into one continuous paragraph. The
portal displays the message while preserving line endings, so the structure
you send along is what the team sees.
Step 3: Send
Claude Code sets plugin-root bin/ in $PATH, so there wbso
works directly. Codex uses the skill-local wrapper scripts/wbso.
WBSO_CLI="$(command -v wbso 2>/dev/null || find "$PWD" "$HOME/.codex/plugins/cache/wbso-ai/wbso" "$HOME/.codex/plugins/cache" -path '*/skills/*/scripts/wbso' -type f 2>/dev/null | sort -V | tail -1)"
test -n "$WBSO_CLI" || { echo "WBSO CLI niet gevonden"; exit 127; }
"$WBSO_CLI" feedback \
--message "<wat de gebruiker zei>" \
--category "<bug|idea|question|compliment|complaint|other>"
Optional --context '{"step":"track-time"}' to send along
context that helps the team reproduce (for bugs). Keep the JSON small
and without secrets.
Step 4: Confirm
Server returns 201 on success and the team automatically gets
a Slack notification. Give a short response:
"Passed on to the WBSO.ai team. Thanks!"
For a compliment: extra warm.
"Passed on to the team — they'll be happy with your compliment. Thanks!"
No JSON, HTTP codes or IDs to the user.
Error handling
400/422: validation error (empty message, unknown category) — ask again401with token: token invalid — still send feedback without header (anonymously), or let the user know that they are not logged in- Network error: report briefly "Could not send the feedback, your internet or the platform is doing something strange." and stop