CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ov-resources

Search and read documents, repos, URLs, and other resources stored in OpenViking under viking://resources/. Use whenever the user asks about docs, specs, codebases, papers, or notes that were added to OpenViking ("check the docs", "what does our design doc say", "find it in OpenViking"), or when a task needs reference material this session does not have. Covers picking between find, grep, glob, and list, and drilling from a hit down to the exact file.

76

Quality

95%

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

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.

A lean, well-structured instruction-only skill: system-specific conventions, concrete tool signatures, a clear drill-down workflow with stopping criteria and fallback guidance. The only gap is the absence of a fully literal worked-example call, leaving actionability just short of copy-paste ready.

Suggestions

Add one fully literal worked example, e.g. grep("viking://resources/specs", pattern=["rate limit"]), so the tool signatures become copy-paste ready.

DimensionReasoningScore

Conciseness

Every line carries system-specific knowledge Claude cannot infer (".abstract.md" / ".overview.md" summary levels, "Low scores (under ~0.4) are usually noise", when to use "search instead of find"). No filler and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Near-executable tool calls are given throughout: "find(query, target_uri=\"viking://resources\")", "grep(uri, pattern=[...])", "glob(pattern, uri) e.g. **/*.pdf", plus "read with offset/limit around the match". Not 5 because invocations use placeholder parameters with no single fully literal worked example (e.g., a real grep call with an actual pattern and URI) to copy-paste.

4 / 5

Workflow Clarity

The drill-down is a clear numbered sequence (find hit → read .overview.md → list/scoped find/grep → read the file) with an explicit stopping criterion ("Stop as soon as you have what the task needs") and an error-recovery feedback loop ("If find returns nothing useful, list viking://resources... then search inside the closest directory"). Operations are read-only, so no validation cap applies.

5 / 5

Progressive Disclosure

The body is ~45 lines with well-organized sections (Pick the tool / Drill down / Tips) and no external references needed; no bundle files exist, so this fits the under-50-lines exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

96%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.

A strong description with explicit what and when clauses, natural user phrasings quoted verbatim, and a distinctive OpenViking/viking:// niche. The only weakness is the broad "needs reference material this session does not have" trigger, which invites overlap with general research skills.

Suggestions

Tighten the broad trigger "when a task needs reference material this session does not have" to reference OpenViking-hosted material specifically, reducing overlap with general research/web-search skills.

DimensionReasoningScore

Specificity

"Search and read documents, repos, URLs, and other resources" plus "Covers picking between find, grep, glob, and list, and drilling from a hit down to the exact file" lists multiple concrete actions comprehensively covering the skill's scope; no meaningful coverage gap exists.

5 / 5

Completeness

Explicitly answers what ("Search and read... resources stored in OpenViking under viking://resources/") and when ("Use whenever the user asks about... or when a task needs reference material this session does not have") with concrete trigger phrases, in third-person voice.

5 / 5

Trigger Term Quality

Natural terms users would actually say are present: "docs, specs, codebases, papers, or notes" plus quoted phrases "check the docs", "what does our design doc say", "find it in OpenViking" — comprehensive synonym and phrasing coverage.

5 / 5

Distinctiveness Conflict Risk

"OpenViking" and "viking://resources/" define a clear niche, but the clause "when a task needs reference material this session does not have" is broad and could overlap with general research or web-search skills. Not 5: minor overlap risk with closely related skills.

4 / 5

Total

19

/

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

volcengine/OpenViking

Path

agent-plugins/skills/ov-resources/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.