agent-production-validator

Agent skill for production-validator - invoke with $agent-production-validator

1.22x

Quality

Does it follow best practices?

Impact

98%

1.22x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-production-validator/SKILL.md

Quality

Discovery

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 an extremely weak description that fails on all dimensions. It provides no information about what the skill does, when it should be used, or what triggers should activate it. It reads as a placeholder rather than a functional description that Claude could use to select the right skill.

Suggestions

Describe the concrete actions this skill performs (e.g., 'Validates production deployments by checking service health, configuration correctness, and dependency availability').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to validate a production environment, check deployment readiness, or verify production configuration').

Remove the invocation instruction ('invoke with $agent-production-validator') from the description and replace it with functional details about what the skill does and when it applies.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for production-validator' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an agent skill and how to invoke it, providing no functional or contextual information.	1 / 3
Trigger Term Quality	The only keyword is 'production-validator', which is a technical/internal name rather than a natural term a user would say. There are no natural language trigger terms like 'validate', 'deploy', 'check production', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it's impossible to distinguish it from other skills. 'Production-validator' hints at a domain but without any specifics, it could conflict with any validation or production-related skill.	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, presenting generic testing patterns and boilerplate code that Claude already knows how to write. It lacks a clear sequential workflow for performing production validation and dumps all content into a single monolithic file. The content would benefit enormously from being condensed to a concise checklist with key commands, with detailed examples moved to separate reference files.

Suggestions

Reduce the main skill to a concise validation checklist (under 50 lines) with the key bash grep commands and a clear sequential workflow, moving detailed test examples to separate reference files like EXAMPLES.md

Add a clear step-by-step workflow with explicit validation checkpoints and feedback loops (e.g., 'If mock implementations found → fix → re-scan → proceed only when clean')

Remove generic test code patterns (CRUD tests, load tests, security tests) that Claude already knows how to write, and focus only on project-specific patterns or non-obvious validation logic

Fix the regex pattern formatting issues ($ used instead of / in patterns like $mock[A-Z]\w+$g) to ensure code examples are actually executable

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Most code examples are generic test patterns Claude already knows (CRUD tests, health checks, load testing). The skill explains obvious concepts like what mock implementations are and provides boilerplate test code that doesn't add unique value.	1 / 3
Actionability	Contains concrete TypeScript code examples and bash commands, but they are illustrative templates rather than truly executable, copy-paste-ready code. The regex patterns have formatting issues (using $ instead of /), and the code depends on undefined project-specific infrastructure that limits direct executability.	2 / 3
Workflow Clarity	There is no clear sequential workflow for performing production validation. The content is organized as a collection of independent code snippets and checklists without a defined order, validation checkpoints, or feedback loops for when issues are found. The numbered sections don't form a coherent process.	1 / 3
Progressive Disclosure	Monolithic wall of text with all content inline. No references to external files for detailed examples. The massive code blocks for database testing, API testing, infrastructure testing, performance testing, and security testing should be split into separate reference files with the SKILL.md providing a concise overview.	1 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: ruvnet/claude-flow
Commit: f547cec

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.