instantly-ci-integration
Configure CI/CD pipelines for Instantly.ai integrations with GitHub Actions. Use when setting up automated testing, deployment pipelines, or continuous validation of Instantly API integrations. Trigger with phrases like "instantly ci", "instantly github actions", "instantly pipeline", "instantly automated testing", "instantly ci/cd".
77
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-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 well-structured description with clear 'what' and 'when' clauses and explicit trigger phrases. Its main weakness is that the specific capabilities could be more concrete—listing particular actions like creating workflow YAML files, configuring API key secrets, or setting up test suites would strengthen it. The distinctiveness is excellent due to the narrow Instantly.ai + GitHub Actions niche.
Suggestions
Add more concrete actions beyond 'configure pipelines', such as 'create GitHub Actions workflow files, set up API key secrets, configure test suites for Instantly endpoints, define deployment stages'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD pipelines for Instantly.ai with GitHub Actions) and some actions (automated testing, deployment pipelines, continuous validation), but doesn't list multiple concrete specific actions like 'create workflow files, configure test runners, set up deployment stages'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure CI/CD pipelines for Instantly.ai integrations with GitHub Actions) and 'when' (setting up automated testing, deployment pipelines, or continuous validation) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'instantly ci', 'instantly github actions', 'instantly pipeline', 'instantly automated testing', 'instantly ci/cd'. These cover good variations of how users might request this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Instantly.ai + CI/CD + GitHub Actions. The trigger terms all include 'instantly' prefix, making it highly unlikely to conflict with generic CI/CD or other API integration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, copy-paste ready CI/CD configuration for Instantly.ai integrations with good coverage of testing, deployment, and security. However, it suffers from being a monolithic document that inlines ~200 lines of code that should be split into referenced files, and it lacks explicit error recovery/feedback loops in the deployment workflow. The content is solid but poorly structured for token efficiency and progressive disclosure.
Suggestions
Split the integration test suite, deployment workflow, and pre-commit hook into separate referenced files (e.g., INTEGRATION-TESTS.md, DEPLOY.md) and keep SKILL.md as a concise overview with just the core CI workflow.
Add explicit validation/rollback guidance in the deployment step — e.g., what to do if the health check fails, how to roll back to a previous revision.
Trim the integration test suite to 1-2 representative examples rather than showing all 5 test cases inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with complete workflow files, test suites, and deployment configs. While the code examples are useful, the integration test suite and deployment workflow add significant length that could be referenced in separate files. Some sections (like the full test suite with 5 test cases) could be trimmed to representative examples. | 2 / 3 |
Actionability | Fully executable, copy-paste ready YAML workflows, TypeScript test files, and bash scripts. Every step includes concrete, runnable code with specific tool versions, environment variables, and commands. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (test → integration-test → deploy) with job dependencies, and the deployment includes a health check verification step. However, there are no explicit validation/feedback loops for error recovery in the multi-step deployment process — if the deploy verification fails, there's no rollback or retry guidance. The pre-commit hook catches secrets but the overall pipeline lacks checkpoint-based error recovery. | 2 / 3 |
Progressive Disclosure | All content is inline in a single monolithic file — full workflow YAML, complete test suites, deployment configs, and pre-commit hooks. This would benefit greatly from splitting the test suite, deployment workflow, and validation scripts into referenced files, keeping SKILL.md as an overview with the core CI workflow. | 1 / 3 |
Total | 8 / 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.