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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-ci-integration/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Gamma CI/CD with GitHub Actions), provides explicit trigger guidance, and answers both what and when. The main weakness is that the specific capabilities could be more granular—listing concrete actions like creating workflow YAML files, configuring test matrix, or setting up test reporting would strengthen it. The use of second person 'your' is a minor voice issue but the description is otherwise well-structured.
Suggestions
Add more specific concrete actions such as 'generate GitHub Actions workflow YAML, configure test matrix, set up test reporting, manage secrets for CI' to improve specificity.
Replace second person 'your build process' with third person phrasing like 'the build process' to match the preferred voice guidelines.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma CI/CD with GitHub Actions) and some actions (configure integration, set up automated testing, integrate tests into build process), but doesn't list multiple concrete specific actions like 'create workflow files, configure test runners, set up deployment triggers'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Gamma CI/CD integration with GitHub Actions and testing) and 'when' (setting up automated testing, configuring CI pipelines, integrating Gamma tests into build process), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'gamma CI', 'gamma GitHub Actions', 'gamma automated tests', 'CI gamma', 'gamma pipeline'. Also includes broader terms like 'automated testing', 'CI pipelines', and 'build process' that users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Gamma' with CI/CD and GitHub Actions creates a clear niche. The specific trigger phrases all include 'gamma' which makes it unlikely to conflict with generic CI/CD skills or other tool-specific CI skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with complete, executable code examples covering the full CI setup pipeline. Its main weaknesses are the lack of validation checkpoints within the workflow (e.g., verifying the pipeline runs successfully before proceeding) and some verbosity that could be trimmed. The content would benefit from inline verification steps and slightly tighter prose.
Suggestions
Add validation checkpoints between steps, e.g., 'Run `npm run test:gamma` locally to verify mock mode works before pushing the workflow' after Step 4.
Remove the comments explaining millisecond values and the Resources section with generic documentation links Claude already knows.
Consider splitting the mock client setup and test examples into referenced files (e.g., 'See GAMMA_MOCKS.md for mock client patterns') to reduce the main skill's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary elements like comments explaining obvious things (e.g., '# 60000: 1 minute in ms'), the Resources section with generic links Claude already knows, and the Prerequisites section stating obvious requirements. The Output section is somewhat redundant given the workflow already shows what it produces. | 2 / 3 |
Actionability | Fully executable code throughout — complete GitHub Actions YAML, package.json scripts, Vitest config, test setup with mocking, integration test examples, and CLI commands for setting secrets. All code is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-6) and logically ordered, but there are no validation checkpoints or feedback loops. After creating the workflow, there's no step to verify it works, no 'run locally first' validation, and no error recovery guidance within the workflow itself. The error handling table is separate and reactive rather than integrated into the steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's quite long (~150 lines of content) and could benefit from splitting detailed mock setup or test examples into separate files. The reference to 'gamma-deploy-integration' in Next Steps is good, but the main content is monolithic with all configuration inline. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
c8a915c
- Reviewed
Table of Contents
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.