instantly-deploy-integration
Deploy Instantly.ai webhook receivers and API integrations to cloud platforms. Use when deploying to Vercel, Cloud Run, or Fly.io, or setting up production webhook endpoints. Trigger with phrases like "deploy instantly", "instantly cloud run", "instantly vercel", "instantly webhook deployment", "instantly production deploy".
64
77%
Does it follow best practices?
Impact
—
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-deploy-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 skill description that clearly defines its niche at the intersection of Instantly.ai integrations and cloud deployment. It excels at completeness with explicit 'Use when' and 'Trigger with' clauses, and has strong distinctiveness. The main weakness is that the specific capabilities could be more detailed beyond just 'deploy' and 'setting up endpoints'.
Suggestions
Add more specific concrete actions such as 'configure webhook routes, set environment variables, manage API secrets, set up health checks' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai webhook receivers and API integrations) and the action (deploy to cloud platforms), but doesn't list multiple concrete actions beyond 'deploy' and 'setting up production webhook endpoints'. It could be more specific about what the deployment entails (e.g., configuring environment variables, setting up routes, managing secrets). | 2 / 3 |
Completeness | Clearly answers both 'what' (deploy Instantly.ai webhook receivers and API integrations to cloud platforms) and 'when' (explicit 'Use when' clause with deployment scenarios and a 'Trigger with phrases' section listing specific trigger terms). | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms: 'deploy instantly', 'instantly cloud run', 'instantly vercel', 'instantly webhook deployment', 'instantly production deploy', plus platform names like Vercel, Cloud Run, Fly.io. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of Instantly.ai with cloud deployment platforms (Vercel, Cloud Run, Fly.io). The 'instantly' prefix on trigger terms creates a clear niche that is unlikely to conflict with generic deployment or generic webhook 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, highly actionable deployment skill with complete, executable code for three cloud platforms. Its main weaknesses are the somewhat confusing step numbering (options vs. sequential steps), the length of the single file which could benefit from splitting deployment options into separate references, and minor verbosity in repeated patterns across options. The post-deploy verification is a strength, though it lacks explicit error recovery loops.
Suggestions
Restructure the workflow numbering: use 'Step 1: Choose and deploy to a platform (Option A/B/C)' → 'Step 2: Register webhook' → 'Step 3: Verify' to make the sequence unambiguous.
Add explicit failure recovery guidance: 'If health check fails, check logs with `fly logs` / `gcloud logs read` and verify env vars are set correctly before re-deploying.'
Consider splitting each deployment option into separate referenced files (e.g., deploy-vercel.md, deploy-cloud-run.md, deploy-fly.md) to reduce SKILL.md length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy across the three deployment options (repeated webhook secret validation, similar patterns). The error handling table and resources section are lean, but the overall length could be tightened—e.g., the three options share boilerplate that could be factored out. Some explanatory comments in code are helpful but borderline unnecessary for Claude. | 2 / 3 |
Actionability | Excellent actionability—every deployment option includes complete, executable code (TypeScript handlers, Dockerfiles, deployment commands, fly.toml config). The post-deploy verification includes copy-paste-ready curl commands. Code is concrete and production-ready, not pseudocode. | 3 / 3 |
Workflow Clarity | The workflow has a structural issue: Options A/B/C are labeled as alternatives but aren't numbered as steps, then 'Step 2' and 'Step 3' follow as sequential steps after any option. This is somewhat confusing. Post-deploy verification (Step 3) provides validation, but there's no explicit feedback loop for handling failures during deployment itself—no 'if deploy fails, check X' guidance. The verification step is good but could include expected outputs. | 2 / 3 |
Progressive Disclosure | The skill references other skills (`instantly-install-auth`, `instantly-local-dev-loop`, `instantly-webhooks-events`) and external docs, which is good. However, with no bundle files, all content is inline in one large file. The three deployment options could arguably be split into separate files with the SKILL.md serving as an overview, which would better serve progressive disclosure for a skill this long. | 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
a04d1a2
- 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.