gamma-multi-env-setup

Configure Gamma across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Gamma configurations. Trigger with phrases like "gamma environments", "gamma staging", "gamma dev prod", "gamma environment setup", "gamma config by env".

Quality

86%

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

Quality

Content

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

A well-structured, highly actionable body with executable code across all environments and useful checklist/troubleshooting tables. The main weakness is progressive disclosure: the bundle reference file is orphaned and its content duplicated inline rather than linked.

Suggestions

Replace the inlined config/secrets/guards/CI code blocks with concise summaries and point to references/implementation.md for the full implementations, eliminating the duplication.

Add an explicit '## Validate' step (e.g., run a config sanity check or a mock-mode smoke test) before the CI/CD deployment step to close the workflow validation gap.

Reference implementation.md explicitly in the body (e.g., a '## Implementation details — see [implementation.md](references/implementation.md)') so the bundle file is discoverable rather than orphaned.

Dimension	Reasoning	Score
Conciseness	Mostly lean with executable TypeScript/bash/YAML and minimal concept over-explanation; the Overview's SaaS note is a useful domain fact. Not a 5 because the body duplicates config, env-file, secrets, guards, and CI/CD content that also appears in references/implementation.md, adding redundant tokens.	4 / 5
Actionability	Fully executable, copy-paste-ready TypeScript (config, factory, secrets, guards), bash env files, and a CI/CD YAML workflow covering dev/test/staging/production, matching the anchor-5 bar of concrete examples covering common cases.	5 / 5
Workflow Clarity	Six clearly sequenced steps with an Environment Checklist and an Error Handling troubleshooting table acting as checkpoints. Not 5 because there is no explicit 'validate the configuration works' feedback loop before deploying; the destructive/batch cap does not apply since setup is configuration, but validation gaps remain.	4 / 5
Progressive Disclosure	Good section structure exists, but references/implementation.md is never referenced from the body while its content (config interface, env files, secrets, guards, CI) is inlined and largely duplicated. Matches anchor 3: references present but not clearly signaled and content that should be separate is inline, rather than anchor 2 because section organization is sound.	3 / 5
	Total	16 / 20 Passed

Description

95%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, third-person description that clearly states what the skill does and when to use it, with explicit natural trigger phrases. Minor specificity gap in that the named actions are slightly high-level rather than fully enumerated.

Dimension	Reasoning	Score
Specificity	Names the domain (Gamma across dev/staging/prod) and three concrete actions: 'setting up multi-environment deployments, configuring per-environment secrets, ... implementing environment-specific Gamma configurations'. Sits at anchor 4 (several specific actions, minor gaps) rather than 5 because the actions are somewhat high-level compared to the fully comprehensive anchor example.	4 / 5
Completeness	Explicitly answers both 'what' ('Configure Gamma across development, staging, and production environments') and 'when' ('Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Gamma configurations') with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Provides comprehensive natural trigger phrases a user would actually say: 'gamma environments', 'gamma staging', 'gamma dev prod', 'gamma environment setup', 'gamma config by env', matching the anchor-5 bar of synonyms and variations; no file extensions apply to this config-oriented skill.	5 / 5
Distinctiveness Conflict Risk	Clear narrow niche (Gamma multi-environment setup) with distinct Gamma-specific triggers, minimal overlap risk with other skills; matches anchor 5.	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-multi-env-setup/SKILL.md
Commit: 0540a62

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