Create a minimal working Instantly.ai example with real API calls. Use when starting a new Instantly integration, testing your setup, or learning basic Instantly API v2 patterns. Trigger with phrases like "instantly hello world", "instantly example", "instantly quick start", "simple instantly code", "test instantly api".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-hello-world/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 strong completeness and distinctiveness. It clearly identifies when to use the skill and provides explicit trigger phrases. The main weakness is that the 'what' could be more specific about the concrete actions performed (e.g., which API endpoints, what the example actually does).
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates a script that authenticates, lists campaigns, and sends a test email via Instantly.ai API v2' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Instantly.ai API v2) and a general action ('Create a minimal working example with real API calls'), but doesn't list multiple specific concrete actions like which endpoints are called, what the example does, or what outputs are produced. | 2 / 3 |
Completeness | Clearly answers both 'what' (create a minimal working Instantly.ai example with real API calls) and 'when' (starting a new integration, testing setup, learning basic API v2 patterns), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'instantly hello world', 'instantly example', 'instantly quick start', 'simple instantly code', 'test instantly api'. These cover common variations well and are natural user language. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (Instantly.ai), a specific API version (v2), and a specific use case (hello world / quick start example). Very unlikely to conflict with other 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 hello-world skill with real executable code and useful error handling guidance. Its main weaknesses are verbosity (detailed formatting code and interface definitions that Claude could infer) and lack of validation checkpoints between workflow steps. The content would benefit from being more concise and adding a quick validation step after the first API call to confirm connectivity before proceeding.
Suggestions
Add an explicit validation checkpoint after Step 1 (e.g., 'If the campaign list returns successfully, your API key and connection are confirmed — proceed to Step 2') to improve workflow clarity.
Trim the TypeScript interface definitions and console.log formatting — Claude can generate these; focus the code examples on the API call patterns and endpoint paths.
Consider moving the full TypeScript example into a referenced file (e.g., `hello-world.ts`) and keeping only the curl quick-test and key patterns inline in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary verbosity — the detailed console.log formatting, percentage calculations, and interface definitions add bulk that Claude could generate on its own. The error handling table and resources section are useful but the overall content could be tightened. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with typed interfaces, concrete API endpoints, and copy-paste ready curl commands. Each step has specific, runnable code with real endpoint paths and query parameters. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (list campaigns → check accounts → get analytics → run all), but there are no validation checkpoints between steps. The workflow doesn't verify that the API key works before proceeding, and there's no error recovery loop — just a static error table at the end. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the inline code is quite lengthy for a SKILL.md overview. The TypeScript examples could be referenced as separate files rather than fully inlined, especially since this is meant to be a 'hello world' entry point that links to 'instantly-core-workflow-a'. | 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 | |
3e83543
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.