gamma-sdk-patterns

Reusable patterns for the Gamma REST API (no SDK exists). Use when building typed wrappers, generation helpers, template factories, or error handling for Gamma. Trigger: "gamma patterns", "gamma client wrapper", "gamma best practices", "gamma API helper", "gamma code structure".

Quality

88%

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

Quality

Content

77%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.

A strong, highly actionable code-patterns skill with executable TypeScript and clear sequencing, weakened mainly by duplicative summary tables and a monolithic structure that foregoes progressive disclosure. Pulling the type definitions and endpoint reference into a separate file would tighten SKILL.md into a true overview.

Suggestions

Remove or trim the "Error Handling" and "API Endpoints Reference" tables, since they restate the GammaApiError/withRetry/pollUntilDone/getGamma constructs and the six endpoints already shown in the code.

Move the detailed TypeScript type definitions (GenerateRequest, GenerateResult, TemplateRequest) and the endpoint table into a references file (e.g. references/api-types.md), leaving SKILL.md as a lean overview with one-level-deep links.

Add a brief validation checkpoint in generateAndWait (e.g. assert result.status === "completed" and gammaUrl/exportUrl are present) so the happy path has an explicit verification step before returning.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, executable TypeScript with no concept-explanation padding, but the "Error Handling" and "API Endpoints Reference" tables restate constructs and endpoints already shown in the code, adding duplicative tokens.	2 / 3
Actionability	Every step ships complete, typed, copy-paste-ready TypeScript (client, error class, polling, generate-and-wait, templates, retry) with concrete usage examples.	3 / 3
Workflow Clarity	Steps 1–6 form a clear generate-poll-retrieve sequence with explicit error-recovery feedback loops: pollUntilDone checks completed/failed status with a timeout, and withRetry retries 429/5xx while throwing 4xx.	3 / 3
Progressive Disclosure	Sections are well organized with external Resources links, but the skill is a single ~260-line monolithic file with all types, code, and endpoint tables inline and no split-out reference files to keep SKILL.md as an overview.	2 / 3
	Total	10 / 12 Passed

Description

100%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 well-crafted description that states concrete capabilities, provides explicit "Use when" guidance and natural trigger terms, and occupies a clearly distinct niche. The only blemish is cosmetic: odd mid-sentence line breaks and a redundant trailing blank inside the YAML string that do not affect the rendered text.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "building typed wrappers, generation helpers, template factories, or error handling for Gamma" — rather than vague language.	3 / 3
Completeness	It clearly answers what ("Reusable patterns for the Gamma REST API (no SDK exists)") and when ("Use when building typed wrappers..." plus an explicit Trigger list), satisfying both halves.	3 / 3
Trigger Term Quality	Explicit triggers ("gamma patterns", "gamma client wrapper", "gamma best practices", "gamma API helper", "gamma code structure") give good coverage of phrases a user would naturally say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The Gamma REST API niche is specific and all triggers are gamma-prefixed, making conflict with other skills unlikely.	3 / 3
	Total	12 / 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-sdk-patterns/SKILL.md
Commit: 4c47e33

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.