SkillsAdd

antithesishq/antithesis-skills

antithesis-skills-feedback

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.

First seen Mar 25, 2026

Installation

$ npx skills add antithesishq/antithesis-skills --skill antithesis-skills-feedback
View on skills.sh ↗ GitHub repository ↗

Also in this package

Other skills from antithesishq/antithesis-skills · top by installs.

npx skills add antithesishq/antithesis-skills
antithesis-research 463 antithesis-triage 447 antithesis-documentation 445 antithesis-workload 436 antithesis-setup 420 antithesis-debug 411 antithesis-launch 350 antithesis-query-logs 347 test:triage 240 antithesis-agent-browser 227

Browse all from antithesishq/antithesis-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 267
License LICENSE
Default branch main
Open issues 12
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version2026-09-08 2e4a837
Declared agents claude-code
More metadata
version
2026-09-08 2e4a837

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,285 B
  • docs SUMMARY.md 339 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 326 installs

SKILL.md

Antithesis Skills feedback

Skill version: 2026-09-08 2e4a837

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.yml

Pre-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

  1. Identify the skill that was being used when the problem occurred.
  2. Get the skill version by running git rev-parse --short HEAD in the skills repo if you know where it is.
  3. Determine agent info from your environment context (agent name + version).
  4. Write a brief what-happened summary (1-2 sentences).
  5. Write your agent-explanation — a short, honest self-assessment of what went wrong (2-4 sentences).
  6. Set the title to a short description of the bug (under 80 characters).
  7. Percent-encode all parameter values.
  8. Assemble the URL by appending only the fields you can meaningfully fill. Do NOT fill expected or context — 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-happened and agent-explanation first — the user can edit these in the form.
  • Drop agent-explanation entirely if still too long.
  • As a last resort, drop what-happened too and only pre-fill skill, skill-version, agent, and title.

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.