← ClayCONTENT HISTORY
WHAT CHANGED
Update to Clay
Snapshot Nov 18, 2026 · 06:19 UTC · version 2.38.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Clay and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Clay feedback — send a bug report or product feedback to the Clay team via the `clay feedback` CLI.",
"included_files": [],
"name": "clay-feedback",
"skill_md_contents": "---\nname: clay-feedback\ndescription: Clay feedback — send a bug report or product feedback to the Clay team via the `clay feedback` CLI.\nallowed-tools: AskUserQuestion\n---\n\n# Clay Feedback\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\nSend feedback or a bug report to the Clay team using `clay feedback`. It reads the message from **stdin** and automatically attaches environment details.\n\nThe CLI does no confirmation of its own, so confirm with the user before sending.\n\nFeedback is one-way: it lands in the Clay team's triage queue and nobody replies. When the\nuser wants a human who responds — they explicitly ask for support, or the matter needs staff\naction (a disputed or duplicate charge, a refund, account recovery) — use `clay support`\ninstead (see the `clay` skill's \"Getting help and reporting problems\"). Product feedback\n_about_ billing or plans (confusing UX, a feature request) is still feedback and belongs here.\n\n## Steps\n\n1. **Determine type.** The test is: did Clay fail, or behave differently from how it is documented or built to work? First occurrences count, and you do not need to know whether it worked before.\n - Choose `bug` for: errors, crashes, timeouts or hangs; failures on valid input; wrong, empty, stale or duplicated output; output that contradicts the docs or `--help`; data lost or changed unexpectedly; documented features that do not work.\n - Choose `feedback` only when Clay worked as designed and the user wants something different: feature requests, capabilities Clay does not claim to have, UX or naming suggestions, working-but-confusing flows, general ideas.\n - Tiebreaker: if the user saw an error or unexpected result while doing something Clay supports, use `bug`; if it is still ambiguous, use `bug` without asking.\n\n2. **Get feedback text.** Use the argument if provided (e.g. `/clay-feedback would love CSV export from the enrichment table`). Otherwise ask the user what feedback or bug report they'd like to send. For a bug, include the command that was run, the error output, and expected versus actual behavior in the message.\n\n3. **Confirm.** Use your ask-user tool (`AskUserQuestion`; `askUser` inside the Clay app). List what the report will include, and offer \"Send\" / \"Cancel\":\n\n > This report will include:\n >\n > - Type: {bug or feedback}\n > - Your feedback: {feedback text}\n > - Environment info (auto-collected)\n >\n > Send this feedback?\n\n4. **If confirmed**, send the message on stdin. The CLI reads the feedback from stdin. Do **not** pass it inline in the shell command (no heredoc, no `echo`): the feedback is arbitrary user text, and a here-doc delimiter or quote appearing in it would truncate or mis-parse the message — or let pasted text run as shell. Instead, write the text to a temp file with your file-writing tool (which never goes through the shell), then redirect that file into the command. Always pass `--type bug` or `--type feedback` from step 1.\n - Write the feedback text verbatim to a temp file with an unpredictable name (a shared\n fixed path lets other local sessions read or clobber it), e.g. `/tmp/clay-feedback-<random>.txt`.\n - Then run:\n\n ```bash\n clay feedback --type <bug|feedback> < /tmp/clay-feedback-<random>.txt\n rm -f /tmp/clay-feedback-<random>.txt\n ```\n"
}SHA-256 of public snapshot: 3dc0831bdd6cab1d3c59a37123278537162bf5b5c2862a610c345b7acc94f5ce