Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.
Install with Tessl CLI
npx tessl i github:rohitg00/skillkit --skill verification-gates90
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
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 an excellent skill description that clearly articulates what the skill does (creates validation checkpoints and produces various gate configurations), when to use it (explicit trigger terms covering quality gates, approvals, phase transitions), and provides concrete examples of outputs. The description uses proper third-person voice and includes both high-level purpose and specific deliverables.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates explicit validation checkpoints', 'produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules' with specific scenarios like 'security changes, API changes, or database migrations'. | 3 / 3 |
Completeness | Clearly answers both what (creates validation checkpoints, produces checklists and configurations) AND when (explicit 'Use when...' clause listing quality gates, milestone checks, phase transitions, approval steps, go/no-go decisions, preventing cascading errors). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'quality gates', 'milestone checks', 'phase transitions', 'approval steps', 'go/no-go decision points', 'cascading errors', 'multi-step workflow'. These are terms users would naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on validation checkpoints and phase gates with distinct triggers like 'verification gates', 'go/no-go decision points', and specific outputs like 'CI gate configurations'. Unlikely to conflict with general workflow or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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, actionable skill with excellent workflow clarity and concrete, executable examples. The main weakness is its length - the content could be more concise by trimming explanatory text and splitting detailed templates/CI configurations into separate reference files for better progressive disclosure.
Suggestions
Move the detailed CI/CD YAML examples and Gate Documentation Template to a separate REFERENCE.md file, keeping only a brief example in the main skill
Trim the 'Gate Metrics' section - the concepts of effectiveness, overhead, and value are self-evident to Claude and don't need explanation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (e.g., the core principle is restated in various forms, gate metrics section explains obvious concepts). The checklists and tables are appropriately dense, but some sections could be tightened. | 2 / 3 |
Actionability | Provides fully executable YAML configurations for CI pipelines, concrete markdown checklists, specific GitHub Actions examples, and clear templates. The guidance is copy-paste ready with real commands and configurations. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit gates, clear sequencing (Gate 1 → Gate 5), visual flow diagram, and explicit failure actions. Each gate has verification methods and the CI/CD integration shows proper dependency chains with 'needs' clauses. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and a quick reference table, but it's a long monolithic document (~200 lines) that could benefit from splitting detailed gate templates and CI examples into separate reference files. The 'Integration with Other Skills' section hints at related content but doesn't provide navigation links. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.