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.
What this skill does
# Antithesis Skills feedback 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.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.