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

71%

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 ./skills/oma-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, terse router skill: concrete CLI entry points, a routes table, explicit failure-and-recovery loops, and disciplined guardrails, with no padding or over-explanation. Its main defects are the dangling references — most of the resource files cited in the workflow and References section are absent from the bundle — and abstract workflow steps that depend on those missing files. Fixing the reference targets would raise both progressive disclosure and actionability.

Suggestions

Create the six referenced resources/*.md files (intent-rules, execution-protocol, trust-registry, error-playbook, checklist, examples) or correct the paths to files that exist in the bundle — currently 6 of 7 referenced paths do not resolve, which is the lowest-scoring dimension.

Add one or two concrete example invocations with realistic values (e.g., oma search web "pydantic v2 model config" --provider brave) so the CLI guidance is copy-paste ready for common cases.

Merge the overlapping "Intent signature" and "When to use" sections and inline one or two concrete recovery commands to tighten token use and make failure handling executable.

DimensionReasoningScore

Conciseness

The body is dense and information-rich with no explanations of concepts Claude already knows (it does not explain what Context7 or a search provider is), and guardrails are stated tersely. Minor tightening is possible — the "Intent signature" and "When to use" sections overlap, and the three-part section taxonomy (Scheduling/Structural Flow/Logical Operations) adds slight ceremony — so it fits anchor 4 rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete, executable guidance is present: a copy-paste CLI block with flags ("oma search web \"<query>\" [--provider <id>] [--limit <n>]"), a routes table with execution details, and precise modifier semantics ("--strict requires suitable primary or official sources"). Minor gaps remain — workflow steps are abstract ("Resolve the requested outcome and constraints") and key details defer to resource files that are not present in the bundle — keeping it below anchor 5's fully-executable, example-covered level.

4 / 5

Workflow Clarity

The canonical workflow is a clear 4-step sequence, and the "Failure and recovery" section provides explicit feedback loops (missing docs → official-site discovery; no candidate URLs → refine within constraints or report; strict gap → report the gap). This is a retrieval skill with no destructive or batch operations, so no cap applies; recovery guidance stays abstract (no concrete commands), fitting anchor 4 rather than anchor 5's explicit validation commands.

4 / 5

Progressive Disclosure

The in-body structure is good — a References section lists one-level-deep files each with a clear purpose annotation — but scoring against the actual bundle reveals that 6 of the 7 referenced paths (resources/intent-rules.md, execution-protocol.md, trust-registry.md, error-playbook.md, checklist.md, examples.md) do not exist in the provided bundle; only references/_shared/core/code-intelligence.md resolves. Clearly signaled references that point to non-existent files break navigation, matching anchor 3's could-be-better-organized level rather than anchor 4's well-placed content.

3 / 5

Total

15

/

20

Passed

Description

58%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, concrete capability (external docs/web/remote-code search with citations) with an explicit boundary against local code navigation, giving it good specificity and distinctiveness. Its main weaknesses are the missing "Use when..." trigger clause, which caps completeness, and keyword coverage that lacks the natural synonyms users would actually say. Adding an explicit trigger clause with natural phrasing would lift the two lowest dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to search the web, find library documentation, look up external sources, or read a known URL" — this directly addresses the completeness cap.

Include natural user-spoken synonyms such as "search", "look up", and "fetch a URL" alongside the current "Find external documentation, web sources, or remote code" phrasing to improve trigger-term coverage.

Mention the known-URL reading capability (a stated route in the body) so the description's capability coverage matches the skill's actual scope.

DimensionReasoningScore

Specificity

"Find external documentation, web sources, or remote code with citations" names several concrete capability areas (docs search, web search, remote code search, citation-backed results) with only minor gaps (e.g., known-URL reading is not mentioned). It lists several specific actions rather than the 1-2 of anchor 3, though the single-verb pattern keeps it below anchor 5's comprehensive multi-action coverage.

4 / 5

Completeness

The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance; the second sentence ("Local code navigation uses the configured code tools") is a scope exclusion that only weakly implies when to use the skill. Per the rubric guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ("documentation", "web sources", "remote code", "citations") but common natural variations are missing — users would say "search the web", "look this up", or "find docs", and "web sources"/"remote code" are more jargon-adjacent than user-spoken phrases. This matches anchor 3 (some relevant keywords, missing synonyms) better than anchor 4's good-but-incomplete coverage.

3 / 5

Distinctiveness Conflict Risk

The description carves a clear external-search niche and explicitly boundaries it ("Local code navigation uses the configured code tools"), reducing conflict with local-code skills. Minor overlap risk remains with closely related skills (generic web-fetch or code-search tools), so it fits anchor 4 rather than anchor 5's minimal-conflict clear niche.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

first-fluke/oh-my-agent

Path

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.