clay-core-workflow-a
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-core-workflow-aExecute Clay primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "clay main workflow", "primary task with clay".
Activation
17%This description fails to communicate what the skill actually does, relying entirely on placeholder-like language ('Core Workflow A', 'primary use case') that provides no concrete information. The trigger terms are artificial constructs rather than natural user language, and the description would be indistinguishable from any other generic workflow skill.
Suggestions
Replace 'Core Workflow A' and 'primary use case' with specific, concrete actions (e.g., 'Enrich contact data, find email addresses, build prospect lists').
Add natural trigger terms users would actually say, such as specific task names, file types, or domain-specific vocabulary related to what Clay actually does.
Explain what 'Clay' is and what domain it operates in to establish distinctiveness from other workflow skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'primary workflow', 'primary use case', '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' section, but the 'what' is so vague ('Core Workflow A') that it provides no meaningful information about actual capabilities. | 2 / 3 |
Trigger Term Quality | The trigger phrases 'clay main workflow' and 'primary task with clay' are artificial and unlikely to be naturally spoken by users. Terms like 'primary use case' and 'core integration' 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 could apply to virtually any skill. Only 'Clay' provides any specificity, but without explaining what Clay is or does. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
42%This skill is a well-structured template but lacks any actual content. The organization and progressive disclosure are good, but the complete absence of executable code, real error handling information, and concrete examples makes it unusable. It's essentially a skeleton that needs to be filled in with real implementation details.
Suggestions
Replace all placeholder code comments with actual executable TypeScript code showing the real Clay API calls and data flow
Fill in the error handling table with actual errors Claude might encounter (e.g., authentication failures, rate limits, invalid payloads) and specific solutions
Add a concrete, complete workflow example with real input data and expected output to demonstrate the full process
Include validation steps between workflow stages (e.g., 'Verify initialization succeeded before proceeding to Execute')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is efficient and doesn't over-explain concepts, but the placeholder comments ('// Step 1 implementation') add no value and waste tokens. The content is mostly lean but includes some unnecessary scaffolding. | 2 / 3 |
Actionability | The code blocks contain only placeholder comments with no actual executable code. The error handling table has placeholder values ('Error 1', 'Cause', 'Solution'). Claude cannot execute or learn from any of this content. | 1 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (Initialize → Execute → Finalize), but there are no validation checkpoints between steps and no feedback loops for error recovery. The workflow structure exists but lacks substance. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate references to external resources and related skills (clay-install-auth, clay-core-workflow-b), and content is well-organized without deep nesting. | 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.