instantly-ci-integration
Configure Instantly CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Instantly tests into your build process. Trigger with phrases like "instantly CI", "instantly GitHub Actions", "instantly automated tests", "CI instantly".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-ci-integration90
Quality
88%
Does it follow best practices?
Impact
95%
1.75xAverage score across 3 eval scenarios
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 well-structured skill description with explicit trigger guidance and clear 'Use when' clause. The main weakness is the somewhat generic action verbs (configure, setting up, integrating) rather than listing specific concrete capabilities like creating workflow YAML files or configuring test runners.
Suggestions
Add more specific concrete actions such as 'create GitHub Actions workflow files', 'configure test runners', or 'set up test reporting' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD integration with GitHub Actions) and some actions (configure, setting up, integrating), but lacks specific concrete actions like 'create workflow files', 'add test steps', or 'configure triggers'. | 2 / 3 |
Completeness | Clearly answers both what (configure Instantly CI/CD integration with GitHub Actions and testing) and when (setting up automated testing, configuring CI pipelines, integrating tests) with explicit 'Use when' clause and trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'instantly CI', 'instantly GitHub Actions', 'instantly automated tests', 'CI instantly'. Also includes terms like 'automated testing', 'CI pipelines', and 'build process'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to 'Instantly' tool integration with CI/CD. The combination of 'Instantly' product name with CI/CD context creates a clear niche unlikely to conflict with generic CI or testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent conciseness and fully executable code examples. The main weakness is the lack of explicit validation steps between workflow creation and branch protection configuration—users should verify their pipeline works before enforcing it as a required check.
Suggestions
Add a validation step after Step 3: 'Run `gh workflow run instantly-integration.yml` and verify success before enabling branch protection'
Include a troubleshooting step for verifying secrets are correctly configured: 'Run `gh secret list` to confirm INSTANTLY_API_KEY exists'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary configuration and code without explaining what GitHub Actions or CI/CD is. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable YAML workflows, bash commands, and TypeScript test code that are copy-paste ready. Includes specific file paths and complete configurations. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints between steps. No feedback loop for verifying the workflow works before proceeding (e.g., 'run workflow manually to verify before enabling branch protection'). | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate inline examples, and single-level references to external resources and related skills. Content is appropriately scoped for a SKILL.md file. | 3 / 3 |
Total | 11 / 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 | |
- 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.