gamma-debug-bundle
Comprehensive debugging toolkit for Gamma integration issues. Use when you need detailed diagnostics, request tracing, or systematic debugging of Gamma API problems. Trigger with phrases like "gamma debug bundle", "gamma diagnostics", "gamma trace", "gamma inspect", "gamma detailed logs".
71
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-debug-bundle/SKILL.mdQuality
Discovery
89%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 solid skill description with strong trigger term coverage and clear 'when to use' guidance. Its main weakness is that the capability descriptions are somewhat generic debugging terms rather than listing specific concrete actions the toolkit performs. The Gamma-specific focus and explicit trigger phrases make it highly distinctive and unlikely to conflict with other skills.
Suggestions
Replace generic terms like 'detailed diagnostics' and 'systematic debugging' with specific concrete actions, e.g., 'capture request/response payloads, analyze Gamma error codes, generate debug bundles with full stack traces'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Gamma integration debugging) and mentions some actions like 'detailed diagnostics', 'request tracing', and 'systematic debugging', but these are somewhat generic debugging terms rather than concrete specific actions like 'capture request/response payloads' or 'analyze error codes'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (comprehensive debugging toolkit for Gamma integration issues, diagnostics, request tracing, systematic debugging) and 'when' (explicit 'Use when' clause and 'Trigger with phrases like' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | The description explicitly lists natural trigger phrases: 'gamma debug bundle', 'gamma diagnostics', 'gamma trace', 'gamma inspect', 'gamma detailed logs'. These are specific, varied, and likely match what users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to 'Gamma' integration debugging with distinct trigger terms all prefixed with 'gamma'. This creates a clear niche that is unlikely to conflict with other debugging or API-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable diagnostic tools for Gamma API debugging, which is its primary strength. However, it is significantly over-verbose with redundant implementations across bash and TypeScript, and all content is packed into a single file rather than being split into referenced scripts. The debugging workflow would benefit from a clearer decision tree connecting the diagnostic steps rather than presenting them as independent tools.
Suggestions
Extract the bash script, TypeScript diagnostic, and debug client into separate bundle files (e.g., scripts/gamma-diagnose.sh, scripts/gamma-diagnose.ts, src/gamma/debug-client.ts) and reference them from SKILL.md with brief descriptions.
Choose one primary diagnostic approach (e.g., the bash curl script for quick checks) and make the TypeScript version a referenced advanced option, rather than presenting both inline.
Add a decision tree or flowchart at the top: 'Run Step 1 → if 401, check API key → if 200 but generation fails, run Step 2 → if latency >2s, check network' to create a proper debugging workflow with explicit branching.
Remove the support ticket template or move it to a separate file—Claude can generate support tickets from context without a template taking up token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines with three large code blocks (bash, TypeScript diagnostic, TypeScript debug client) that are largely redundant—they test the same things in different languages. The support ticket template explains things Claude already knows how to generate. Much of this could be condensed to a single diagnostic script plus the quick reference table. | 1 / 3 |
Actionability | All code blocks are fully executable and copy-paste ready with proper imports, error handling, and run commands. The bash script, TypeScript diagnostic, and debug client are all concrete and complete with specific endpoints, headers, and expected responses. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but the workflow is more of a collection of independent tools than a coherent debugging workflow. There's no clear decision tree (e.g., 'if Step 1 fails with 401, skip to Common Issues; if Step 1 passes, proceed to Step 2'). Validation is present within individual scripts but the overall debugging flow lacks explicit checkpoints and feedback loops between steps. | 2 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no bundle files to offload the lengthy code blocks. The TypeScript diagnostic script (~80 lines) and debug client (~40 lines) should be in separate referenced files. The support ticket template could also be a separate file. There's a reference to 'gamma-rate-limits' but no other structural organization. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.