gamma-core-workflow-a
Generate presentations, documents, and webpages via Gamma API. Use when creating content from text prompts, configuring themes, image styles, text modes, and output formats. Trigger: "gamma generate", "gamma presentation from text", "gamma AI slides", "gamma create deck", "gamma content generation".
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 clearly identifies the Gamma API as the tool, lists specific output types (presentations, documents, webpages), and provides both a 'Use when' clause and explicit trigger terms. The product-specific naming ensures high distinctiveness, and the description is concise without unnecessary fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate presentations, documents, and webpages' and details configurable aspects like 'themes, image styles, text modes, and output formats'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate presentations, documents, webpages via Gamma API with configurable themes/styles/formats) and 'when' (explicit 'Use when' clause plus a dedicated 'Trigger' list with specific phrases). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'gamma generate', 'gamma presentation from text', 'gamma AI slides', 'gamma create deck', 'gamma content generation'. These cover multiple natural phrasings a user might use, all anchored to the 'Gamma' product name for disambiguation. | 3 / 3 |
Distinctiveness Conflict Risk | The 'Gamma API' branding and specific trigger terms like 'gamma generate' and 'gamma AI slides' create a very clear niche. This is unlikely to conflict with generic presentation or document skills due to the product-specific anchoring. | 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 well-structured, highly actionable skill with excellent code examples covering the full Gamma generation API. Its main weaknesses are moderate verbosity (inline content that could be referenced separately) and missing validation checkpoints in the workflow, particularly around credit verification before batch operations and result quality checks. The progressive build from simple to complex usage is effective but the document tries to be both a tutorial and a reference, making it longer than necessary.
Suggestions
Extract the API Parameters Reference table, Credit Cost table, and Error Handling table into a separate REFERENCE.md file, keeping only the essential workflow steps in SKILL.md
Add explicit validation checkpoints: check credit balance before generation, verify generation status before accessing exportUrl, and add a verification step after batch operations to confirm all outputs are accessible
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code examples, but includes some unnecessary verbosity like the Overview section restating what's in the frontmatter, the Prerequisites section, and Step 3's text mode comparison which could be a simple table. The parameter reference table is useful but some inline comments in code are slightly redundant. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code examples, a curl reference, complete parameter tables with types and defaults, and concrete examples covering basic through advanced usage. Code is copy-paste ready with realistic content prompts and proper error handling patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from basic to advanced usage, but the batch generation step (Step 5) lacks validation/verification beyond logging success/failure. There are no explicit checkpoints like verifying credit balance before batch operations or validating that the generation result is satisfactory before proceeding. The error handling table helps but is separate from the workflow rather than integrated as validation checkpoints. | 2 / 3 |
Progressive Disclosure | The content references external resources and a next skill ('gamma-core-workflow-b'), but the SKILL.md itself is quite long (~170 lines of content) with all parameter details, six steps, credit tables, and error handling inline. The parameter reference, credit costs, and error handling tables could be split into separate reference files to keep the main skill focused on the core workflow. | 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
a04d1a2
- 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.