gamma-install-auth
Set up Gamma API v1.0 authentication and first request. Use when configuring API keys, setting up X-API-KEY header, or initializing Gamma REST API access in a project. Trigger: "install gamma", "setup gamma API", "gamma auth", "gamma API key", "configure gamma".
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 skill description that clearly identifies its niche (Gamma API v1.0 setup/authentication), provides explicit trigger guidance with natural user phrases, and answers both what and when. The main weakness is that the capability description is somewhat narrow — it could benefit from listing a few more specific actions beyond initial setup, but for a setup-focused skill this is appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma API v1.0) and some actions (authentication, first request, configuring API keys, setting up X-API-KEY header, initializing access), but the actions are somewhat narrow and not comprehensively listed beyond setup tasks. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up Gamma API v1.0 authentication and first request) and 'when' (explicit 'Use when' clause with specific scenarios, plus a dedicated 'Trigger' list with natural phrases). | 3 / 3 |
Trigger Term Quality | Includes explicit, natural trigger terms like 'install gamma', 'setup gamma API', 'gamma auth', 'gamma API key', 'configure gamma' — these are phrases users would naturally say. Also includes technical terms like 'X-API-KEY header' that developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Gamma API v1.0 with distinct triggers mentioning 'gamma' by name. Very unlikely to conflict with other skills unless another Gamma-specific skill exists. | 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 solid, actionable skill with clear step-by-step workflow and executable code examples in multiple languages. Its main weakness is verbosity — it includes security best practices, error handling tables, and credit system details that either Claude already knows or could be in referenced files. The core setup flow (Steps 1-3) is excellent and well-validated.
Suggestions
Move the error handling table, security practices table, and credit system details to a separate reference file to reduce token usage in the main skill.
Remove the prerequisites section — Claude knows it needs an HTTP client and a runtime to make API calls.
Consider keeping only one language example (or making the second a brief one-liner) since both Node.js and Python examples demonstrate the same verification concept.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements — the Python and Node.js examples are somewhat redundant (both do the same verification), the security practices table and error handling table add bulk that Claude likely already knows, and the prerequisites section states obvious things like needing curl or an HTTP client library. | 2 / 3 |
Actionability | Fully executable code examples in bash, TypeScript, and Python; specific curl command for verification with expected status codes; concrete step-by-step instructions for key generation with exact UI navigation paths. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear sequential steps from key generation through environment setup to verification. Step 3 provides an explicit validation checkpoint (200 vs 401) before proceeding to client code. Error handling table provides a feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The skill has reasonable structure with clear sections, but inlines a fair amount of reference material (error handling table, security practices, credit system details) that could be in separate files. The 'Next Steps' reference to gamma-hello-world is good, but the main file is longer than it needs to be for an overview. | 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
c8a915c
- 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.