instantly-core-workflow-a
Execute Instantly primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "instantly main workflow", "primary task with instantly".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-core-workflow-a53
Quality
29%
Does it follow best practices?
Impact
100%
1.72xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-core-workflow-a/SKILL.mdDiscovery
17%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 description fails to communicate any concrete functionality. It relies entirely on placeholder-like language ('Core Workflow A', 'primary use case') without specifying what the skill actually does or what domain it operates in. The trigger phrases are artificial constructs rather than natural user language.
Suggestions
Replace abstract terms like 'Core Workflow A' and 'primary use case' with specific actions (e.g., 'Create automation workflows', 'Connect apps via webhooks', 'Set up data sync between services')
Add natural trigger terms users would actually say, such as specific app names, automation types, or integration scenarios (e.g., 'Zapier alternative', 'webhook automation', 'connect Slack to Google Sheets')
Specify the domain or platform this skill applies to - 'Instantly' appears to be a product name but needs context about what it does
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'primary workflow', 'Core Workflow A', 'main features', and 'core integration tasks' without specifying any concrete actions. No actual capabilities are described. | 1 / 3 |
Completeness | The description attempts to answer both 'what' and 'when' with a 'Use when' clause and 'Trigger with phrases' section, but the content is so vague that neither is meaningfully answered. The structure is present but substance is lacking. | 2 / 3 |
Trigger Term Quality | The trigger phrases 'instantly main workflow' and 'primary task with instantly' are unnatural and unlikely to match how users would actually phrase requests. Terms like 'primary use case' and 'main features' are generic jargon, not natural keywords. | 1 / 3 |
Distinctiveness Conflict Risk | Terms like 'primary workflow', 'main features', and 'core integration tasks' are extremely generic and would conflict with virtually any skill. Nothing distinguishes this from other skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a template with placeholder content rather than actionable guidance. While the structure and progressive disclosure are well-organized, the complete absence of actual code, concrete examples, or real error handling makes it unusable. The skill needs to be populated with real implementation details to provide any value.
Suggestions
Replace all placeholder code comments (e.g., '// Step 1 implementation') with actual executable TypeScript code that demonstrates the Instantly API workflow
Fill in the error handling table with real errors, causes, and solutions specific to the Instantly API
Add a concrete, complete workflow example that can be copied and executed, showing actual API calls and expected responses
Add validation checkpoints between steps (e.g., 'Verify initialization succeeded before proceeding to Execute')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is reasonable but contains placeholder content and some unnecessary sections like 'Prerequisites' that explain things Claude would know. The template-like nature adds tokens without value. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code. The error handling table has placeholder values. Nothing is copy-paste ready or concrete. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Initialize, Execute, Finalize), but there are no validation checkpoints, no feedback loops for error recovery, and the steps themselves are empty placeholders without actual guidance. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, references to related skills (instantly-install-auth, instantly-core-workflow-b), and external documentation links. Navigation is straightforward and one level deep. | 3 / 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 | |
- 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.