gamma-prod-checklist

Production readiness checklist for Gamma integration. Use when preparing to deploy Gamma integration to production, or auditing existing production setup. Trigger with phrases like "gamma production", "gamma prod ready", "gamma go live", "gamma deployment checklist", "gamma launch".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is actionable with executable code and a verification script, and is cleanly organized into headed sections. It loses points for redundant inline comments explaining known concepts, for presenting parallel checklist categories rather than a sequenced validated workflow, and for keeping all detail inline with no progressive split.

Suggestions

Remove inline comments that restate common knowledge (e.g. '# 30000: 30 seconds in ms', '# HTTP 200 OK', '# HTTP 503 Service Unavailable') and the repeated timeout annotation to improve token efficiency.

Reorder the checklist into an explicit sequenced workflow with validation checkpoints (e.g. 'verify auth -> validate error handling -> run prod-verify.sh -> only then proceed') so steps have feedback loops.

Split the larger code examples (client config, circuit breaker, verification script) into a scripts/ or references/ file and link to them from a concise overview, enabling progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The checklist is mostly efficient, but inline comments re-explain concepts Claude already knows ('# 30000: 30 seconds in ms', '# HTTP 503 Service Unavailable', '# HTTP 200 OK') and the timeout comment repeats across examples. It is not a 3 because these annotations add unnecessary tokens; not a 1 because the body is not padded with conceptual explanation.	2 / 3
Actionability	Provides concrete, executable TypeScript and bash examples using real libraries (Sentry, opossum circuit breaker, curl ping verification) plus specific checklist items, all copy-paste ready. It is not a 2 because the code is complete and runnable rather than pseudocode or abstract.	3 / 3
Workflow Clarity	The nine sections are parallel concern categories rather than a sequenced process with validation checkpoints between steps; the final verification script helps but no feedback loop ties the sections together. It is not a 3 because there is no explicit 'do, validate, then proceed' sequence; not a 1 because a verification script and ordered section numbering do provide some sequence.	2 / 3
Progressive Disclosure	Content is well-organized into clearly headed sections, but everything is inline in a single ~170-line file with no overview pointing to one-level-deep references (no references/ scripts/ or assets/ bundle exists). It is not a 3 because there is no signaled split of detail into separate files; not a 1 because organization is clear rather than a monolithic wall of text.	2 / 3
	Total	9 / 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.

The description clearly states what the skill does and when to use it, with strong natural-language trigger phrases and a well-scoped niche. The only weakness is specificity, where the capability is described as a single checklist rather than enumerated concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Production readiness checklist for Gamma integration') and two use cases (deploy, audit) but does not list multiple specific concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor. It is not a 3 because no enumeration of distinct concrete capabilities is given.	2 / 3
Completeness	Explicitly answers both 'what' (production readiness checklist for Gamma integration) and 'when' ('Use when preparing to deploy Gamma integration to production, or auditing existing production setup'), matching the top anchor. It is not a 2 because the 'when' is explicit, not merely implied.	3 / 3
Trigger Term Quality	Provides good coverage of natural trigger phrases a user would actually say ('gamma production', 'gamma prod ready', 'gamma go live', 'gamma deployment checklist', 'gamma launch'), matching the top anchor. It is not below 3 because the terms are natural and varied rather than jargon or generic.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Gamma integration production readiness) with distinct Gamma-specific triggers, making conflict with other skills unlikely. It is not a 2 because the triggers are specific and branded rather than overlapping generic terms.	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: 6e3a65f

Reviewed: 4 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.