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-crafted description for a narrowly scoped skill. It clearly communicates what the skill does, when to use it, and provides explicit trigger terms. The only minor weakness is that the specificity of concrete actions could be slightly more detailed (e.g., mentioning polling for completion status, retrieving the final URL), but for a 'hello world' skill the scope is appropriately limited.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Gamma presentation via API) and a specific workflow (generate-poll-retrieve), but doesn't list multiple concrete actions beyond 'generate your first presentation'. The mention of testing API connectivity and creating a minimal example adds some specificity but remains somewhat surface-level. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate a first Gamma presentation via the API, learn the generate-poll-retrieve workflow, test API connectivity) and 'when' (explicit 'Use when' clause plus a 'Trigger' list with specific phrases). | 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 of how a user would invoke this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it targets a very specific niche (Gamma API hello-world/quickstart scenario) with unique trigger terms like 'gamma hello world' and 'gamma quick start' that are 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, highly actionable hello-world skill with clear workflow sequencing and good error handling guidance. Its main weakness is token inefficiency: three nearly identical code examples in different languages bloat the file significantly when one example plus references to language-specific files would suffice. The content would benefit from choosing one canonical example inline and moving the others to supplementary files.
Suggestions
Keep only one code example (e.g., curl or Python) inline and move the other two to separate referenced files like `examples/hello-world.ts` and `examples/hello-world.py` to improve conciseness and progressive disclosure.
Remove the 'Prerequisites' bullet about Pro account credits if it's already covered in the referenced `gamma-install-auth` skill, to avoid redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides three full code examples (curl, Node.js/TypeScript, Python) that are largely redundant—they all demonstrate the same generate-poll-retrieve pattern. Two of the three could be omitted or moved to a separate file. The prose itself is reasonably lean, but the overall token cost is high due to repetition. | 2 / 3 |
Actionability | All three examples are fully executable, copy-paste ready with real endpoints, proper headers, error handling, and concrete content strings. The expected output JSON, error handling table, and output format table provide specific, actionable reference material. | 3 / 3 |
Workflow Clarity | The three-step generate-poll-retrieve pattern is clearly articulated upfront and then demonstrated with explicit polling loops, status checks for both 'completed' and 'failed', and error handling. The workflow includes validation (checking status, raise_for_status) and a clear feedback loop (poll every 5s, break on terminal states). | 3 / 3 |
Progressive Disclosure | The skill has good section structure and links to external API docs and a next-step skill. However, the three redundant code examples should be split into separate files or a single example chosen for the main skill, with others referenced. No bundle files exist to offload this content to. | 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
3a2d27d
- 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.