gamma-common-errors

Debug and resolve common Gamma API errors. Use when encountering authentication failures, rate limits, generation errors, or unexpected API responses. Trigger with phrases like "gamma error", "gamma not working", "gamma API error", "gamma debug", "gamma troubleshoot".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

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

A usable error reference with concrete payloads and code, but it is a monolithic inline document whose code examples contain syntax errors and whose troubleshooting steps lack verification checkpoints. Splitting detail into real bundle files and fixing the code would lift it significantly.

Suggestions

Replace the invalid '#' comments in the TypeScript blocks with '//' so the withRetry and GammaClient examples are actually executable and copy-paste ready.

Drop the Prerequisites section and other restated-basics boilerplate (e.g. 'Understanding of HTTP status codes') to tighten token efficiency.

Add explicit verification checkpoints to each troubleshooting flow (e.g. 're-run the request to confirm the error is resolved') and split the error reference into actual bundle files referenced from SKILL.md instead of the non-existent 'gamma-debug-bundle'.

Dimension	Reasoning	Score
Conciseness	Mostly reference-style with no concept filler, but the Prerequisites section restates things Claude already knows ('Understanding of HTTP status codes') and the repeated error-JSON-plus-solutions boilerplate could be tightened.	2 / 3
Actionability	Contains real code and concrete commands, but the TypeScript blocks use invalid '#' comments (e.g. '* 1000; # 1000: 1 second in ms' and '// 60 seconds # 60000: 1 minute in ms'), so the examples are not actually executable, and several solution bullets are vague.	2 / 3
Workflow Clarity	Numbered solution lists provide a sequence for each error type, but there are no explicit validation or verification checkpoints confirming a fix resolved the error (only an implicit retry loop for rate limiting).	2 / 3
Progressive Disclosure	Has clear section organization, but ~175 lines of error reference sit inline in one file and the sole external pointer ('gamma-debug-bundle') has no corresponding bundle file, making it a dangling reference.	2 / 3
	Total	8 / 12 Passed

Description

90%

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 description: it states the capability, gives an explicit 'Use when' clause, and lists natural trigger phrases scoped to a distinct Gamma niche. The only weakness is that the action vocabulary is limited to 'debug and resolve' rather than multiple distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Debug and resolve common Gamma API errors') and enumerates error categories (auth, rate limits, generation, unexpected responses), but the action is essentially one verb pair rather than multiple distinct concrete actions as the score-3 anchor requires.	2 / 3
Completeness	Explicitly answers both what ('Debug and resolve common Gamma API errors') and when ('Use when encountering authentication failures, rate limits...') with an explicit 'Use when' clause and trigger phrases.	3 / 3
Trigger Term Quality	Provides natural user-facing phrases ('gamma error', 'gamma not working', 'gamma API error', 'gamma debug', 'gamma troubleshoot') giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Gamma API) with gamma-prefixed trigger phrases, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

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

Reviewed: 1 day 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.