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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

78%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced debugging skill with executable code and concrete troubleshooting tables, but it suffers from broken progressive disclosure: an orphaned reference file, dangling script paths, and code duplicated between the body and the reference. Conciseness and workflow clarity are good but not maximally lean or gated.

Suggestions

Link references/implementation.md from the body (e.g., 'For the full debug client and debug-bundle export, see [implementation.md](references/implementation.md)') and remove the duplicated debug-client/diagnostic code from the body so there is a single source of truth.

Either add the referenced scripts/gamma-diagnose.ts and src/gamma/debug-client.ts as real files under a scripts/ bundle directory, or stop citing file paths that do not exist in the bundle.

Add an explicit validate→fix→re-run feedback loop and a 'only proceed when connectivity/auth checks pass' gate before the credit-consuming generation test in Step 2.

Dimension	Reasoning	Score
Conciseness	The body is action-dense with executable code and avoids explaining concepts Claude already knows, but the two inline TypeScript scripts (Step 2 diagnostic and Step 3 debug client) overlap each other and duplicate content already present in references/implementation.md, offering a clear tightening opportunity.	4 / 5
Actionability	Provides fully executable, copy-paste-ready bash and TypeScript with explicit run commands ('npx tsx scripts/gamma-diagnose.ts'), plus concrete cause→fix tables and a complete support ticket template covering the common diagnostic cases.	5 / 5
Workflow Clarity	Steps 1–4 are clearly sequenced with per-test PASS/FAIL status checks, but there is no explicit validate→fix→re-run feedback loop or 'only proceed when checks pass' gate between steps, and the credit-consuming generation test in Step 2 lacks a pre-gate.	4 / 5
Progressive Disclosure	references/implementation.md exists but is never linked or signaled from the body, while the body references scripts/gamma-diagnose.ts and src/gamma/debug-client.ts paths that do not exist in the bundle, and content that should live in the reference is duplicated inline rather than split out.	3 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-constructed description that explicitly answers both what the skill does and when to trigger it, with a comprehensive set of natural trigger phrases scoped to a distinct niche. The only weakness is that the named actions overlap somewhat and under-represent the concrete capabilities documented in the body.

Dimension	Reasoning	Score
Specificity	Names the Gamma domain plus several specific actions ('detailed diagnostics, request tracing, systematic debugging of Gamma API problems'), but the actions overlap conceptually and concrete deliverables surfaced in the body (connectivity tests, support ticket templates) are not mentioned, leaving minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does ('Comprehensive debugging toolkit for Gamma integration issues') and when to use it ('Use when you need detailed diagnostics...') with concrete trigger phrases, matching the anchor that requires explicit what-and-when.	5 / 5
Trigger Term Quality	Provides comprehensive, explicitly enumerated natural trigger phrases ('gamma debug bundle', 'gamma diagnostics', 'gamma trace', 'gamma inspect', 'gamma detailed logs') covering the synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Gamma API debugging) with gamma-prefixed distinct triggers, so overlap with other skills is minimal; third-person voice is maintained.	5 / 5
	Total	19 / 20 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
Path: plugins/saas-packs/gamma-pack/skills/gamma-debug-bundle/SKILL.md
Commit: 0540a62

Reviewed: about 17 hours 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.