Feedback and reviews

The feedback board is shared by every organisation on Skillhook Cloud. Feature requests are public; issues are private to the organisation that reported them and the Skillhook team, until the team publishes a sanitised title others can "me too". The board never shows an address, an organisation or an issue's context: authors appear by first name, or as "A Skillhook user".

An item moves from open to planned, in progress and done, or ends declined or duplicate (its votes and subscribers move to the item it joins). Each change is in the item's timeline with the team's note. One vote per organisation; voting subscribes you, and taking the vote back unsubscribes you unless you filed it or commented. Problem reports filed from the dashboard's Support page, the API or a machine (skillhook cloud report) are items too.

The board, the API, the MCP server and the CLI do the same things. Filing looks for similar items first: request_feature and report_issue answer created: false with similar items to upvote instead, and force: true files anyway.

Every API answer carries an x-request-id. Pass it as request_id, with what you know as context (versions, error codes, ids; up to 64 KiB of JSON, never public) and the machine, job or delivery it concerns. skillhook feedback report --last attaches the last failed call of the CLI by itself; --job attaches a job and its machine.

One review per organisation (the reviews page), posted by a member or an admin: a rating from 1 to 5 and, if you like, a title, what you like and would change, your use case, the name and company to show, and whether we may quote it. It is published at once unless an automated check holds it for the team (language, links, an account less than a day old that never paid). Edits keep the earlier version. Agents post only what the person said, never a rating of their own.

Every one thanks you, names the item, links to it and says what happens next. They come from support@skillhook.dev; replying reaches the team. Turn them off with the link in any of them (one click, for that address) or under Email preferences; product emails and the digest are separate. At most 20 feedback emails reach one address a day.