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
—
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. Its 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 artifacts would strengthen it. The use of second person 'your' is a minor voice issue.
Suggestions
Add more concrete actions such as 'generate GitHub Actions workflow YAML, configure test matrix, set up test result artifacts' to improve specificity.
Replace second person 'your build process' with third person phrasing like 'the build process' to maintain consistent voice.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD integration with GitHub Actions) and some actions (configure, 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 caching'. | 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. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'gamma CI', 'gamma GitHub Actions', 'gamma automated tests', 'CI gamma', 'gamma pipeline'. These cover common variations a user would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining Gamma framework with CI/CD and GitHub Actions. The 'gamma' qualifier on all trigger terms makes it very unlikely to conflict with generic CI/CD skills or other testing framework 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 for Gamma integration. Its main weaknesses are the lack of validation checkpoints (e.g., verifying the workflow runs, checking test output) and the monolithic structure that puts all detailed configuration inline rather than splitting into referenced files. Minor verbosity issues exist but don't significantly detract from utility.
Suggestions
Add a validation step after Step 6, e.g., 'Run `gh workflow run gamma-ci.yml` and verify with `gh run list` to confirm the pipeline executes successfully. If tests fail, check `gh run view <run-id> --log` for errors.'
Consider splitting the mock client setup and test examples into referenced files (e.g., 'See GAMMA_MOCKING.md for advanced mock patterns') to reduce the inline content length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary elements like the comments explaining millisecond values (# 60000: 1 minute in ms), the Resources section linking to docs Claude already knows, and the Prerequisites section stating obvious requirements. The mock client implementation is thorough but could be trimmed. | 2 / 3 |
Actionability | Fully executable, copy-paste ready code across all steps: complete GitHub Actions YAML, package.json scripts, Vitest config, test setup with mocking, integration test examples, and GitHub CLI commands for secrets. Every step has concrete, runnable code. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-6) and logically ordered from CI config through test setup to secrets. However, there are no validation checkpoints — no step to verify the workflow runs correctly, no feedback loop for debugging failed CI runs, and no explicit 'verify your setup works' step after adding secrets. | 2 / 3 |
Progressive Disclosure | The content is somewhat monolithic — all configuration, test setup, mocking, and examples are inline in a single file. The mock client, test configuration, and CI workflow could be referenced as separate files. The 'Next Steps' reference to gamma-deploy-integration is good but the main content would benefit from better splitting. | 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
3a2d27d
- 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.