Set up Instantly.ai API v2 authentication and project configuration. Use when creating a new Instantly integration, generating API keys, or configuring environment variables for the Instantly outreach platform. Trigger with phrases like "install instantly", "setup instantly", "instantly auth", "configure instantly API key", "instantly credentials".
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-install-auth/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-crafted skill description that clearly identifies its niche (Instantly.ai API v2 setup), provides explicit 'Use when' and 'Trigger with' clauses, and includes natural user-facing keywords. The only minor weakness is that the specificity of capabilities could be slightly more detailed about what concrete setup steps are performed beyond authentication and environment variable configuration.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai API v2) and some actions (authentication, project configuration, generating API keys, configuring environment variables), but the actions are somewhat narrow and not comprehensively listed — it's mostly about setup/config rather than listing multiple distinct concrete operations. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up Instantly.ai API v2 authentication and project configuration) and 'when' (explicit 'Use when' clause with specific scenarios, plus a 'Trigger with phrases' section listing exact trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'install instantly', 'setup instantly', 'instantly auth', 'configure instantly API key', 'instantly credentials', plus mentions of 'environment variables', 'API keys', and 'Instantly outreach platform'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (Instantly.ai), a specific API version (v2), and a specific task (authentication/setup). Very unlikely to conflict with other skills due to the narrow, well-defined niche. | 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 for both TypeScript and Python. Its main weakness is that it's somewhat bloated by including both language implementations inline and extensive reference tables, which could be better organized through progressive disclosure. The workflow is clear but lacks explicit validation gates between steps.
Suggestions
Split TypeScript and Python client implementations into separate referenced files (e.g., `TYPESCRIPT_CLIENT.md` and `PYTHON_CLIENT.md`) to reduce the main skill's token footprint.
Add an explicit validation checkpoint after Step 1 (e.g., 'Confirm your .env file is populated correctly before proceeding') and frame Step 4 as a required gate: 'Only proceed to next steps when verification passes.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides both TypeScript and Python client wrappers, which adds bulk. The scopes table and error handling table are useful but the content could be tightened — providing both language implementations inline makes it lengthy. Some minor verbosity in prerequisites (mentioning pricing) and the overview is reasonable but not maximally lean. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready — the .env setup script, TypeScript client, Python client, and verification script are all concrete and complete with proper imports, error handling, and type annotations. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (generate key → create client → verify), but there's no explicit validation checkpoint between creating the .env file and using it, and no feedback loop if the verification step fails beyond a generic error table. The verify step exists but isn't framed as a gate before proceeding. | 2 / 3 |
Progressive Disclosure | The content is mostly monolithic — both TypeScript and Python implementations are inline when one could be in a separate file. The scopes table and error table add significant length. References to external resources and next steps are present but the main content could benefit from splitting language-specific implementations into separate files. | 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 | |
a04d1a2
Table of Contents
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.