clay-load-scale
Scale Clay enrichment pipelines for high-volume processing (10K-100K+ leads/month). Use when planning capacity for large enrichment runs, optimizing batch processing, or designing high-volume Clay architectures. Trigger with phrases like "clay scale", "clay high volume", "clay large batch", "clay capacity planning", "clay 100k leads", "clay bulk enrichment".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clay-pack/skills/clay-load-scale/SKILL.mdQuality
Discovery
89%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 well-structured skill description with strong completeness and distinctiveness. It clearly defines its niche (high-volume Clay enrichment) and provides explicit trigger guidance. The main weakness is that the specific capabilities could be more concrete—listing actual actions like configuring rate limits, managing API credits, or setting up parallel processing tables rather than staying at the architectural/planning level.
Suggestions
Add more concrete specific actions beyond planning/designing, such as 'configure rate limits, manage API credit budgets, set up parallel enrichment tables, optimize waterfall sequences for throughput'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay enrichment pipelines) and mentions some actions like 'capacity planning', 'batch processing', and 'high-volume architectures', but doesn't list multiple concrete specific actions (e.g., configuring rate limits, setting up parallel tables, managing credit budgets). The actions remain somewhat high-level. | 2 / 3 |
Completeness | Clearly answers both 'what' (scale Clay enrichment pipelines for high-volume processing) and 'when' (planning capacity for large enrichment runs, optimizing batch processing, designing high-volume architectures) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes a good range of natural trigger terms that users would actually say: 'clay scale', 'clay high volume', 'clay large batch', 'clay capacity planning', 'clay 100k leads', 'clay bulk enrichment'. These cover multiple natural variations of how a user might phrase their need. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Clay platform + high-volume/scaling concerns. The volume thresholds (10K-100K+) and specific trigger terms like 'clay capacity planning' and 'clay bulk enrichment' make it clearly distinguishable from a general Clay skill or a general data processing skill. | 3 / 3 |
Total | 11 / 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, actionable skill with concrete TypeScript implementations for scaling Clay enrichment pipelines. Its main strengths are the executable code examples and domain-specific knowledge about Clay's limits (50K webhook caps, credit models, plan tiers). Weaknesses include the length of inline code that could be referenced externally, and the lack of explicit validation/verification checkpoints in the multi-step batch processing workflow.
Suggestions
Add explicit validation checkpoints between steps—e.g., 'Verify credit budget is sufficient before proceeding to Step 2' and 'Confirm webhook health with a test payload before queueing full batch'.
Move the longer code implementations (batch processor, webhook rotator) into referenced files and keep only concise usage examples inline in the SKILL.md.
Add a budget/credit verification step integrated into the batch queue workflow to prevent credit overruns, rather than only listing it in the error table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity—e.g., the full BullMQ worker implementation is quite long, and some inline comments explain obvious things. The capacity planner function could be more concise. However, most content is domain-specific knowledge Claude wouldn't inherently know. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with concrete implementations for capacity planning, batch processing, webhook rotation, and multi-table strategies. Code is copy-paste ready with proper imports, types, and error handling including rate limit retries. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no explicit validation checkpoints between steps. For batch operations at this scale (10K-100K+ leads), there should be verification steps—e.g., confirming credit budget before submitting, validating webhook health before queueing, or checking batch completion status. The error handling table helps but isn't integrated into the workflow. | 2 / 3 |
Progressive Disclosure | The skill has reasonable section structure and references external resources and a related skill at the end. However, the inline code blocks are quite lengthy (the batch processor alone is ~70 lines) and could benefit from being split into referenced files. The YAML table strategy section is well-structured but the overall document is heavy for a SKILL.md overview. | 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
3e83543
- 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.