instantly-core-workflow-a
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-core-workflow-aExecute 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".
Activation
17%This description fails to communicate what the skill actually does. It relies entirely on placeholder-like language ('Core Workflow A', 'primary use case') without any concrete actions, specific technologies, or realistic trigger terms. The structure attempts completeness but the content is too vague to be useful for skill selection.
Suggestions
Replace abstract terms like 'Core Workflow A' and 'primary use case' with specific concrete actions (e.g., 'Create automated workflows, sync data between apps, configure webhook triggers').
Add natural trigger terms users would actually say, such as specific integration names, action types, or file formats (e.g., 'automation', 'Zapier alternative', 'webhook', 'API integration').
Define the specific domain or niche this skill covers to distinguish it from other workflow/integration skills (e.g., 'Instantly.ai email automation' or 'Instantly CRM workflows').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'primary workflow', 'Core Workflow A', 'primary use case', and 'main features' without describing any concrete actions. No specific capabilities are listed. | 1 / 3 |
Completeness | The description attempts to answer both 'what' and 'when' with a 'Use when' clause and 'Trigger with' 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 be used by real users. Terms like 'primary use case' and 'core integration tasks' 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%This skill is a well-structured template but lacks any actual executable content. All code examples are placeholders, the error handling table is generic, and there's no concrete guidance Claude could act upon. The organization and progressive disclosure are good, but the skill fails its primary purpose of teaching Claude how to perform a specific task.
Suggestions
Replace all placeholder code comments (e.g., '// Step 1 implementation') with actual executable TypeScript code showing the Instantly API calls
Populate the error handling table with real Instantly API errors, their actual causes, and specific solutions
Add concrete examples with real input/output data showing what a successful workflow execution looks like
Include validation steps between workflow stages to verify each step completed successfully before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is reasonable but contains placeholder content ('// Step 1 implementation') that adds no value. The prerequisites section explains things Claude likely knows, and some sections like 'Output' are somewhat redundant. | 2 / 3 |
Actionability | The code blocks are entirely placeholder comments with no executable code. The error handling table uses generic 'Error 1', 'Cause', 'Solution' placeholders. There is nothing copy-paste ready or concrete to act upon. | 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 actual step content is missing entirely. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate references to related skills and external documentation, and content is organized logically with a clear navigation path to next steps. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%| 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.