DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to send a structured bug report when a label looks wrong with Classifier Dev

Let an agent file a feedback.now report when classification breaks or misbehaves.

Who it is forAn AI agent that gets wrong or failing classifications and needs to tell the maintainers without a human writing the report.

The problemA wrong or failing result goes unreported, so the same problem keeps happening for every caller.

The outcomeA structured report reaches the maintainers, and the agent gets a receipt showing whether it landed and how good it was.

What you need first

  • A terminal with curl or another HTTP client
  • npm, only if you want the classify CLI
  • The texts you want to label and a set of label names

Steps

  1. Run curl https://classifier.dev/.well-known/agent-feedback.json to see what the host accepts. (inferred, check the README)
  2. Run curl https://classifier.dev/api/v1/policy to read the categories, severities and limits. (inferred, check the README)
  3. Send a full structured report to POST /api/v1/feedback with the category, severity and the input and output that show the problem.
  4. Keep the report id from the response and check GET /api/v1/receipts/{id} to confirm it was accepted. (inferred, check the README)

Prompt for your agent

Using the feedback.now endpoints at https://classifier.dev described in the classifier-dev repo, file one report for <describe the wrong label> with the input text and the returned label as evidence. Output the report id and the receipt status. Verify that the receipt shows the report was accepted or marked as a duplicate.

Caveat. Accepted reports are emailed to the maintainers and kept for 90 days, so include only the input and output needed to show the problem and no secrets.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page