clay-reference-architecture
Implement Clay reference architecture with best-practice project layout. Use when designing new Clay integrations, reviewing project structure, or establishing architecture standards for Clay applications. Trigger with phrases like "clay architecture", "clay best practices", "clay project structure", "how to organize clay", "clay layout".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-reference-architecture70
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 description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is the somewhat abstract description of capabilities - it mentions 'best-practice project layout' but doesn't specify what concrete actions or outputs the skill provides (e.g., generating folder structures, creating config files, etc.).
Suggestions
Add specific concrete actions the skill performs, such as 'generates folder structures', 'creates configuration templates', or 'produces architecture diagrams' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay reference architecture) and mentions actions like 'designing new Clay integrations' and 'reviewing project structure', but lacks concrete specific actions like what the architecture includes or what specific tasks it performs. | 2 / 3 |
Completeness | Clearly answers both what (implement Clay reference architecture with best-practice project layout) and when (designing new integrations, reviewing structure, establishing standards) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clay architecture', 'clay best practices', 'clay project structure', 'how to organize clay', 'clay layout'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Clay platform architecture with distinct triggers. The 'clay' prefix on all trigger terms makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid architectural reference with good structure and concrete code examples, but falls short of excellence in several areas. The content is somewhat verbose with explanatory diagrams that add length without proportional value, code examples are incomplete/illustrative rather than executable, and the workflow lacks validation checkpoints for a multi-step setup process.
Suggestions
Make code examples fully executable by defining or importing ClayClient, Cache, and Monitor dependencies, and completing the wrapClayError function body
Add validation checkpoints to the workflow (e.g., 'Verify client connects: npm run test:clay-connection' after Step 2)
Split detailed content (full code examples, configuration schemas, diagrams) into separate reference files, keeping SKILL.md as a concise overview with links
Remove or condense the ASCII diagrams - the layer architecture and data flow can be described more concisely in text or removed entirely as Claude understands these patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the prerequisites section (Claude knows what layered architecture is) and verbose ASCII diagrams that could be simplified. The structure is good but could be tighter. | 2 / 3 |
Actionability | Provides concrete TypeScript code examples and a bash setup script, but many code blocks are incomplete (e.g., wrapClayError function body is empty, ClayClient/Cache/Monitor are undefined). The code is illustrative rather than fully executable. | 2 / 3 |
Workflow Clarity | Steps are listed (Step 1-4 in Instructions section) but lack validation checkpoints. For an architecture setup involving multiple files and configurations, there's no verification that each step succeeded before proceeding to the next. | 2 / 3 |
Progressive Disclosure | References external docs and a flagship skill at the end, but the main content is a long monolithic file. The project structure, layer diagrams, code examples, and configuration could be split into separate reference files with SKILL.md as a concise overview. | 2 / 3 |
Total | 8 / 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.