gamma-cost-tuning

Optimize Gamma usage costs and manage API spending. Use when reducing API costs, implementing usage quotas, or planning for scale with budget constraints. Trigger with phrases like "gamma cost", "gamma billing", "gamma budget", "gamma expensive", "gamma pricing".

Quality

78%

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-cost-tuning/SKILL.md

Quality

Content

65%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 actionable and reasonably concise with good sequencing, but it inlines reference-grade detail and ignores an existing bundle file rather than linking to it. Batch generation also lacks a pre-flight validation checkpoint.

Suggestions

Signal and link the existing references/implementation.md (e.g., a '## Implementation details' section) instead of inlining overlapping usage-monitoring, quota, and caching code in the body.

Add a validation/checkpoint step before the Step 3 batch generation loop so credit spend is confirmed against the budget tracker before generating across all clients.

Move the credit-tier and plan-comparison reference tables to the bundle file, keeping the body focused on the optimization workflow and a concise summary.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code examples and comparison tables, but reference detail (credit tiers, plan comparison) and some explanatory prose around the EXPENSIVE/CHEAPER/CHEAPEST labels could be trimmed or offloaded to the bundle.	4 / 5
Actionability	Provides concrete TypeScript code for tracking, optimization, templates, budgets, and caching across the common cases, though several referenced helpers (GammaClient, pollUntilDone, generateAndWait) are undefined, slightly limiting copy-paste readiness.	4 / 5
Workflow Clarity	Steps are clearly sequenced (Step 1-5) with budget validation in Step 4, but the batch generation loop in Step 3 (looping over clients to generate presentations) lacks a validation checkpoint before consuming credits, capping batch-operation workflows at 3.	3 / 5
Progressive Disclosure	Section structure is present and a bundle file (references/implementation.md) exists with overlapping detail, but the body never signals or links to it, inlining comparable content instead of pointing to the separate reference.	3 / 5
	Total	14 / 20 Passed

Description

92%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.

The description is clear, specific, and well-triggered, covering both what the skill does and when to use it with natural keyword phrases. It is well-scoped to a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (optimize Gamma usage costs, manage API spending, reducing API costs, implementing usage quotas, planning for scale) with comprehensive coverage of the cost-tuning domain.	5 / 5
Completeness	Explicitly answers both what (optimize costs, manage API spending) and when (use when reducing API costs, implementing quotas, or planning for scale) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides explicit natural trigger phrases ('gamma cost', 'gamma billing', 'gamma budget', 'gamma expensive', 'gamma pricing') that users would say, with good coverage though a few synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to the Gamma cost/billing niche with distinct gamma-prefixed triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 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-cost-tuning/SKILL.md
Commit: 0540a62

Reviewed: about 20 hours 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.