gamma-performance-tuning

Optimize Gamma API performance and reduce latency. Use when experiencing slow response times, optimizing throughput, or improving user experience with Gamma integrations. Trigger with phrases like "gamma performance", "gamma slow", "gamma latency", "gamma optimization", "gamma speed".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

A highly actionable, code-dense skill body with clear sequencing and useful reference tables. Its main weaknesses are the absence of validation feedback loops for the batch operation and an orphaned reference file that duplicates inline content without being linked.

Suggestions

Add an explicit validation/retry checkpoint to the Step 3 batch-generation flow (e.g., check per-item status, retry failures, and verify the batch completed) so workflow clarity is not capped.

Link references/implementation.md from SKILL.md and move the overlapping caching, parallel-request, and connection-pooling detail there, keeping SKILL.md as a lean overview with one-level-deep references.

Add a brief 'Quick start' or prioritization note so Claude knows which optimization to apply first given a symptom (e.g., latency vs. throughput vs. cold start).

Dimension	Reasoning	Score
Conciseness	The body is code-forward and assumes Claude's competence, with lean explanatory comments and reference tables rather than padding about basic concepts; every section earns its place.	3 / 3
Actionability	Each step provides complete, executable TypeScript with imports and full function bodies, plus concrete performance-target and error-handling tables that are copy-paste ready.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1-6) but they are independent optimization techniques rather than a fragile pipeline, and the batch-generation operation lacks explicit validation/checkpoint feedback loops, capping clarity at 2.	2 / 3
Progressive Disclosure	Sections are well organized, but the body inlines substantial code that overlaps with the provided references/implementation.md, which is never referenced or signaled from SKILL.md, leaving a bundle file orphaned and content that could be split instead inline.	2 / 3
	Total	10 / 12 Passed

Description

90%

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

A well-constructed description that clearly answers both what and when, with natural trigger phrases and a distinct Gamma-performance niche. It is only slightly limited by the relative abstractness of its action verbs.

Dimension	Reasoning	Score
Specificity	Names the Gamma domain and a couple of actions ('Optimize Gamma API performance and reduce latency'), but the verbs are somewhat abstract compared to a fully concrete action list, so it is not comprehensive.	2 / 3
Completeness	Explicitly states what it does ('Optimize Gamma API performance and reduce latency') and when to use it ('Use when experiencing slow response times, optimizing throughput...') with explicit trigger phrases.	3 / 3
Trigger Term Quality	Lists natural phrases a user would actually say ('gamma performance', 'gamma slow', 'gamma latency', 'gamma optimization', 'gamma speed') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Gamma performance with distinct performance-oriented triggers, making it unlikely to fire for unrelated skills; minor potential overlap with cost-tuning is bounded by the explicit trigger list.	3 / 3
	Total	11 / 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: 1628598

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.