gamma-deploy-integration

Deploy Gamma-integrated applications to production environments. Use when deploying to Vercel, AWS, GCP, or other cloud platforms with proper secret management and configuration. Trigger with phrases like "gamma deploy", "gamma production", "gamma vercel", "gamma AWS", "gamma cloud deployment".

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 skill is highly actionable with complete, executable deployment snippets for Vercel, AWS, GCP, and GitHub Actions. It loses points for absent validation checkpoints in production-deploy workflows, stray/incorrect inline comments, and a monolithic structure that could offload per-platform detail into references.

Suggestions

Add validation checkpoints after each deploy step (e.g. verify `vercel inspect` URL is READY, check `aws lambda get-function` LastUpdateStatus, confirm `gcloud run services describe` is ready) before declaring success.

Remove noisy or wrong code comments (`# HTTP 200 OK`, `# 2010 = configured value`, `# 256 bytes`) so the snippets stay lean and accurate.

Split each platform's full tutorial into a one-level-deep reference file (e.g. references/vercel.md, references/aws-lambda.md) and keep SKILL.md as a decision/overview that links out.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable blocks with little padding, but it carries unnecessary inline noise such as `# HTTP 200 OK`, `# 2010 = configured value`, `# 2016 = configured value`, and an incorrect `# 256 bytes` (MemorySize is in MB), placing it at 'mostly efficient but could be tightened' rather than the every-token-earns-its-place level.	2 / 3
Actionability	Each platform ships fully executable bash, JSON, TypeScript, YAML, and Dockerfile snippets with specific commands and expected placeholders (e.g. `vercel --prod`, `gcloud run deploy ... --set-secrets`), making it copy-paste ready per the top anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced per platform (Step 1/2/3) but production deployment is a destructive, outward-facing operation with no validation checkpoints or success-verification loops, so per the destructive-operations rule workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	No bundle files exist, and the full four-platform guide is a monolithic inline document; sections are well organized with headers, but per-platform deep dives that could live in one-level-deep reference files are inlined, matching 'some structure but content that should be separate is inline.'	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 cleanly answers both what and when with distinctive gamma-prefixed trigger phrases and good natural-language coverage. Its only weakness is specificity: the capability description leans on one verb (deploy) plus vague modifiers rather than enumerating multiple concrete actions.

Suggestions

Expand the capability sentence into discrete actions, e.g. 'Deploy Gamma-integrated applications to Vercel, AWS, or GCP, wire production API keys into platform secret stores, and configure build/environment settings.'

Replace 'proper secret management and configuration' with the concrete steps you actually perform so the description reads as a list of actions rather than a modifier phrase.

Dimension	Reasoning	Score
Specificity	"Deploy Gamma-integrated applications to production environments ... with proper secret management and configuration" names the domain and a couple of supporting concerns but rests on a single concrete verb (deploy); secret management and configuration are stated as modifiers rather than listed discrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what ("Deploy Gamma-integrated applications to production environments") and when ("Use when deploying to Vercel, AWS, GCP, or other cloud platforms") plus explicit triggers, clearly answering both questions, so it sits at the top anchor rather than the 'what present but when only implied' level.	3 / 3
Trigger Term Quality	Explicit trigger phrases "gamma deploy", "gamma production", "gamma vercel", "gamma AWS", "gamma cloud deployment" give good coverage of natural terms a user would plausibly say, matching the 'good coverage of natural terms' anchor rather than the partial-coverage level below.	3 / 3
Distinctiveness Conflict Risk	The gamma-scoped triggers ("gamma deploy", "gamma production") carve a clear niche tied to Gamma-integrated deployments, making it unlikely to fire for unrelated skills.	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: about 5 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.