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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, code-forward dev-loop guide: fully executable, clearly sequenced, with verification via the integration test and an error-handling feedback table. It respects the context window by avoiding concept-explaining fluff and is appropriately self-contained with no nested references.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and lean: the overview is a single sentence, no concepts Claude already knows are over-explained, and supporting material is delivered via concise tables (Dev Loop Summary, Error Handling) and executable code blocks rather than prose padding.	3 / 3
Actionability	Every step ships complete, executable TypeScript (client wrapper, poll helper, mock server, integration test) plus concrete package.json scripts; the code is copy-paste ready with no pseudocode placeholders.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced from project structure through the integration test, which serves as the verification checkpoint, and the Error Handling table provides explicit feedback loops for recovery.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the skill is a self-contained, well-sectioned guide (Overview, Prerequisites, Steps, Dev Loop Summary, Error Handling, Resources, Next Steps) with no nested references, and the inline code is exactly what the user must create.	3 / 3
	Total	12 / 12 Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is complete and distinctive with explicit what/when guidance and domain-specific triggers, but its headline capability is somewhat abstract and the trigger phrases feel artificially constructed rather than natural. Tightening the lead to concrete verbs and using more organic phrasing would raise the specificity and trigger-term scores.

Suggestions

Lead with concrete verbs naming the skill's actual capabilities (e.g., 'Scaffold a Gamma API client, spin up a local mock server, and run integration tests offline') instead of the broad 'Set up local development workflow'.

Replace formulaic 'gamma X' trigger phrases with more natural phrasings a user would actually say, such as 'set up gamma locally', 'test the gamma API without hitting the live endpoint', or 'mock the gamma API'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Gamma API integration') and several actions ('building automation scripts, testing API calls locally, or configuring a dev environment with mock responses'), but the headline 'Set up local development workflow' is broad and the actions read as use-cases rather than a comprehensive list of concrete capabilities.	2 / 3
Completeness	It explicitly answers both what ('Set up local development workflow for Gamma API integration') and when ('Use when building automation scripts, testing API calls locally...') with an explicit trigger clause, satisfying the full completeness bar.	3 / 3
Trigger Term Quality	Five trigger phrases are provided ('gamma local dev', 'gamma development setup', 'gamma test locally', 'gamma mock API', 'gamma dev workflow'), giving decent coverage, but they are formulaic 'gamma X' constructions that feel keyword-stuffed rather than natural phrases a user would organically say.	2 / 3
Distinctiveness Conflict Risk	The skill occupies a clear niche (Gamma API local dev) and all triggers are 'gamma'-prefixed, making it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 6e3a65f

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.