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".
Overall
score
34%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-core-workflow-bActivation
17%This description fails to communicate any concrete functionality, using placeholder-like language ('Core Workflow B', 'secondary use case') that provides no actionable information. The trigger phrases are artificial constructs rather than natural user language, and the description lacks any domain specificity that would help Claude distinguish this skill from others.
Suggestions
Replace abstract terms like 'Core Workflow B' and 'secondary use case' with specific, concrete actions the skill performs (e.g., 'Syncs customer data to CRM', 'Generates backup reports').
Rewrite trigger phrases to match natural user language - what would someone actually say when they need this skill? (e.g., 'sync my contacts', 'create a backup').
Specify the domain or tool this skill applies to (e.g., 'Instantly CRM', 'Instantly email automation') to create clear distinctiveness from other skills.
| 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 or capabilities. No specific operations are mentioned. | 1 / 3 |
Completeness | The description attempts to answer both 'what' and 'when' with explicit trigger guidance, but the 'what' is so vague ('Core Workflow B', 'secondary use case') that it provides no meaningful information about actual capabilities. | 2 / 3 |
Trigger Term Quality | The trigger phrases 'instantly secondary workflow' and 'secondary task with instantly' are unnatural and unlikely to be used by real users. These are technical jargon rather than natural language users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | Terms like 'secondary workflow', 'secondary use case', and 'complementing primary workflow' are extremely generic and could apply to countless skills. There's no clear niche or domain specified. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
22%This skill is essentially a template with no actual content - all code blocks are empty placeholders, the error handling section is mislabeled (contains a comparison table instead), and there's no actionable guidance. While the structure and organization are reasonable, the complete absence of executable code or concrete instructions makes this skill unusable in its current form.
Suggestions
Replace all placeholder comments with actual executable TypeScript code that demonstrates the workflow steps
Add real error handling content with specific error types, causes, and recovery steps - move or remove the comparison table
Include concrete examples with actual API calls, expected inputs, and outputs rather than empty code blocks
Add validation checkpoints between steps (e.g., 'Verify step 1 succeeded before proceeding') with specific checks to perform
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured without excessive explanation, but includes placeholder comments instead of actual code, which wastes tokens without providing value. The comparison table in 'Error Handling' section is misplaced and doesn't actually cover error handling. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code. Claude cannot follow these instructions as there is nothing concrete to execute or learn from. | 1 / 3 |
Workflow Clarity | While steps are numbered, they contain no actual content - just empty placeholder comments. There are no validation checkpoints, no feedback loops for error recovery, and the 'Error Handling' section is actually a comparison table that doesn't address errors at all. | 1 / 3 |
Progressive Disclosure | The structure with sections and references to other skills (instantly-install-auth, instantly-core-workflow-a, instantly-common-errors) is reasonable, but the main content is so empty that the structure serves little purpose. External links are provided appropriately. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
75%Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 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.