CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-search

Find external documentation, web sources, or remote code with citations. Local code navigation uses the configured code tools.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-search/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 a dense, well-structured routing skill: concrete CLI commands, a sequenced workflow with explicit failure-recovery branches, and clearly annotated one-level-deep references. Main gaps are the missing docs-route command, an implicit rather than explicit validation gate, and referenced resource files that are not present in the bundle.

Suggestions

Add the docs-route command (e.g. "oma search docs ...") to the CLI entry points block so every route has an executable entry.

Wire resources/checklist.md into the final workflow step as an explicit validation gate instead of listing it only in References.

Ship the referenced resources/*.md files (or inline their essentials) — none are present in the bundle, so the skill currently points at unverifiable paths.

DimensionReasoningScore

Conciseness

The body is telegraphic and operational throughout (e.g. "oma doctor checks credential presence without verifying validity or API reachability") with no explanations of concepts Claude already knows, matching "efficient; minor instances that could be trimmed". It is not 5 because resource files are cited both in workflow steps and again in the References section, and a few over-compressed lines ("no numeric lookup is required for ordinary results") require re-reading.

4 / 5

Actionability

The CLI entry points block gives copy-paste-ready commands ("oma search web \"<query>\" [--provider <id>] [--limit <n>]", "oma search fetch <url>") and the routes table maps each route to concrete execution. It is not 5 because the docs route (Context7) has no CLI command shown and step-level specifics are delegated to resources/*.md files, leaving a minor gap for the most common route.

4 / 5

Workflow Clarity

The four-step canonical workflow is clearly sequenced and the "Failure and recovery" section provides explicit feedback loops (provider failure -> report; no results -> refine or report; strict gap -> report). It is not 5 because validation is implicit rather than an explicit gate: resources/checklist.md appears only in the References list, not as a verification step in the workflow path; not 3 because recovery branches and exit criteria are explicitly stated.

4 / 5

Progressive Disclosure

The References section signals six resources/*.md files plus ../_shared/core/code-intelligence.md, each with a one-line purpose label (e.g. "Recovery: resources/error-playbook.md (route failure)"), one level deep. It is not 5 because none of the referenced files exist in the provided bundle (no references/, scripts/, assets/, or resources/ directories), so the reference targets cannot be verified and the skill depends entirely on files not shipped here.

4 / 5

Total

16

/

20

Passed

Description

66%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 states a clear, reasonably specific capability set with an effective local/external boundary, but lacks any explicit "Use when..." trigger guidance and misses natural search phrasings. Adding a trigger clause would raise both completeness and trigger coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. "Use when the user asks to search the web, find library documentation, search remote code, or read a known URL".

Include natural user phrasings such as "web search", "look up", or "fetch this URL" to broaden trigger-term coverage.

Mention known-URL reading/fetching in the capability list to close the gap with the skill's actual routes.

DimensionReasoningScore

Specificity

"Find external documentation, web sources, or remote code with citations" lists several concrete capability targets (documentation, web sources, remote code, citations) plus an explicit boundary ("Local code navigation uses the configured code tools"), matching the anchor for several specific actions with minor gaps. It is not 5 because the body shows the skill also reads known URLs and selects search providers, which the description omits; not 3 because coverage goes beyond 1-2 actions.

4 / 5

Completeness

The "what" is clear ("Find external documentation, web sources, or remote code with citations"), but there is no "Use when..." clause; the second sentence ("Local code navigation uses the configured code tools") only weakly implies when to use the skill as a boundary statement. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "external documentation", "web sources", "remote code", "citations", and "Local code navigation" give good natural keyword coverage across the docs/web/code space. It is not 5 because common user phrasings such as "search the web", "web search", "look up", or "read/fetch this URL" are absent; not 3 because coverage is noticeably broader than a few scattered keywords.

4 / 5

Distinctiveness Conflict Risk

The external-vs-local contrast ("Find external documentation, web sources, or remote code" vs. "Local code navigation uses the configured code tools") carves a mostly distinct niche with minor overlap risk against generic web-search or research skills. It is not 5 because without explicit triggers, a request like "find docs for X" could still route ambiguously among related skills.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

first-fluke/oh-my-agent

Path

.agents/skills/oma-search/SKILL.md

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.