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".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly communicates what the skill does (Clay account setup and configuration), when to use it (onboarding, connecting providers, configuring keys), and includes explicit trigger phrases. It uses proper third-person voice, is concise without being vague, and provides enough specificity to distinguish it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: setting up account access, API keys, webhook URLs, and provider connections. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (set up account access, API keys, webhook URLs, provider connections) and 'when' (explicit 'Use when' clause with onboarding, connecting providers, configuring keys, setting up webhooks, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'install clay', 'setup clay', 'clay auth', 'configure clay API key', 'connect clay providers', plus contextual phrases like 'onboarding to Clay' and 'webhook endpoints'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Clay-specific terminology and setup/configuration focus. The combination of 'Clay' as a product name with specific setup actions (API keys, webhooks, providers) creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid setup/onboarding skill with excellent actionability — concrete commands, specific UI paths, and real examples. Its main weaknesses are moderate verbosity (explanatory sentences that don't add value for Claude) and missing validation/verification checkpoints between steps. The error handling table is a useful addition but the skill could be tighter overall.
Suggestions
Add explicit verification checkpoints after key steps (e.g., 'Expected response: 200 OK with JSON body containing...' after the API key test, and 'Verify the row appeared in your Clay table before proceeding' after webhook test)
Remove explanatory sentences Claude doesn't need, such as 'Clay is a web-based data enrichment platform', 'This is the primary way to send data into Clay programmatically', and the Output section which restates completed steps
Consider moving the provider connection table and error handling table to a separate reference file to keep the main skill leaner
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., 'Clay is a web-based data enrichment platform', 'This is the primary way to send data into Clay programmatically') and the provider table with credit savings details is nice-to-have but adds bulk. The Output section restates what was already covered. However, it's not egregiously verbose. | 2 / 3 |
Actionability | Provides fully executable curl commands, concrete .env file templates, specific UI navigation paths (Settings > API, Settings > Connections), and a detailed provider table with key locations. Every step is copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but there are no validation checkpoints or feedback loops. Step 1 has a verification curl but doesn't explain what success/failure looks like. Step 2 says 'record appears within seconds' but doesn't instruct to verify. Step 5 on webhook authentication doesn't explain how to verify the secret is working on the receiving end. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical flow, and it references external resources and a next-steps skill. However, the provider connection table and error handling table could potentially be split into separate reference files. For a standalone skill with no bundle files, the inline content is somewhat long but reasonably organized. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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 | |
- Commit
3a2d27d
- 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.