Configures Jahro lifecycle controls for safe production deployment including JAHRO_DISABLE, auto-disable, and build validation. Use when the user mentions production builds, release builds, disabling Jahro, shipping, CI/CD, lifecycle controls, or production safety.
89
88%
Does it follow best practices?
Impact
85%
3.14xAverage score across 3 eval scenarios
Passed
No known issues
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (lifecycle controls, JAHRO_DISABLE, auto-disable, build validation), includes a comprehensive 'Use when...' clause with natural trigger terms, and is highly distinctive due to Jahro-specific terminology. The description follows best practices with third-person voice and clear, concise language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configures Jahro lifecycle controls', 'JAHRO_DISABLE', 'auto-disable', and 'build validation'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (configures lifecycle controls including specific features) AND when (explicit 'Use when...' clause with comprehensive trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'production builds', 'release builds', 'disabling Jahro', 'shipping', 'CI/CD', 'lifecycle controls', 'production safety'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Jahro-specific terminology (JAHRO_DISABLE, auto-disable) and clear niche around production deployment safety. Unlikely to conflict with other 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 guidance. The three-tier disable mechanism is clearly explained with validation checkpoints. Main weaknesses are moderate verbosity (some redundant explanations) and the monolithic structure that could benefit from progressive disclosure to separate reference files.
Suggestions
Consider moving the detailed Lifecycle section and Role-Based Access table to separate reference files, keeping only essential production-focused content in the main skill
Remove redundant mentions of the validation message 'Jahro Console: Disabled in this build' - it appears 4 times across different sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy, such as repeating validation messages across sections and explaining the three-tier system multiple times. The role-based access section feels tangential to the core production readiness topic. | 2 / 3 |
Actionability | Provides fully executable code examples for CI/CD scripts, runtime validation, and clear step-by-step instructions with exact menu paths (Edit → Project Settings → Player). Copy-paste ready commands and code snippets throughout. | 3 / 3 |
Workflow Clarity | Excellent workflow structure with clear priority ordering (three-tier mechanism), explicit validation steps after each configuration, a comprehensive production checklist, and verification instructions at the end with specific success criteria. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear headers and logical sections, but it's a lengthy monolithic document (~150 lines) that could benefit from splitting detailed sections (CI/CD guidance, lifecycle details) into separate reference files. | 2 / 3 |
Total | 10 / 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.
300b45d
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.