gamma-local-dev-loop
Set up local development workflow for Gamma API integration. Use when building automation scripts, testing API calls locally, or configuring a dev environment with mock responses. Trigger: "gamma local dev", "gamma development setup", "gamma test locally", "gamma mock API", "gamma dev workflow".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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, explicit trigger terms, and a distinct niche around Gamma API local development. The main weakness is that the specific capabilities could be more granular—listing concrete setup steps rather than general categories like 'building automation scripts'. Overall it performs well across all dimensions.
Suggestions
Add more concrete actions to improve specificity, e.g., 'install dependencies, configure API keys, set up mock server, run integration tests' instead of general phrases like 'building automation scripts'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma API integration, local development) and some actions (building automation scripts, testing API calls, configuring dev environment with mock responses), but doesn't list multiple concrete specific actions like 'install dependencies, configure environment variables, set up mock server'. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up local development workflow for Gamma API integration) and 'when' (building automation scripts, testing API calls locally, configuring dev environment with mock responses), with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'gamma local dev', 'gamma development setup', 'gamma test locally', 'gamma mock API', 'gamma dev workflow'. Also includes natural phrases like 'automation scripts', 'testing API calls locally', and 'mock responses'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to 'Gamma API' local development, which is a clear niche. The combination of 'Gamma' + 'local dev' + 'mock API' makes it very 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 skill with complete executable code for every step of the local dev workflow. Its main weakness is length — inlining the full mock server, client, poll helper, and integration tests makes it token-heavy when some of these could be referenced files. The workflow sequencing and error handling tables are strong additions.
Suggestions
Move the full mock server and integration test code into referenced files (e.g., 'See [mock-server.ts](examples/mock-server.ts)') and keep only key snippets inline to improve conciseness.
Remove the overview paragraph explaining what the dev loop centers on — Claude can infer this from the steps themselves.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial executable code which is valuable, but is quite lengthy (~200 lines). The overview paragraph explains what a REST API dev loop is, which Claude already knows. Some code blocks (like the full mock server) could be referenced externally rather than inlined. However, most content is functional code rather than explanation. | 2 / 3 |
Actionability | Excellent actionability — every step includes fully executable TypeScript code, complete package.json scripts, and a working mock server. The client wrapper, poll helper, mock server, and integration tests are all copy-paste ready with no pseudocode. | 3 / 3 |
Workflow Clarity | The 6-step sequence is clearly ordered from project structure through client creation, polling, mock server, scripts, and testing. The dev loop summary table provides an excellent checkpoint overview showing which commands hit live API vs mock. Error handling table covers common failure modes with fixes. | 3 / 3 |
Progressive Disclosure | The skill is quite long with all code inlined — the mock server, client wrapper, and integration tests could reasonably be split into referenced files. There are references to related skills (gamma-install-auth, gamma-sdk-patterns) and external docs, but the main content is monolithic. For a skill of this size, better splitting would improve navigation. | 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.