clay-core-workflow-a

Execute 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".

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-core-workflow-a

What are skills?

1.19x

Quality

29%

Does it follow best practices?

Impact

99%

1.19x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/clay-pack/skills/clay-core-workflow-a/SKILL.md

SKILL.md

Review

Evals

Discovery

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 fails to communicate what the skill actually does. It relies entirely on placeholder-like language ('Core Workflow A', 'primary use case', 'main features') without specifying concrete actions or capabilities. The trigger phrases are artificial constructs rather than natural user language, making skill selection unreliable.

Suggestions

Replace vague terms like 'Core Workflow A' and 'primary use case' with specific concrete actions (e.g., 'Enriches lead data, builds prospect lists, automates outreach sequences')

Add natural trigger terms users would actually say, such as specific Clay features, data types, or task names (e.g., 'lead enrichment', 'prospect research', 'Clay table')

Define the distinct niche by specifying what makes this workflow different from other Clay workflows or integrations

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 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 '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. Nothing distinguishes this from other Clay-related or general workflow skills.	1 / 3
	Total	5 / 12 Passed

Implementation

42%

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. While the organization and progressive disclosure are good, the complete absence of executable code, real examples, or concrete guidance makes it unusable. It reads as a skeleton waiting to be filled in rather than a functional skill.

Suggestions

Replace all placeholder code blocks with actual executable TypeScript code showing real Clay API usage

Fill in the error handling table with real errors, causes, and solutions specific to Clay workflows

Add a concrete 'Complete Workflow' example with real API calls and expected responses

Include validation steps between Initialize/Execute/Finalize to verify each step succeeded before proceeding

Dimension	Reasoning	Score
Conciseness	The structure is efficient and doesn't over-explain concepts, but the content is entirely placeholder (empty code blocks with comments like '// Step 1 implementation') which adds no value while consuming tokens.	2 / 3
Actionability	All code blocks contain only placeholder comments with no actual executable code. The error handling table has placeholder values ('Error 1', 'Cause', 'Solution'). There is zero concrete, copy-paste ready guidance.	1 / 3
Workflow Clarity	Steps are clearly 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 external resources and related skills (clay-install-auth, clay-core-workflow-b), and content is well-organized with logical navigation.	3 / 3
	Total	8 / 12 Passed

Validation

81%

Warnings & errors only

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: 2 days ago

Table of Contents

Discovery Implementation Validation

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.