CtrlK
BlogDocsLog inGet started
Tessl Logo

deepsearch

Deepsearch deprecated shim

52

Quality

56%

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

Quality

Content

92%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 an efficient, clear deprecation redirect that tells Claude exactly what not to do and where to route instead. Its only minor gap is that the replacement commands are named rather than given as ready-to-run invocations.

DimensionReasoningScore

Conciseness

The body is a lean three-sentence redirection with zero padding and no explanation of concepts Claude already knows; every token earns its place. This matches the lean-and-efficient anchor.

5 / 5

Actionability

It gives concrete replacement commands ($analyze, omx explore) with clear routing criteria, which is mostly executable guidance. It stays at 4 rather than 5 because the commands are referenced by name without copy-paste-ready invocation syntax.

4 / 5

Workflow Clarity

As a single-purpose deprecation shim, the single action is unambiguous: do not invoke, redirect based on need (deep analysis vs. fast lookup). The simple-skill exception applies and there is no destructive/batch operation requiring validation.

5 / 5

Progressive Disclosure

The skill is well under 50 lines, single-purpose, and needs no external references; the content is appropriately self-contained and organized. The under-50-lines/no-references exception applies.

5 / 5

Total

19

/

20

Passed

Description

21%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 bare deprecation label with no capability description or trigger guidance. It is too sparse and jargon-laden to function as a meaningful skill description.

Suggestions

Add a concrete statement of what deepsearch did and what replaces it, e.g. "Deprecated — formerly performed deep repository analysis; use $analyze instead."

Include natural trigger phrasing so the description reads as guidance a user or Claude would actually act on, not just a status tag.

If the skill is hard-deprecated, consider keeping the description as a routing pointer but make the replacement triggers explicit (e.g. mention "repository analysis", "repo lookup").

DimensionReasoningScore

Specificity

"Deepsearch deprecated shim" names the domain (deepsearch) and its status, but offers no concrete actions — matching the anchor that names the domain with minimal/generic actions. It does not reach 3 because no concrete capability is described.

2 / 5

Completeness

It gives a vague "what" (a deprecated shim) and entirely lacks a "when/Use when" trigger clause, which the guidelines cap at 3 at most. It cannot be 3 because no explicit trigger guidance is present.

2 / 5

Trigger Term Quality

The only terms are the skill's own name "deepsearch" and jargon "deprecated shim"; a user would never naturally say this phrase to trigger a capability. This matches the anchor for no natural keywords / only technical jargon.

1 / 5

Distinctiveness Conflict Risk

Naming the specific skill "deepsearch" gives it a niche, but as a deprecation marker it is not a clear functional trigger and could still overlap conceptually with other analysis skills. It is more distinct than the generic anchor 2 but lacks the clear functional triggers of anchor 4.

3 / 5

Total

8

/

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.