CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-builder

Use this skill when hardening an existing Codex skill or plugin for release. It produces focused audits, eval coverage, safety gates, and packaging/install handoff evidence.

63

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./Plugins/skill-factory/fixtures/budget-archive/2026-04-21/deferred-store/skills/code_quality_review/skill-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

This is a well-structured hardening/quality skill with strong actionability through specific CLI commands and a clear validation ladder. The workflow is well-sequenced with explicit fail-fast checkpoints and feedback loops. The main weakness is moderate verbosity—some content is repeated across sections (e.g., redaction constraints, routing boundaries) and the Philosophy section could be tighter, though the overall token cost is reasonable for the complexity of the task.

Suggestions

Consolidate duplicated constraints (e.g., 'redact secrets' appears in both Constraints and Failure mode sections) to reduce token overhead.

Tighten the Philosophy section—the two contract references with long relative paths and 'Read when:' guidance would fit better in the Context routes section where similar references already live.

DimensionReasoningScore

Conciseness

The skill is reasonably structured but contains some redundancy (e.g., the philosophy section restates principles that could be implicit, constraints like 'redact secrets' appear twice, and some sections like 'Anti-patterns' and 'Gotchas' overlap). The references to external contracts in the Philosophy section are verbose with full relative paths repeated. However, it generally avoids explaining concepts Claude already knows.

2 / 3

Actionability

The skill provides specific, executable validation commands (e.g., `./bin/ask skills audit <target-skill-path> --level strict --json`), a clear ordered workflow, concrete deliverable schema fields, and explicit pass/fail/blocked outcome categories. The validation section gives exact command sequences and a defined execution order.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (9 numbered steps), includes explicit validation checkpoints ('fail fast: stop at the first failed gate, fix it, and rerun'), defines a specific gate ordering (strict audit → smoke eval → Plugin Eval → Tessl review), and includes feedback loops for error recovery. The failure mode section adds additional guardrails including a cap on unchanged reruns.

3 / 3

Progressive Disclosure

The skill uses a well-structured 'Context routes' section with clear 'Read when:' signposts pointing to five reference files for deeper detail. The main SKILL.md serves as a map with appropriate depth, and the See Also table provides clear routing to related skills. References are one level deep and clearly signaled.

3 / 3

Total

11

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has a clear 'Use when...' clause and identifies a reasonably specific domain (hardening Codex skills/plugins for release), which is a strength. However, the listed capabilities are somewhat abstract ('focused audits', 'handoff evidence') and could benefit from more concrete action verbs and additional natural trigger terms to improve specificity and discoverability. The second-person 'Use this skill' phrasing is borderline but acceptable as it's a common pattern in the good examples.

Suggestions

Replace abstract terms like 'focused audits' and 'handoff evidence' with more concrete actions, e.g., 'Runs security and quality audits, generates test coverage reports, validates safety constraints, and produces install/packaging checklists.'

Add more natural trigger terms users might say, such as 'pre-release review', 'quality assurance', 'release readiness', 'deployment preparation', or 'plugin validation'.

DimensionReasoningScore

Specificity

Names the domain ('hardening an existing Codex skill or plugin') and lists some actions ('audits, eval coverage, safety gates, packaging/install handoff evidence'), but these are somewhat vague and not fully concrete—e.g., 'focused audits' and 'handoff evidence' lack specificity about what exactly is produced.

2 / 3

Completeness

Explicitly answers both 'what' (produces focused audits, eval coverage, safety gates, and packaging/install handoff evidence) and 'when' ('Use this skill when hardening an existing Codex skill or plugin for release'), with a clear trigger clause at the start.

3 / 3

Trigger Term Quality

Includes some relevant terms like 'hardening', 'skill', 'plugin', 'release', 'audits', 'eval coverage', 'safety gates', and 'packaging', but misses common natural variations a user might say such as 'quality assurance', 'pre-release checklist', 'testing', 'validation', or 'deployment readiness'.

2 / 3

Distinctiveness Conflict Risk

The niche of 'hardening a Codex skill or plugin for release' is fairly specific, but terms like 'audits', 'safety gates', and 'packaging' could overlap with general code review, security auditing, or CI/CD skills. The Codex-specific framing helps but doesn't fully eliminate conflict risk.

2 / 3

Total

9

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

9

/

11

Passed

Repository
jscraik/Agent-Skills
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.