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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-production-validator/SKILL.md

Quality

Content

14%Scale 1-3

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, spending most of its token budget on illustrative TypeScript test examples that Claude already knows how to write. It lacks a clear sequential workflow for actually performing production validation, reading more like a tutorial or documentation page than an actionable agent skill. The content would benefit enormously from being condensed to a concise checklist with the grep commands and key validation criteria, with detailed examples moved to separate reference files.

Suggestions

Reduce the content to a concise validation checklist (under 50 lines) with the concrete bash grep commands and a brief list of validation categories, removing all the illustrative TypeScript code that Claude already knows how to produce.

Add a clear sequential workflow with numbered steps, explicit go/no-go checkpoints, and feedback loops (e.g., 'If mock implementations found → fix → re-scan → only proceed when clean').

Move detailed code examples into separate bundle files (e.g., EXAMPLES.md, SECURITY_CHECKS.md) and reference them from the main skill with clear one-level-deep links.

Replace generic template code with project-specific executable commands or scripts that can actually be run, rather than illustrative patterns that require significant adaptation.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. The vast majority is illustrative TypeScript test code that Claude already knows how to write. Concepts like CRUD testing, Redis caching, SMTP sending, and load testing are explained at length with full code examples that don't teach Claude anything new. The entire skill could be reduced to a checklist of what to validate and the grep commands.	1 / 3
Actionability	The bash grep commands in the validation checklist are concrete and executable. However, the TypeScript code blocks are illustrative examples rather than executable scripts tied to a specific project — they're templates/pseudocode dressed up as real code, with placeholder environment variables and generic service names. Claude can't copy-paste these into any real project without significant adaptation.	2 / 3
Workflow Clarity	There is no clear sequential workflow for performing production validation. The content is organized as a collection of independent validation categories (code quality, environment, security, deployment) but lacks a defined order, dependencies between steps, or validation checkpoints with feedback loops. For a destructive/critical operation like production validation, the absence of a clear step-by-step process with explicit go/no-go gates is a significant gap.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no bundle files to support it. All content is inline regardless of complexity, with no separation between quick-reference material and detailed examples. The massive code blocks should be in separate reference files.	1 / 3
	Total	5 / 12 Passed

Description

0%Scale 1-3

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 provides no information about what the skill does, when to use it, or what domain it operates in. It reads as a placeholder rather than a functional description, making it essentially unusable for skill selection among multiple options.

Suggestions

Add concrete actions describing what 'production-validator' actually does, e.g., 'Validates production deployments by checking service health, configuration correctness, and dependency availability.'

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

Replace the invocation instruction ('invoke with $agent-production-validator') with domain-specific keywords that distinguish this skill from other validation or production-related skills.

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, with 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.	1 / 3
Distinctiveness Conflict Risk	The term 'production-validator' is too opaque to create a clear niche. Without knowing what it validates or in what context, it could conflict with any validation-related skill.	1 / 3
	Total	4 / 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
Path: .agents/skills/agent-production-validator/SKILL.md
Commit: 913f9ea

Reviewed: 3 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.