instantly-core-workflow-b
Manage Instantly.ai email account warmup, analytics, and deliverability. Use when enabling warmup, monitoring sender reputation, pulling analytics, or troubleshooting deliverability issues. Trigger with phrases like "instantly warmup", "instantly analytics", "email warmup instantly", "instantly deliverability", "instantly account health".
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-core-workflow-b/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 identifies its niche (Instantly.ai email warmup and deliverability), provides explicit trigger guidance, and is highly distinctive due to the product-specific focus. The main area for improvement is adding more specific concrete actions beyond the somewhat general verbs like 'manage', 'monitor', and 'troubleshoot'.
Suggestions
Enhance specificity by listing more concrete actions, e.g., 'enable/disable warmup schedules, view warmup progress charts, check spam rate metrics, configure daily send limits'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai email warmup/deliverability) and some actions (enabling warmup, monitoring reputation, pulling analytics, troubleshooting deliverability), but the actions are somewhat general and not deeply specific (e.g., doesn't mention specific API calls, configuration steps, or concrete outputs). | 2 / 3 |
Completeness | Clearly answers both 'what' (manage Instantly.ai email account warmup, analytics, and deliverability) and 'when' (explicit 'Use when...' clause with specific scenarios plus a 'Trigger with phrases like...' section). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'instantly warmup', 'instantly analytics', 'email warmup instantly', 'instantly deliverability', 'instantly account health' — these are terms users would naturally say when needing this skill, with good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (Instantly.ai) with specific features (warmup, deliverability, sender reputation). The branded trigger terms make it 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 skill with executable TypeScript code covering the full warmup and analytics lifecycle. Its main weaknesses are the length (could be more concise by trimming type annotations and console formatting) and the lack of explicit validation checkpoints between workflow steps — particularly important since warmup misconfiguration can damage sender reputation. The error handling table is helpful but should be woven into the workflow as decision points.
Suggestions
Add explicit validation gates between steps, e.g., 'After Step 1, verify warmup is active by calling checkWarmupHealth before configuring settings in Step 2' and 'Only launch campaigns when inbox rate exceeds 90%'.
Trim the overview paragraph explaining what warmup is — Claude can infer this from context. Remove or shorten console.log formatting code that doesn't add instructional value.
Consider extracting the three campaign analytics sub-functions (aggregate, daily, step-level) into a referenced file to reduce the main skill's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity — the overview paragraph explaining what warmup is (Claude knows this given context), console.log formatting details, and the extensive TypeScript type annotations for every response add bulk. The API endpoint table and error table are useful but the code blocks could be tighter. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with concrete API paths, request bodies, typed responses, and real configuration values. Each step has copy-paste-ready functions with specific parameters and realistic defaults. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from enabling warmup through monitoring and analytics. However, there are no explicit validation checkpoints or feedback loops — e.g., after enabling warmup there's no 'verify warmup is active before proceeding to Step 2' gate, and no guidance on what to do if warmup health scores are poor before launching campaigns. The error table partially compensates but doesn't integrate into the workflow steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a reference table, but it's quite long (~180 lines of code) with all detail inline. The campaign analytics section (Step 4) with three sub-functions could be split to a separate reference file. References to external docs and next-step skill are good, but no bundle files exist to offload detail. | 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
d41e58e
- 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.