deepsearch

Deepsearch deprecated shim

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/deepsearch/SKILL.md

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 content body is a model deprecation shim: concise, unambiguous, and pointing to two concrete replacement tools. It achieves full marks across all content dimensions for its scope.

Dimension	Reasoning	Score
Conciseness	The body is lean and every token earns its place ('Hard-deprecated. Do not invoke or route this skill.'), assuming Claude's competence with no padding or restated concepts.	3 / 3
Actionability	It gives concrete, copy-paste-ready redirects — 'Use `$analyze`' and 'omx explore' — which are specific executable commands rather than vague direction.	3 / 3
Workflow Clarity	As a simple single-purpose skill the single action (do not invoke; redirect to one of two named tools) is unambiguous, satisfying the simple-skill allowance for a top score.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references, the single clear header and well-organized body meet the bar for a top progressive-disclosure score.	3 / 3
	Total	12 / 12 Passed

Description

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 rather than a capability description, omitting both actions and use-when triggers. It distinguishes the named skill somewhat but offers nothing for routing or invocation.

Suggestions

Add a brief 'what' statement even for deprecated skills, e.g. 'Legacy deepsearch skill, replaced by $analyze and omx explore.'

Include explicit trigger guidance such as 'Do not use; route deep-repository analysis requests to $analyze instead.'

Replace internal jargon ('shim') with user-facing language that clarifies the skill's status and replacement.

Dimension	Reasoning	Score
Specificity	The phrase 'Deepsearch deprecated shim' names a domain but describes no concrete actions, matching the 'vague or no actions' anchor rather than the score-2 example which at least lists actions like 'Processes PDF files and extracts content'.	1 / 3
Completeness	It states neither what the skill does (it is deprecated and does nothing) nor when to use it; the explicit guidance is instead 'do not use', so both 'what' and 'when' are effectively missing.	1 / 3
Trigger Term Quality	No natural user-facing keywords appear; 'deepsearch' is a skill name and 'deprecated shim' is internal jargon, offering nothing a user would naturally say to trigger this skill.	1 / 3
Distinctiveness Conflict Risk	Naming the specific domain 'deepsearch' gives it some specificity, but 'deprecated shim' carries no functional trigger and could still overlap with other skills.	2 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Yeachan-Heo/oh-my-codex
Path: skills/deepsearch/SKILL.md
Commit: 435d4a9

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.