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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with real, executable diagnostic code and useful quick-reference tables, but it is token-heavy because full scripts are inlined instead of pointing to the existing implementation reference. Workflow and progressive-disclosure suffer from the lack of validation checkpoints and the unlinked/duplicated bundle file.

Suggestions

Replace the full inline diagnostic script and debug-client code with concise summaries plus a clearly signaled link to references/implementation.md, keeping only the short curl quick-start inline.

Add explicit validation checkpoints between steps (e.g., 'run the connectivity test first; only proceed to the generation test if auth passes') to turn the parallel tools into a gated workflow.

Resolve the path mismatch: the body cites scripts/gamma-diagnose.ts and src/gamma/debug-client.ts, but those files/directories do not exist — align inline code with the actual bundle layout or create the referenced files.

Dimension	Reasoning	Score
Conciseness	The body embeds two full inline implementations (a ~90-line diagnostic script and a debug client) that largely duplicate references/implementation.md, so it is mostly efficient but carries significant bloat that should be externalized.	2 / 3
Actionability	Provides fully executable curl and TypeScript scripts against real endpoints, a run command, a debug-client factory, a ticket template, and symptom-to-fix tables — copy-paste ready and concrete.	3 / 3
Workflow Clarity	Steps 1-4 are sequenced but read as parallel tools rather than a validation-gated process; the diagnostic script's internal PASS/FAIL checks provide some recovery feedback but there are no explicit checkpoints chaining the steps.	2 / 3
Progressive Disclosure	A bundle file references/implementation.md exists but is never linked from the body, while the debug client and diagnostic script are duplicated inline; content that should be split is inline and the existing reference is not signaled.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is specific, complete, and well-scoped to the Gamma integration niche, with explicit 'what' and 'when' guidance plus concrete trigger phrases. It is slightly padded by the enumeration of near-synonymous trigger terms, but every dimension is clearly met.

Dimension	Reasoning	Score
Specificity	Names the Gamma API domain and lists multiple concrete actions ('detailed diagnostics, request tracing, or systematic debugging'), matching the multi-action anchor.	3 / 3
Completeness	Explicitly states both what it does ('Comprehensive debugging toolkit for Gamma integration issues') and when to use it ('Use when you need detailed diagnostics, request tracing...').	3 / 3
Trigger Term Quality	Provides a set of natural trigger phrases ('gamma debug bundle', 'gamma diagnostics', 'gamma trace', 'gamma inspect', 'gamma detailed logs') a user would plausibly say, giving good coverage though all are gamma-prefixed.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Gamma API issues with gamma-prefixed triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.