agent-production-validator
Agent skill for production-validator - invoke with $agent-production-validator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-production-validator40
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/skillEvaluation — 98%
↑ 1.22xAgent success when using this skill
Validation for skill structure
Discovery
0%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 description is critically deficient across all dimensions. It functions only as an invocation reference ('invoke with $agent-production-validator') rather than a functional description. Claude would have no basis for selecting this skill appropriately since there's no information about capabilities, use cases, or trigger conditions.
Suggestions
Add specific concrete actions describing what production-validator does (e.g., 'Validates deployment configurations, checks service health, verifies production readiness')
Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when deploying to production, checking deployment status, or validating release candidates')
Remove the invocation syntax from the description and replace with functional content that distinguishes this skill from other validation or production-related tools
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for production-validator' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what does this do' and 'when should Claude use it'. The description only provides invocation syntax, not functional information. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'production-validator' which is technical jargon. No natural keywords a user would say like 'validate', 'deploy', 'check production', etc. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'production-validator' could mean anything from code validation to deployment checks to data validation. No clear niche or distinct triggers. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is excessively verbose, treating Claude like a junior developer who needs to be taught how to write tests and connect to databases. The content lacks a clear workflow for actually performing production validation, instead presenting a catalog of example code patterns. The skill would benefit from dramatic condensation to essential commands and patterns, with a clear step-by-step validation process.
Suggestions
Reduce content to ~50 lines focusing on: (1) the grep commands to detect mocks, (2) a clear 5-step validation workflow, and (3) a checklist of what to verify
Add a clear sequential workflow: 'Step 1: Scan for mocks → Step 2: Verify env vars → Step 3: Run integration tests → Step 4: Check security → Step 5: Validate deployment config'
Remove all the TypeScript test examples - Claude knows how to write tests. Instead, specify what to test and acceptance criteria
Split detailed examples into separate reference files (e.g., EXAMPLES.md) and keep SKILL.md as a concise overview with clear navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive code examples that explain concepts Claude already knows (how to write tests, connect to databases, make API calls). The 400+ lines could be condensed to ~50 lines of key patterns and validation commands. | 1 / 3 |
Actionability | Contains executable code examples, but they're generic templates rather than project-specific guidance. The bash commands in the checklist are actionable, but the TypeScript examples are illustrative patterns rather than copy-paste ready solutions. | 2 / 3 |
Workflow Clarity | No clear sequential workflow for performing production validation. Content is organized as a reference catalog of validation types rather than a step-by-step process. Missing explicit validation checkpoints and feedback loops for the overall validation process. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline despite being far too long. No clear navigation structure or separation between quick-start and advanced content. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.