clay-core-workflow-b
Execute Clay secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "clay secondary workflow", "secondary task with clay".
Overall
score
40%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-core-workflow-bActivation
7%This description fails to communicate what the skill actually does, using placeholder-like language ('Core Workflow B', 'secondary use case') that provides no meaningful information. The trigger terms are artificial constructs rather than natural user language, and the circular 'when' clause offers no real guidance for skill selection.
Suggestions
Replace 'Core Workflow B' and 'secondary use case' with specific, concrete actions the skill performs (e.g., 'Enriches contact data with company information, validates email addresses, appends LinkedIn profiles').
Add natural trigger terms users would actually say, such as specific task names, data types, or outcomes (e.g., 'data enrichment', 'contact lookup', 'lead scoring').
Rewrite the 'Use when' clause to describe actual scenarios or user needs rather than self-referential terms (e.g., 'Use when enriching CRM data, validating leads, or appending company details to contact lists').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'Core Workflow B', 'secondary use case', and 'complementing primary workflow' without describing any concrete actions or capabilities. | 1 / 3 |
Completeness | The 'what' is essentially undefined (just 'Core Workflow B' with no explanation), and the 'when' is circular and meaningless ('when implementing secondary use case'). Neither question is meaningfully answered. | 1 / 3 |
Trigger Term Quality | The trigger phrases 'clay secondary workflow' and 'secondary task with clay' are artificial and unlikely to be naturally spoken by users. No natural keywords describing actual tasks are included. | 1 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Clay' and 'secondary workflow' provides some distinctiveness from other skills, but the vague nature means it could still conflict with any Clay-related skill or generic workflow skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
42%This skill has good structural organization and appropriate cross-references, but critically fails on actionability - every code block is a placeholder with no actual implementation. The 'Error Handling' section is mislabeled (contains a comparison table, not error handling), and the workflow lacks validation checkpoints needed for API operations.
Suggestions
Replace all placeholder code comments with actual executable TypeScript code showing real Clay API calls and data handling
Add actual error handling code in the Error Handling section, including try/catch blocks and specific error recovery patterns
Include validation checkpoints after each step (e.g., 'Verify API response status before proceeding to Step 2')
Add concrete input/output examples showing what data flows through each step
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes placeholder comments instead of actual code, and the comparison table in 'Error Handling' section doesn't actually explain error handling - it's misplaced content that wastes tokens. | 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's nothing concrete to execute. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Setup → Process → Complete), but there are no validation checkpoints, no feedback loops for error recovery, and the 'Error Handling' section contains a comparison table instead of actual error handling guidance. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate references to related skills (clay-install-auth, clay-core-workflow-a, clay-common-errors), and external documentation links. Content is well-organized for a skill of this size. | 3 / 3 |
Total | 8 / 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.