instantly-core-workflow-b
Execute Instantly secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "instantly secondary workflow", "secondary task with instantly".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-core-workflow-b49
Quality
23%
Does it follow best practices?
Impact
97%
1.22xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-core-workflow-b/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 follows a good structural template with 'Use when' and 'Trigger with' clauses, but fails to provide any meaningful content. It reads like a placeholder or template that was never filled in with actual capabilities, using abstract terms like 'Core Workflow B' and 'secondary use case' that convey no information about what the skill actually does.
Suggestions
Replace placeholder terms like 'Core Workflow B' and 'secondary use case' with specific, concrete actions the skill performs (e.g., 'Generate reports', 'Process batch files', 'Send notifications').
Add natural trigger terms users would actually say - identify the real domain this skill operates in and include relevant keywords, file types, or task names.
Define what makes this skill distinct from others - what specific problem does it solve that other skills don't?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'secondary workflow', 'Core Workflow B', and 'secondary use case' without describing any concrete actions. There are no specific capabilities listed - just placeholder terminology. | 1 / 3 |
Completeness | The description attempts to answer both 'what' and 'when' with explicit trigger guidance, but the content is so vague that neither is meaningfully answered. It has the structure of completeness but lacks substance. | 2 / 3 |
Trigger Term Quality | The trigger phrases 'instantly secondary workflow' and 'secondary task with instantly' are not natural language users would say. These are technical jargon that don't reflect real user intent or common vocabulary. | 1 / 3 |
Distinctiveness Conflict Risk | Terms like 'secondary workflow', 'secondary use case', and 'complementing primary workflow' are extremely generic and could apply to virtually any supporting skill, creating high conflict risk with other skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a well-structured template but lacks any actual content. All code blocks are empty placeholders, making it completely non-actionable. The organization and progressive disclosure are good, but the skill provides zero executable guidance for Claude to follow.
Suggestions
Replace all placeholder comments (e.g., '// Step 1 implementation') with actual executable TypeScript code that demonstrates the workflow
Add concrete examples showing real API calls, expected inputs, and outputs from the Instantly API
Include validation checkpoints between steps (e.g., 'Verify response status before proceeding to Step 2')
Add specific error handling code in the Error Recovery section instead of placeholder comments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is reasonably lean but contains placeholder comments instead of actual code, and some sections like the comparison table add little value for a workflow skill. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code, commands, or concrete guidance. This is entirely non-actionable. | 1 / 3 |
Workflow Clarity | While steps are numbered, they contain no actual instructions or validation checkpoints. The workflow is a skeleton with no substance - Claude cannot execute 'Step 1 implementation' as a comment. | 1 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate references to related skills (instantly-install-auth, instantly-core-workflow-a, instantly-common-errors), and external documentation links. Navigation is clear and one-level deep. | 3 / 3 |
Total | 7 / 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.