CtrlK
BlogDocsLog inGet started
Tessl Logo

build-fix

Build Fix deprecated shim

44

Quality

45%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/build-fix/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The body is appropriately terse for a hard-deprecated shim and unambiguously tells Claude not to invoke it while pointing to替代 workflows. Its main weakness is that the redirection names generic workflow categories instead of concrete replacement skills, leaving the redirect slightly soft.

DimensionReasoningScore

Conciseness

The four-line body is lean and assumes Claude's competence, with no padding or explanation of concepts Claude already knows; every token earns its place, matching the 'Lean and efficient' anchor.

5 / 5

Actionability

It gives concrete redirection guidance ('Do not invoke or route this skill'; route build failures to 'the active execution, debugging, or verification workflow') but provides no executable code or precise target skill names, fitting 'Some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The single action (do not invoke; redirect build failures elsewhere) is unambiguous and the simple-skill exception applies, but the redirection names workflow categories rather than specific skills, leaving a minor gap below the fully-explicit anchor (5).

4 / 5

Progressive Disclosure

For a sub-50-line skill needing no external references, the heading plus clear deprecation notice is well-organized; it stops short of a 5 only because a leftover '{{ARGUMENTS}}' placeholder and lack of explicit routing targets slightly reduce navigational crispness.

4 / 5

Total

16

/

20

Passed

Description

16%Weight 40%Scale 1-5

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 is a terse, jargon-laden label that fails to convey what the skill concretely does or when to use it, and offers no meaningful trigger guidance. It reads as a stub rather than a usable skill description.

Suggestions

Add a 'Use when...' trigger clause so users and routing know when (if ever) this skill applies, or state explicitly that it is deprecated and should never be routed.

Replace the noun phrase with concrete actions or a clear deprecation rationale (e.g., 'Deprecated: formerly rerouted build failures to the debugging workflow; do not invoke').

Include natural user-facing keywords (e.g., 'build failure', 'broken build', 'compile error') if any routing is still intended.

DimensionReasoningScore

Specificity

The description 'Build Fix deprecated shim' names the domain ('Build Fix') but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic' rather than the entirely-vague (1) or action-listing (3) anchors.

2 / 5

Completeness

The description offers an extremely vague noun-phrase 'what' and no 'when'/trigger guidance at all, matching 'Missing both what and when, or both are extremely vague' rather than the vague-what-plus-no-when anchor (2).

1 / 5

Trigger Term Quality

'Build' and 'Fix' are only mildly natural keywords while 'deprecated shim' is technical jargon, missing the common phrases a user would actually say; this fits 'One or two generic keywords; missing the natural phrases users say' below the relevant-keywords anchor (3).

2 / 5

Distinctiveness Conflict Risk

'Build Fix' is a very broad domain with high overlap risk against many debugging/execution/verification skills, fitting 'Very broad; high overlap risk with many similar skills' rather than the entirely-generic (1) or somewhat-specific (3) anchors.

2 / 5

Total

7

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
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.