Generate from templates, retrieve exports, and manage sharing via Gamma API. Use when creating content from template gammas, downloading PDF/PPTX/PNG exports, or configuring sharing and folder organization. Trigger: "gamma template", "gamma export", "gamma download PDF", "gamma PPTX", "gamma sharing", "gamma from template".
67
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that concisely covers specific capabilities, provides explicit 'Use when' guidance, and includes well-chosen trigger terms scoped to the Gamma API domain. It uses third-person voice correctly and is clearly distinguishable from other skills. Minor improvement could include mentioning the full product name for users unfamiliar with 'Gamma'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generate from templates, retrieve exports, manage sharing, downloading PDF/PPTX/PNG exports, configuring sharing and folder organization. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate from templates, retrieve exports, manage sharing via Gamma API) and 'when' (explicit 'Use when' clause with specific scenarios plus a dedicated 'Trigger' list). | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger terms like 'gamma template', 'gamma export', 'gamma download PDF', 'gamma PPTX', 'gamma sharing', 'gamma from template' — these are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The 'Gamma API' domain and specific trigger terms like 'gamma template', 'gamma PPTX' create a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with executable TypeScript and curl examples covering template generation, batch operations, exports, and sharing. Its main weaknesses are the lack of validation checkpoints in multi-step and batch workflows, and moderate verbosity from explanatory content that Claude doesn't need (format comparisons, concept definitions). The content would benefit from trimming explanations and adding explicit verification steps.
Suggestions
Add explicit validation checkpoints, especially after batch generation (e.g., 'Verify all results succeeded before proceeding; retry failed items with exponential backoff').
Remove or condense the 'Key Concepts' section and export format comparison table — Claude already understands PDF vs PPTX vs PNG trade-offs.
Add a verification step for template generation: check that the template gamma actually has one page before attempting generation, rather than just documenting the error.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations (e.g., explaining what a template gamma is, what PDF/PPTX/PNG are best for). The export format comparison table and some inline comments add bulk that Claude could infer. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with concrete examples, curl commands, specific API endpoints, and realistic usage scenarios. Code is copy-paste ready with proper imports, error handling, and real-world parameters like rate limiting with p-limit. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but there are no explicit validation checkpoints or feedback loops. For batch operations (Step 2), there's no guidance on what to do when individual items fail beyond logging. The workflow lacks a 'verify before proceeding' pattern, especially important for batch generation which could consume credits. | 2 / 3 |
Progressive Disclosure | The skill references external resources (developer docs links) and a next-step skill, but the body itself is quite long with all content inline. The export format comparison table, error handling table, and curl reference could potentially be in separate reference files. However, for a skill with no bundle files, the inline organization with clear headers is acceptable. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
a04d1a2
Table of Contents
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.