CtrlK
BlogDocsLog inGet started
Tessl Logo

validation-gates

Defines 10 sequential validation gates: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, smoke tests. Use when running pre-deploy validation or CI checks, CI/CD pipelines, deployment pipeline validation, pre-merge checks, continuous integration, or pull request validation.

77

Quality

96%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

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 strong skill description that clearly articulates specific capabilities (10 named validation gates) and provides explicit trigger guidance via a comprehensive 'Use when...' clause. It uses third-person voice appropriately and covers multiple natural keyword variations for CI/CD and deployment validation scenarios. The description is both concise and information-dense.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, smoke tests. These are clearly defined validation gates.

3 / 3

Completeness

Clearly answers both 'what' (defines 10 sequential validation gates with specific steps listed) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios for CI/CD and deployment contexts).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'pre-deploy validation', 'CI checks', 'CI/CD pipelines', 'deployment pipeline validation', 'pre-merge checks', 'continuous integration', 'pull request validation'. Good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche around pre-deploy validation pipelines with 10 sequential gates. The specificity of the validation steps and the CI/CD deployment context make it unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Implementation

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-structured skill that clearly defines a 10-gate validation pipeline with concrete commands, thresholds, and escalation paths. The workflow sequencing is excellent with explicit triggers, failure modes, and feedback loops. The only notable weakness is that referenced files (REFERENCE.md, various skills) cannot be verified since no bundle was provided, and some gates could benefit from slightly more separation of detailed content into reference files.

DimensionReasoningScore

Conciseness

The content is lean and well-structured using tables and concise descriptions. It avoids explaining basic concepts and assumes Claude understands CI/CD, npm, and testing. Every section delivers actionable information without padding.

3 / 3

Actionability

Nearly every gate includes executable commands (gitleaks, npm audit, rm -rf cache dirs, npm test, playwright), concrete thresholds (lines changed ≤200, bundle size ≤50KB), and specific tool invocations. The blast radius table provides clear numeric criteria for decision-making.

3 / 3

Workflow Clarity

The 10 gates are clearly sequenced with explicit triggers ('Runs When' column), escalation paths (Normal/Warning/Escalate), failure handling (BLOCK, re-delegate max 2, then Gate 9), and feedback loops (3× FAIL → Panel Review). Validation checkpoints are built into the workflow structure itself.

3 / 3

Progressive Disclosure

References to REFERENCE.md, fast-review skill, browser-testing skill, and panel-majority-vote skill are well-signaled, but no bundle files were provided to verify these exist. The snippet reference to never-expose-secrets.md is good practice, but the skill inlines a fair amount of detail that could potentially be split out for gates with more complex logic.

2 / 3

Total

11

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.