antithesis-skills-feedback
Skill304 starsChanged 18 days agoApache-2.0View on GitHub
File a bug report or feedback on the Antithesis skills by opening a pre-filled GitHub issue URL (skill name, skill version, agent, short summary). Load when the user wants to report a problem with, or give feedback on, any Antithesis skill. Does not auto-submit — presents the URL for the user to review.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Percent-encode: all parameter values.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Antithesis Skills feedback
Skill version: 2026-10-30 d5d7b3b
Help the user file a bug report against the Antithesis skills by opening a pre-filled GitHub issue.
Base URL
https://github.com/antithesishq/antithesis-skills/issues/new?template=bug_report.ymlPre-filling fields via URL parameters
GitHub issue templates accept query parameters to pre-fill fields. Each
parameter key corresponds to the id of a field in the template. Append them as
&<id>=<value> with values percent-encoded (spaces → %20, newlines →
%0A, etc.).
The available fields are:
| Parameter | Type | What to fill |
what-happened | textarea | Brief summary of what went wrong. Keep to 1-2 sentences — the user will elaborate. |
expected | textarea | Leave blank — only the user knows what they expected. |
skill | input | The skill that was active (e.g. antithesis-triage, antithesis-setup). |
skill-version | input | Run git -C <skills-repo> rev-parse --short HEAD to get the commit SHA. |
agent | input | The agent name and version (e.g. Claude Code 1.0.20). Use the agent info available in your context. |
agent-explanation | textarea | Your honest self-assessment: what did you do, and why did it go wrong? 2-4 sentences max. |
context | textarea | Leave blank — the user can add screenshots and logs themselves. |
You can also set the issue title via a title=<value> parameter.
How to construct the URL
- Identify the skill that was being used when the problem occurred.
- Get the skill version by running
git rev-parse --short HEADin the skills repo if you know where it is. - Determine agent info from your environment context (agent name + version).
- Write a brief
what-happenedsummary (1-2 sentences). - Write your
agent-explanation— a short, honest self-assessment of what went wrong (2-4 sentences). - Set the
titleto a short description of the bug (under 80 characters). - Percent-encode all parameter values.
- Assemble the URL by appending only the fields you can meaningfully fill. Do NOT fill
expectedorcontext— those are for the user.
URL length limit
Keep the total URL under 2000 characters. Browsers and GitHub may truncate or reject longer URLs. If the URL would exceed this limit:
- Shorten
what-happenedandagent-explanationfirst — the user can edit these in the form. - Drop
agent-explanationentirely if still too long. - As a last resort, drop
what-happenedtoo and only pre-fillskill,skill-version,agent, andtitle.
Example URL
https://github.com/antithesishq/antithesis-skills/issues/new?template=bug_report.yml&title=Triage%20skill%20fails%20to%20parse%20property%20results&skill=antithesis-triage&skill-version=1c45cd3&agent=Claude%20Code%201.0.20&what-happened=The%20triage%20skill%20crashed%20while%20parsing%20property%20results%20from%20the%20Antithesis%20dashboard.&agent-explanation=I%20attempted%20to%20extract%20property%20data%20from%20the%20results%20page%20but%20the%20HTML%20structure%20did%20not%20match%20the%20expected%20selectors.Presenting to the user
Do NOT auto-submit the issue. Open the URL (or print it if no browser is
available) so the user can review the pre-filled fields, add their own details
to expected and context, and submit when ready.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- ghuntley/loom★ 1.6k98% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- antithesis-debugSkill
- antithesis-documentationSkill
- antithesis-feature-workloadSkill
- antithesis-launchSkill
- antithesis-mutation-testingSkill
- antithesis-researchSkill
- antithesis-review-inputsSkill
- antithesis-setup-k8sSkill
- antithesis-setupSkill
- antithesis-triageSkill
- antithesis-workloadSkill
- test:triageSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.