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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/gamma-pack/skills/gamma-common-errors/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The body is a solid, actionable error reference with concrete commands and code, but it functions as a flat catalog rather than a guided debugging workflow, and its single bundle reference is dangling. Tightening prerequisite boilerplate and either shipping or removing the referenced bundle would raise quality.

Suggestions

Replace the flat error catalog with a short diagnostic workflow (e.g. check API status -> verify auth key -> inspect error code -> apply category fix) with a validation/retry checkpoint, to lift workflow_clarity above 2.

Remove or trim the Prerequisites boilerplate ("Understanding of HTTP status codes") and any illustrative GammaClient blocks that do not add executable value, to improve conciseness.

Either provide the referenced `gamma-debug-bundle` files under references/scripts/assets or remove the dangling "Proceed to `gamma-debug-bundle`" Next Steps line, so progressive disclosure points to real, one-level-deep material.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — error JSON, numbered solutions, and code snippets — but the Overview/Prerequisites lines (e.g. "Understanding of HTTP status codes") state knowledge Claude already has, and several illustrative GammaClient blocks could be trimmed, so it is not fully lean.	2 / 3
Actionability	It provides concrete executable guidance: shell commands (`echo $GAMMA_API_KEY`), header names (`X-RateLimit-Remaining`), a runnable retry/backoff function, and a typed error-handling pattern with real SDK class names.	3 / 3
Workflow Clarity	Content is organized as a per-error-type reference catalog with numbered solution lists, but there is no sequenced diagnostic workflow or validation checkpoint; it reads as a lookup table rather than a guided multi-step process.	2 / 3
Progressive Disclosure	Sections are logically grouped by error category, but all reference material lives inline in one ~174-line file and the only external pointer ("Proceed to `gamma-debug-bundle`") targets a bundle that is not present in references/scripts/assets, so navigation is only partially realized.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 explicitly covers what and when, uses natural trigger phrases, and is well-scoped to the Gamma API error niche. Its only weakness is moderate action specificity, naming debug/resolve rather than enumerating concrete operations.

Dimension	Reasoning	Score
Specificity	"Debug and resolve common Gamma API errors" names the domain and two verbs (debug, resolve) plus error categories, but it does not list multiple distinct concrete actions comparable to 'extract, fill, merge', so it sits at the domain-and-some-actions level rather than comprehensive.	2 / 3
Completeness	It explicitly states what ("Debug and resolve common Gamma API errors") and when ("Use when encountering authentication failures, rate limits, generation errors, or unexpected API responses"), satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	It supplies natural phrases a user would actually say — "gamma error", "gamma not working", "gamma API error", "gamma debug", "gamma troubleshoot" — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Gamma-specific niche and gamma-prefixed trigger phrases make it unlikely to fire for unrelated skills, giving it a clear distinct niche.	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
Path: plugins/saas-packs/gamma-pack/skills/gamma-common-errors/SKILL.md
Commit: 4c47e33

Reviewed: 3 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.