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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/gamma-pack/skills/gamma-performance-tuning/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

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

The content is highly actionable with complete executable code and a clean overview-plus-reference structure. Its main weaknesses are missing validation/feedback checkpoints for batch and performance workflows and some redundant explanatory tables that inflate token use.

Suggestions

Add validation/feedback checkpoints to the workflow (e.g., measure latency before and after each optimization; verify a cache hit via log or TTL check; retry/backoff on poll failure) so batch and tuning steps form a measure-fix-retry loop rather than one-shot steps.

Link references/implementation.md explicitly from the body (e.g., in an 'Advanced configuration' pointer) and move the duplicate keep-alive/connection-pool code out of SKILL.md into that reference to reduce redundancy.

Tighten the three tables (performance characteristics, performance targets, error handling) by merging or trimming entries Claude can infer, keeping only the non-obvious thresholds and causes.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable code per step, but the performance characteristics table, performance targets table, and error-handling table repeat context Claude could largely infer, and Step 6 re-explains connection reuse; it could be tightened.	3 / 5
Actionability	Every step provides complete, copy-paste ready TypeScript with imports, named functions, and concrete parameters, covering the common cases (polling, caching, batching, content tuning, preload, keep-alive).	5 / 5
Workflow Clarity	The six steps are sequenced, but this is a batch/performance workflow with no validation checkpoints or feedback loops (e.g., verifying a cache hit, measuring latency before/after, retry on failure), which per the guidelines caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The SKILL.md is a well-structured overview with clear section headers and points to a real one-level-deep references/implementation.md; minor gaps in that the reference is not linked from the body and some detail (e.g., full client config) lives in the reference rather than inline.	4 / 5
	Total	15 / 20 Passed

Description

80%Weight 40%Scale 1-5

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 strong description that clearly states what the skill does and when to trigger it, with a thorough set of natural trigger phrases. It is slightly held back by action phrasing that is more general than the most specific anchors.

Dimension	Reasoning	Score
Specificity	The description names the domain and concrete actions ('Optimize Gamma API performance and reduce latency', 'optimizing throughput', 'improving user experience') but these are somewhat high-level and not as granular as the score-4 anchor's multiple specific actions.	3 / 5
Completeness	It explicitly answers both what ('Optimize Gamma API performance and reduce latency') and when ('Use when experiencing slow response times...') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	It lists comprehensive natural trigger phrases ('gamma performance', 'gamma slow', 'gamma latency', 'gamma optimization', 'gamma speed') that a user would plausibly say, with good synonym coverage.	5 / 5
Distinctiveness Conflict Risk	The 'gamma'-prefixed triggers carve a clear niche distinct from generic performance skills, with minimal overlap risk; it is mostly distinct though the general performance framing leaves slight overlap with broad tuning skills.	4 / 5
	Total	17 / 20 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
Path: plugins/saas-packs/gamma-pack/skills/gamma-performance-tuning/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.