apollo-debug-bundle
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-debug-bundleCollect Apollo.io debug evidence for support. Use when preparing support tickets, documenting issues, or gathering diagnostic information for Apollo problems. Trigger with phrases like "apollo debug", "apollo support bundle", "collect apollo diagnostics", "apollo troubleshooting info".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
77%This is a solid, highly actionable debug skill with executable code and clear workflows. Its main weakness is verbosity - the comprehensive TypeScript script and inline bash commands make it lengthy when a more modular approach with external file references would improve token efficiency. The content is well-structured but could benefit from splitting the debug script into a separate file.
Suggestions
Move the TypeScript debug script to a separate file (e.g., scripts/apollo-debug-bundle.ts) and reference it, keeping only a brief usage example inline
Consolidate the Quick Debug Commands section - some commands duplicate what the TypeScript script does
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides useful content but is verbose for its purpose. The 100+ line TypeScript script could be condensed, and some sections like the checklist items are somewhat redundant with the script's functionality. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code, copy-paste ready bash commands, and a complete support ticket template. All code is concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear workflow with numbered checklist sections, explicit verification steps, and a logical progression from environment check to network to request to rate limits. The error handling table provides clear diagnostic paths. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is monolithic with everything inline. The TypeScript script and bash commands could be referenced as separate files. The 'Next Steps' reference to another skill is good. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger term coverage and clear when/what guidance. The main weakness is the lack of specific concrete actions - it describes the general purpose but not the specific diagnostic artifacts or steps involved. The description uses appropriate third person voice throughout.
Suggestions
Add specific concrete actions like 'Collects logs, configuration files, error traces, and system state' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io debug) and general actions (collect evidence, prepare support tickets, gather diagnostic information), but doesn't list specific concrete actions like what files are collected, what logs are gathered, or what diagnostic checks are performed. | 2 / 3 |
Completeness | Clearly answers both what (collect Apollo.io debug evidence for support) and when (preparing support tickets, documenting issues, gathering diagnostic information) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'apollo debug', 'apollo support bundle', 'collect apollo diagnostics', 'apollo troubleshooting info', plus contextual phrases like 'support tickets' and 'documenting issues' that users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Apollo.io debugging and support bundle collection. The explicit 'Apollo' branding and specific trigger phrases make it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
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.