CtrlK
BlogDocsLog inGet started
Tessl Logo

ask-claude

Deprecated compatibility shim for Claude advisor requests

64

Quality

75%

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/ask-claude/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is an exemplary lean deprecation shim: concise, fully actionable with concrete replacement commands, and clearly organized for its minimal scope. No external references are needed and none are promised, so progressive disclosure is satisfied.

DimensionReasoningScore

Conciseness

The body is a lean six lines with no padding and no explanation of concepts Claude already knows; every line (deprecation notice, replacement commands, one-sentence rationale) earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

It provides two concrete, copy-paste-ready replacement commands ('$ask claude <question>' and 'omx ask claude "<question>"') that tell Claude exactly what to do, matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

This is a single-purpose deprecation redirect under 50 lines with no multi-step or risky operation; the single action (do not use this, use these commands instead) is unambiguous, so per the simple-skills note workflow clarity scores 3.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is self-contained and under 50 lines, so per the simple-skills note well-organized sections alone warrant a 3; the single heading and instruction paragraph are appropriately structured with no nested references.

3 / 3

Total

12

/

12

Passed

Description

50%

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 identifies a clear niche but is written in technical jargon with no explicit 'when to use' trigger guidance, capping most dimensions at 2. It is functional for a deprecated shim but would not help a user naturally discover or select this skill.

Suggestions

Rewrite in third-person action voice naming concrete actions (e.g., 'Routes Claude advisor requests to the canonical $ask workflow'), even if deprecated.

Add an explicit trigger clause or, since it is deprecated, state plainly 'Do not use for new work; invoke $ask claude directly' to satisfy the 'when' requirement.

Replace jargon ('compatibility shim') with natural user-facing terms to improve trigger term quality.

DimensionReasoningScore

Specificity

The phrase 'compatibility shim for Claude advisor requests' names a specific domain and function, but lists no concrete actions — matching the 'names domain and some actions, but not comprehensive' anchor rather than the vague level 1 or the multi-action level 3.

2 / 3

Completeness

It states what the skill is ('compatibility shim') but provides no 'Use when...' trigger guidance, which per the guidelines caps completeness at 2; it is not level 1 because 'what' is present, and not level 3 because 'when' is entirely absent.

2 / 3

Trigger Term Quality

Terms like 'compatibility shim' and 'advisor requests' are technical jargon a user would not naturally say; relevant keywords exist but common natural variations are missing, so it sits at level 2 rather than the well-covered level 3 or the jargon-only level 1.

2 / 3

Distinctiveness Conflict Risk

The 'Claude advisor requests' niche is reasonably specific and unlikely to broadly conflict, but the discouragement of use leaves triggers imprecise, fitting the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

8

/

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.

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.