Name: clay
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

clay

Clay integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clay data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/clay/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and well-structured, leading Claude through a clear connect-discover-act workflow with strong validation feedback loops. Minor verbosity and a couple of dense reference sections keep it just short of the top anchor.

Suggestions

Trim motivational asides like 'so you can focus on the integration logic rather than auth plumbing' and condense the agent-types enumeration.

Move the proxy flag reference table and clientAction field breakdown into a short reference section or separate file to keep the main flow lean.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and tight tables, though a few explanatory asides ('so you can focus on the integration logic rather than auth plumbing', agent-types list) could be trimmed.	4 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands for installation, auth, connection, action discovery, running, and proxying, with only minor gaps such as placeholder values.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based polling and explicit feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though some edge-case recovery steps are lightly sketched.	4 / 5
Progressive Disclosure	Single-file skill with well-organized sections and clear navigation; no bundle files to split out, so the structure is appropriate, though a few dense reference blocks could live in separate files.	4 / 5
	Total	16 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, third-person, and covers both what the skill does and when to use it, with Clay-specific framing that limits conflict risk. It could be strengthened by replacing generic actions ('manage data, records') with concrete Clay operations and richer trigger phrases.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Clay actions such as 'search contacts, enrich people and companies, and trigger workflows'.

Expand the trigger clause with natural user phrasings, e.g. 'Use when the user wants to search or enrich Clay contacts, companies, or automate Clay workflows.'

Dimension	Reasoning	Score
Specificity	Names the Clay domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Clay-specific operations.	3 / 5
Completeness	Provides both a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Clay data'), though the trigger could be more concrete.	4 / 5
Trigger Term Quality	Includes some relevant natural terms ('Clay data', 'records', 'workflows') but misses common variations or synonyms a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	Tightly scoped to Clay with distinct triggers, low overlap risk with unrelated skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/clay/SKILL.md
Commit: f484c82

Reviewed: ~10 hours 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.