CtrlK
BlogDocsLog inGet started
Tessl Logo

clay-install-auth

Set up Clay account access, API keys, webhook URLs, and provider connections. Use when onboarding to Clay, connecting data providers, configuring API keys, or setting up webhook endpoints for programmatic data flow. Trigger with phrases like "install clay", "setup clay", "clay auth", "configure clay API key", "connect clay providers".

78

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-structured, actionable setup skill with executable commands, a sensible step sequence including verification, and a useful error-handling table. It stays lean by surfacing only Clay-specific knowledge and avoids teaching concepts Claude already knows.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence; it adds only Clay-specific facts Claude wouldn't know (credit savings, plan rate limits, webhook submission limits) without explaining generic concepts.

3 / 3

Actionability

Fully executable curl commands with real endpoints, env-var assignments, and concrete JSON payloads, plus a provider table with exact key locations — copy-paste ready.

3 / 3

Workflow Clarity

Five clearly sequenced steps with built-in verification (Step 1 test lookup, Step 5 webhook auth check) and an error-handling table providing recovery feedback loops; not a destructive/batch workflow, so validation is adequate.

3 / 3

Progressive Disclosure

Single well-organized SKILL.md with clear sections (Overview, Prerequisites, Instructions, Error Handling, Output, Resources, Next Steps) and one-level external doc links in Resources — no nested bundle references, appropriate for a self-contained setup skill.

3 / 3

Total

12

/

12

Passed

Description

100%

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

A strong, third-person description that clearly states capabilities, provides explicit 'Use when' guidance, and lists natural trigger phrases tied to the Clay domain. Voice is correctly third person and there is no over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Set up Clay account access, API keys, webhook URLs, and provider connections' — naming specific artifacts rather than vague capabilities.

3 / 3

Completeness

Explicitly answers both what ('Set up Clay account access, API keys, webhook URLs, and provider connections') and when ('Use when onboarding to Clay, connecting data providers...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural phrases a user would say — 'install clay', 'setup clay', 'clay auth', 'configure clay API key', 'connect clay providers' — covering common onboarding variations.

3 / 3

Distinctiveness Conflict Risk

Clay-specific niche with 'clay' embedded in every trigger phrase, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.