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

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A well-structured, highly actionable auth/setup skill: clear sequenced steps with verification, executable copy-paste commands, and a useful error-recovery table. Minor conciseness slack from credit-savings commentary is the only weak point.

DimensionReasoningScore

Conciseness

The body is mostly lean, executable curl/.env commands and concrete tables, with the Overview purposefully correcting the no-SDK misconception; minor credit-savings commentary lightly pads it but most tokens earn their place (borderline 3).

3 / 3

Actionability

Fully copy-paste-ready curl examples, a concrete .env template, precise UI navigation ('Settings > API', 'Settings > Connections'), and provider/error tables provide concrete executable guidance.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced with explicit verification (test lookup in Step 1, 'Verify Webhook Authentication' in Step 5) and an error-handling table giving feedback/recovery; this is config/auth setup, not a destructive/batch op, so no cap applies.

3 / 3

Progressive Disclosure

No bundle files exist; the skill is a single self-contained file with well-organized sections and no nested references, with external links kept to one-level web docs, matching the well-organized-sections allowance.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, specific description that states concrete actions, gives explicit 'Use when' guidance, and lists natural trigger phrases for a clearly distinct niche. It uses appropriate third-person imperative voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Set up Clay account access, API keys, webhook URLs, and provider connections' — matching the multi-action anchor rather than the partial anchor 2.

3 / 3

Completeness

Answers both what (setup actions) and when ('Use when onboarding to Clay, connecting data providers...') with explicit triggers, satisfying the explicit-when anchor rather than the implied-when anchor 2.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would say ('install clay', 'setup clay', 'clay auth', 'configure clay API key', 'connect clay providers'), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

A clear Clay-specific niche with distinct triggers unlikely to fire for unrelated skills; voice is imperative/third person with no first/second-person penalty.

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.