gamma-core-workflow-b
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".
84
82%
Does it follow best practices?
Impact
Pending
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 clearly identifies the Gamma API domain, lists specific concrete actions (template generation, export retrieval in multiple formats, sharing management), and provides explicit trigger guidance with natural user terms. The description is concise, well-structured, and highly distinguishable from other skills.
| 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 export', '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 excellent executable code examples covering template generation, batch operations, export retrieval, and sharing configuration. Its main weaknesses are the lack of explicit validation/retry feedback loops in the workflow (especially for batch operations and expiring download URLs) and the somewhat monolithic structure that could benefit from splitting detailed sections into referenced files. Minor verbosity in the overview and key concepts sections could be trimmed.
Suggestions
Add explicit validation checkpoints and retry logic, especially in Step 2 (batch generation) and Step 4 (download with expiring URLs) — e.g., check response status, retry on transient failures, verify file size after download.
Consider moving the batch generation pattern, curl reference, and sharing configuration into separate referenced files to improve progressive disclosure for this longer skill.
Trim the Overview and Key Concepts sections — Claude doesn't need explanations like 'Template generation lets you replicate a single-page gamma template across multiple variations' when the code examples make this self-evident.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanations (e.g., 'Template generation lets you replicate a single-page gamma template across multiple variations' and the Key Concepts section explaining things Claude can infer). The export format comparison table and error handling table add value, but the overall content could be tightened. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with concrete examples, curl commands for API reference, specific parameter values, and real-world usage patterns like batch generation with rate limiting. Code is copy-paste ready with clear variable names and comments. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from template creation through export and sharing, but there are no explicit validation checkpoints or error recovery feedback loops. For an API workflow involving batch operations (Step 2) and file downloads with expiring URLs, there should be explicit validate-retry patterns rather than just an error table at the end. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and references to external docs and related skills (gamma-core-workflow-a, gamma-common-errors). However, the skill is quite long (~170 lines of content) and could benefit from splitting the batch generation, sharing configuration, and curl reference into separate files rather than inlining everything. | 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 | |
- Commit
70e9fa4
- Reviewed
Table of Contents
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.