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 with clear 'what' and 'when' clauses, strong trigger terms, and a distinct niche focused on Gamma API v1.0 setup. Its main weakness is that the capability description is somewhat narrow — it could benefit from listing more specific concrete actions beyond initial authentication and first request. Overall, it's a solid description that would perform well in skill selection.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'generates boilerplate code for authentication, validates API key configuration, sends test requests to verify connectivity'.
| 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), but doesn't list multiple concrete actions beyond setup — e.g., no mention of specific endpoints, SDK installation steps, or error handling. | 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 'Trigger' list with concrete phrases). | 3 / 3 |
Trigger Term Quality | Includes a well-curated list of natural trigger terms ('install gamma', 'setup gamma API', 'gamma auth', 'gamma API key', 'configure gamma') that cover common variations a user would naturally say. Also includes technical terms like 'X-API-KEY header' and 'REST API access'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Gamma API v1.0 with distinct triggers like 'gamma auth' and 'gamma API key'. Very unlikely to conflict with other skills unless another skill also targets Gamma API setup. | 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 instructions and executable code examples for multiple languages. Its main weakness is moderate verbosity — the security practices table, dual-language examples, and some explanatory notes could be trimmed or split into separate files. The workflow is well-sequenced with an explicit verification checkpoint.
Suggestions
Trim the API Key Security table — Claude already knows not to commit secrets and to rotate keys; a single line like 'Store in .env, add to .gitignore, rotate periodically' suffices.
Consider moving one of the language examples (Node.js or Python) to a separate reference file to reduce the main skill's token footprint while maintaining progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content — providing both Node.js and Python examples when the skill could pick one or be more compact, the security practices table explains things Claude already knows (never commit keys, rotate regularly), and the prerequisites section states obvious requirements. | 2 / 3 |
Actionability | Provides fully executable code in bash, TypeScript, and Python with copy-paste ready examples. The curl verification command, client wrapper, and Python snippet are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear sequential steps from key generation through environment configuration to verification. Step 3 provides an explicit validation checkpoint (200 = authenticated, 401 = invalid key) before proceeding to actual API usage, and error handling covers recovery paths. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the error handling table, security practices, and dual-language examples could be in separate reference files. The reference to 'gamma-hello-world' for next steps is good, but no bundle files exist to support progressive disclosure. | 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.