gamma-ci-integration

Configure Gamma CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Gamma tests into your build process. Trigger with phrases like "gamma CI", "gamma GitHub Actions", "gamma automated tests", "CI gamma", "gamma pipeline".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 content is concise and action-oriented with substantial executable code, but small execution gaps (missing `vi` import, an invalid comment line) and the absence of validation checkpoints and external reference files hold it back from the top tier.

Suggestions

Make the setup file fully runnable: import `vi` from 'vitest' and replace the invalid `# 30000:` comment with a `//` comment so the TypeScript compiles.

Add explicit validation checkpoints to the workflow (e.g., after Step 6 verify the secret with `gh secret list` and confirm the workflow runs) to create feedback loops for error recovery.

Move the large inline config blocks (the workflow YAML, vitest config, setup file) into reference files under references/ and link to them from the overview to enable proper progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean, mostly executable code with minimal prose, and assumes Claude's competence without explaining concepts like what Vitest or GitHub Actions are. It is not a 2 because there is no padding or explanatory fluff of known concepts, though a couple of redundant inline comments are minor blemishes.	3 / 3
Actionability	Concrete YAML, package.json, vitest config, and gh CLI commands are provided, but the code is not fully copy-paste runnable: the setup file uses `vi.fn()` without importing `vi`, and a `# 30000:` line is invalid TypeScript. It is not a 3 because these missing/erroneous details prevent fully executable code; not a 1 because real executable code and commands dominate over pseudocode.	2 / 3
Workflow Clarity	Six clearly sequenced steps are labeled, but there are no explicit validation checkpoints or feedback loops within the step sequence (e.g., verifying the secret or that the config loads). It is not a 1 because the sequence is clearly laid out; not a 3 because the rubric caps at 2 when validation checkpoints are missing and none are embedded in the workflow.	2 / 3
Progressive Disclosure	Sections are well-organized, but no bundle/reference files exist and all detailed configs are inline in a ~180-line file that could be split out. It is not a 1 because organization is clean, not a monolithic wall; not a 3 because there are no one-level-deep referenced files and content is not appropriately split.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 strong: it states concrete actions, gives explicit "Use when" triggers with natural phrasings, and targets a distinct niche. It uses imperative third-person voice with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Multiple concrete actions are named — "Configure Gamma CI/CD integration with GitHub Actions and testing", "setting up automated testing, configuring CI pipelines", "integrating Gamma tests into your build process" — matching the anchor for listing several specific actions. It is not a 2 because it goes beyond naming a domain to enumerating distinct actions.	3 / 3
Completeness	It answers both what ("Configure Gamma CI/CD integration with GitHub Actions and testing") and when ("Use when setting up automated testing, configuring CI pipelines, or integrating Gamma tests into your build process") with explicit triggers. It is not a 2 because the "when" is explicit, not merely implied.	3 / 3
Trigger Term Quality	Explicit triggers like "gamma CI", "gamma GitHub Actions", "gamma automated tests", "CI gamma", and "gamma pipeline" give good natural-term coverage a user would plausibly say. It is not a 2 because it lists multiple common phrasings rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	It targets a specific Gamma niche with distinct Gamma-prefixed triggers, making overlap with other skills unlikely. It is not a 2 because the domain and triggers are specific rather than broadly overlapping.	3 / 3
	Total	12 / 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.