clay-sdk-patterns
Apply production-ready Clay SDK patterns for TypeScript and Python. Use when implementing Clay integrations, refactoring SDK usage, or establishing team coding standards for Clay. Trigger with phrases like "clay SDK patterns", "clay best practices", "clay code patterns", "idiomatic clay".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-sdk-patterns88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excellent trigger term coverage and completeness. The main weakness is the lack of specific concrete actions - it describes the purpose (patterns, best practices) but doesn't enumerate what specific SDK operations or patterns it covers. The explicit trigger phrases and clear 'Use when' clause make it highly functional for skill selection.
Suggestions
Add 2-3 specific concrete actions the skill covers, such as 'configure API clients', 'handle rate limiting', 'implement error handling patterns', or whatever specific Clay SDK operations are covered.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay SDK) and mentions some actions ('implementing Clay integrations, refactoring SDK usage, establishing team coding standards'), but lacks concrete specific actions like 'create API clients', 'handle authentication', or 'manage webhooks'. | 2 / 3 |
Completeness | Clearly answers both what ('Apply production-ready Clay SDK patterns for TypeScript and Python') and when ('Use when implementing Clay integrations, refactoring SDK usage, or establishing team coding standards'). Includes explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clay SDK patterns', 'clay best practices', 'clay code patterns', 'idiomatic clay'. Also mentions 'TypeScript and Python' which are relevant language keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Clay SDK specifically. The combination of 'Clay SDK', 'Clay integrations', and specific trigger phrases like 'idiomatic clay' make it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent code examples and efficient token usage. The patterns are production-ready and well-organized. The main weakness is the lack of validation checkpoints - there's no guidance on how to verify the implementations work correctly before deploying them.
Suggestions
Add a validation step after implementing each pattern (e.g., 'Test the singleton by calling getClayClient() twice and verifying the same instance is returned')
Include a simple integration test example to verify the retry logic works as expected before production use
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary code patterns without explaining basic concepts like what async/await is or how error handling works. Every section adds value. | 3 / 3 |
Actionability | All code examples are fully executable TypeScript/Python with proper imports, type annotations, and complete implementations. The patterns are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but there are no validation checkpoints or feedback loops. No guidance on how to verify the singleton is working correctly or how to test the retry logic before production use. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, Instructions, Examples, Resources). References to external docs and next steps are one level deep and clearly signaled. Content is appropriately split between core patterns and examples. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.