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".
77
73%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-local-dev-loop/SKILL.mdQuality
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 local development) and provides explicit trigger terms. The 'when' clause is well-defined with multiple use cases. The main weakness is that the specific capabilities could be more concrete—listing actual setup steps, tools, or configurations rather than general categories of actions.
Suggestions
Add more concrete actions to improve specificity, e.g., 'Generates config files, sets up authentication tokens, creates mock server endpoints, and scaffolds test scripts for Gamma API integration.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma API integration, local development workflow) and some actions (building automation scripts, testing API calls, configuring dev environment with mock responses), but doesn't list multiple concrete specific actions like step-by-step setup tasks or specific tools/configurations involved. | 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' which are terms users would use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to 'Gamma API' local development, which is a clear niche. The combination of 'Gamma' + 'local dev' + 'mock API' makes it highly unlikely to conflict with other skills. The explicit trigger terms further reduce conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with fully executable, well-structured TypeScript code covering the complete local dev workflow. However, it suffers from being monolithic — the extensive code blocks for the mock server, client, polling helper, and tests should be split into referenced files with the SKILL.md serving as an overview. Adding explicit validation checkpoints between steps (e.g., confirming the mock server works before running integration tests) would improve workflow clarity.
Suggestions
Split the large code blocks (client.ts, poll.ts, mock-server.ts, integration.test.ts) into bundle files and reference them from SKILL.md, keeping only a brief description and usage example inline.
Add explicit validation checkpoints, e.g., 'After starting the mock server, verify it responds: curl http://localhost:9876/v1.0/themes' before proceeding to integration tests.
Trim the overview paragraph — Claude doesn't need to be told that 'Gamma is a REST API with no SDK' or that 'the dev loop centers on HTTP request/response testing'; jump straight to the setup steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with extensive code blocks that are mostly useful, but the overview paragraph explains what a REST API dev loop is (which Claude knows), and some code (like the full mock server implementation) could be summarized or referenced externally. The error handling table and dev loop summary are efficient, but overall the skill is heavier than necessary. | 2 / 3 |
Actionability | Every step includes fully executable TypeScript code, concrete project structure, runnable npm scripts, and a complete integration test. The code is copy-paste ready with proper imports, error handling, and type annotations. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from project structure through client, polling, mock server, scripts, and tests. However, there are no explicit validation checkpoints between steps (e.g., 'verify the mock server responds before running tests') and no feedback loops for error recovery during the setup process. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of code — approximately 200+ lines of inline TypeScript that could be split into referenced files. With no bundle files provided, all the detailed implementation (mock server, client wrapper, poll helper, tests) is crammed into a single document rather than being appropriately distributed across referenced files. | 1 / 3 |
Total | 8 / 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.