clay-policy-guardrails
Implement Clay lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Clay integrations, implementing pre-commit hooks, or configuring CI policy checks for Clay best practices. Trigger with phrases like "clay policy", "clay lint", "clay guardrails", "clay best practices check", "clay eslint".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-policy-guardrails78
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 that excels in completeness and trigger term quality with explicit 'Use when' and 'Trigger with phrases' clauses. The Clay-specific focus makes it highly distinctive. The main weakness is that the capabilities could be more concrete—listing specific rule types or enforcement actions would strengthen specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay lint rules, policy enforcement, guardrails) and some actions (setting up rules, implementing hooks, configuring CI checks), but lacks comprehensive concrete actions like specific rule types or enforcement mechanisms. | 2 / 3 |
Completeness | Clearly answers both what (implement lint rules, policy enforcement, automated guardrails) and when (explicit 'Use when...' clause with specific scenarios plus 'Trigger with phrases' providing additional guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'clay policy', 'clay lint', 'clay guardrails', 'clay best practices check', 'clay eslint', and contextual phrases like 'pre-commit hooks' and 'CI policy checks'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Clay-specific terminology throughout. The combination of 'Clay' prefix on all trigger terms and focus on linting/policy enforcement creates a clear niche unlikely to conflict with general linting or other integration skills. | 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 skill provides comprehensive, actionable code examples for Clay policy enforcement across multiple tools (ESLint, pre-commit, CI, OPA). However, it's somewhat verbose with sections like ADR templates that don't directly serve the core purpose, and the workflow lacks explicit validation checkpoints between implementation steps.
Suggestions
Add explicit validation steps between the 4 implementation steps (e.g., 'Verify ESLint rule fires: npx eslint --print-config . | grep clay')
Move the ADR template and OPA policy sections to separate reference files, keeping SKILL.md focused on the core ESLint + pre-commit + CI workflow
Add a troubleshooting feedback loop: 'If pre-commit hook fails silently, check .git/hooks/pre-commit exists and is executable'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary sections like the ADR template which adds bulk without being directly actionable for the stated purpose of implementing lint rules and guardrails. | 2 / 3 |
Actionability | Provides fully executable code examples throughout - complete ESLint plugin implementation, pre-commit config, CI workflow YAML, TypeScript patterns, and OPA policies. All examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are listed at the end but lack validation checkpoints. For policy enforcement involving CI and pre-commit hooks, there's no explicit verify-then-proceed workflow or error recovery guidance between steps. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the document is quite long (200+ lines) with inline content that could be split into separate reference files. Only one external reference to 'clay-architecture-variants' at the end. | 2 / 3 |
Total | 9 / 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.