Use this skill to interactively debug Antithesis test runs using the multiverse debugger (MVD session). Open a debugging-session URL, inspect container filesystems and runtime state, run shell commands, and extract evidence from inside the Antithesis environment. Supports both the simplified debugger (default) and the advanced notebook mode.
75
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies a specific niche (Antithesis multiverse debugger sessions), lists concrete actions, and provides explicit trigger guidance via the 'Use this skill to...' opening clause. The description includes domain-specific terminology that users would naturally use, making it highly distinguishable from other skills. One minor note is the use of second-person-adjacent 'Use this skill' phrasing, but it functions as trigger guidance rather than addressing the user directly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Open a debugging-session URL, inspect container filesystems and runtime state, run shell commands, and extract evidence from inside the Antithesis environment.' Also mentions specific modes (simplified debugger and advanced notebook mode). | 3 / 3 |
Completeness | Clearly answers both 'what' (inspect container filesystems, run shell commands, extract evidence, open debugging URLs) and 'when' ('Use this skill to interactively debug Antithesis test runs using the multiverse debugger'). The 'Use this skill to...' clause serves as an explicit trigger. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Antithesis', 'debug', 'multiverse debugger', 'MVD session', 'debugging-session URL', 'container filesystems', 'shell commands', 'notebook mode'. These are terms a user working with Antithesis would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Antithesis multiverse debugger (MVD) sessions. The specific product name 'Antithesis' and tool name 'MVD' make it very unlikely to conflict with other debugging or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides clear, actionable guidance for interacting with the Antithesis multiverse debugger. Its strengths are excellent progressive disclosure with well-organized reference file tables, concrete executable commands, and clear multi-step workflows with validation. The main weakness is moderate verbosity — some guidance is repeated across sections (e.g., simplified-first preference, runtime injection after navigation), and a few sections could be tightened without losing clarity.
Suggestions
Consolidate repeated guidance about 'start in simplified mode' and 'inject runtime after navigation' — these appear in multiple sections and could be stated once with a clear cross-reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~200+ lines) and includes some redundancy — for example, the runtime injection section repeats guidance already covered in the reference file pointers, and the general guidance section restates points made earlier (e.g., 'start in simplified mode' is said multiple times). However, most content is domain-specific and not something Claude would inherently know, so it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides concrete, executable bash commands throughout — runtime injection, mode detection, mode switching, waitForReady calls, simplified command execution, and page loading checks are all copy-paste ready. The workflows are specific with numbered steps and exact method calls. | 3 / 3 |
Workflow Clarity | Multiple workflows are clearly sequenced with numbered steps, each referencing the specific reference file to read and the specific action to take. The skill includes validation checkpoints (waitForReady, loadingFinished, loadingStatus), error recovery guidance (retry missing-runtime errors, fork fresh branch on nonzero exit), and a self-review checklist at the end. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview that delegates detailed instructions to clearly-organized reference files (setup-session.md, simplified-debugger.md, advanced-debugger.md, notebook.md, actions.md, common-inspections.md). References are one level deep, organized in tables by mode, and each reference file's purpose is clearly signaled with 'when to read' guidance. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
f837248
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.