gamma-hello-world
Generate your first Gamma presentation via the API. Use when learning the generate-poll-retrieve workflow, testing API connectivity, or creating a minimal example. Trigger: "gamma hello world", "gamma quick start", "first gamma presentation", "gamma example", "gamma test".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 well-structured description with excellent trigger terms and clear 'what/when' guidance. Its main weakness is that the specificity of capabilities could be stronger — it mentions generating a presentation but doesn't detail the concrete steps or outputs (e.g., polling for completion, retrieving the result). Overall, it serves its purpose well for skill selection.
Suggestions
Expand the capability description to list the concrete actions: e.g., 'Generates a Gamma presentation via the API, polls for completion status, and retrieves the final result' to better convey the full workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma presentation via API) and one action (generate), but doesn't list multiple concrete actions. The 'generate-poll-retrieve workflow' hints at specifics but doesn't fully enumerate them as distinct capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate a first Gamma presentation via the API) and 'when' (learning the workflow, testing API connectivity, creating a minimal example) with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Includes explicit, natural trigger terms that users would actually say: 'gamma hello world', 'gamma quick start', 'first gamma presentation', 'gamma example', 'gamma test'. These are well-chosen and cover common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically a 'hello world' / quick start for the Gamma API. The trigger terms are highly specific ('gamma hello world', 'gamma quick start') and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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 hello-world skill with excellent actionability and clear workflow sequencing. Its main weakness is verbosity from including three complete language implementations inline, which triples the token cost without proportional value. The error handling table and expected output are strong additions that aid practical use.
Suggestions
Keep only one code example inline (e.g., curl or Python) and move the other two to a separate EXAMPLES.md file, linked from the main skill.
Remove the 'Prerequisites' section or reduce it to a single line—Claude can infer these from context and the referenced setup skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Providing three full examples (curl, Node.js, Python) for the same workflow is redundant—one or two would suffice. The overview and pattern sections are efficient, but the triple implementation bloats the content significantly. | 2 / 3 |
Actionability | All three examples are fully executable, copy-paste ready with real endpoints, proper headers, and complete error handling. The expected output JSON and error handling table provide concrete guidance for troubleshooting. | 3 / 3 |
Workflow Clarity | The generate-poll-retrieve pattern is clearly sequenced with explicit steps numbered 1-2-3. Each code example includes validation (checking for 'failed' status, raise_for_status), and the polling loop has clear termination conditions for both success and failure. | 3 / 3 |
Progressive Disclosure | The skill references external resources and a next-step skill, which is good. However, the three full code examples could have been split into a separate EXAMPLES.md file, keeping the main skill leaner with just one example and links to alternatives. | 2 / 3 |
Total | 10 / 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.