CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openviking-skills

Find, use, create, install, share, update, and migrate agent skills stored in OpenViking (viking://~/skills and viking://agent/skills). Use it when a search result, or the session's <available-skills> list where the harness injects one, names a skill that fits the task; when a task looks like one a stored skill would cover; when the user asks to write, save, install, or share a skill from text, a Git repository, or a local folder; when a skill should work in every harness and on every machine; or when the user wants to move local skills (~/.claude/skills, ~/.agents/skills, ~/.cursor/skills) into OpenViking — "upload my skills", "save this as a skill", "迁移本地 skill", "把 skill 存到 OpenViking", "新建一个 skill". Covers the add_skill tool, running a skill's helper files, and which local skills must stay local.

Quality

94%

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

The canonical home for this skill is openviking-skills in volcengine/OpenViking

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong operational skill: every instruction is concrete and executable, workflows are sequenced with confirmation and validation checkpoints, and the batch migration path is especially well-guarded. The two weaknesses are mild repetition of safety warnings and an entirely monolithic body despite enough reference-grade material to justify a split.

Suggestions

Consolidate the duplicated write/edit/add_resource prohibition — currently argued in both "Create or change a skill" and "Boundaries" — into a single place to remove the repetition holding conciseness below 5.

Move the per-harness local skill paths and the environment-bound classification criteria (step 2 of "Move local skills into OpenViking") into a references/ file (e.g. references/migration.md) so the main body stays a lean overview, improving progressive disclosure.

DimensionReasoningScore

Conciseness

Dense, imperative prose with no concept explanations Claude already knows — every section teaches OpenViking-specific facts (URI roots, tool semantics, installer quirks). Minor repetition keeps it below anchor 5: the write/edit/add_resource prohibition appears in both "Create or change a skill" and "Boundaries", and the keep-local-copies/deletion caution is stated twice.

4 / 5

Actionability

Fully executable throughout: exact tool calls with parameters (find(query="...", context_type="skill"), tree(uri=..., level_limit=1, include_abstract=true)), copy-paste shell for the zip upload (zip -r ... -x '*/.git/*' '*/.env*'; curl -sS -F "file=@..."), CLI flags (ov skills add -l -s a,b -p ...), and per-harness local skill paths. Covers the common cases: create from text, install from Git repo or folder, share, delete, migrate.

5 / 5

Workflow Clarity

Every workflow is a numbered sequence with checkpoints: the name-exists check before add_skill, user-confirmation gates on replace and delete, "ov skills validate <dir>" before upload, and an explicit Verify step ("tree(...) should list every uploaded name") plus a Remember step in the batch migration. The destructive/batch cap does not apply since all such operations carry validation or confirmation.

5 / 5

Progressive Disclosure

Clear section headers (Find, Use, Create, Install, Share, Delete, Move, Boundaries) make the single-file body easy to navigate, and no buried or nested references exist. At ~185 lines the environment-bound classification criteria and per-harness path list are reference-grade material that could live in a references/ file, so the fully monolithic structure sits below anchor 5.

4 / 5

Total

18

/

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.

An exemplary description: comprehensive concrete action list, explicit what-and-when structure, and quoted natural-language triggers including non-English phrasings users actually type. The only weakness is the deliberately broad stored-skill-matches-task trigger clause, which creates minor overlap risk with other skills.

DimensionReasoningScore

Specificity

"Find, use, create, install, share, update, and migrate agent skills stored in OpenViking" lists seven concrete lifecycle actions with comprehensive coverage and no vague filler. It does not fit anchor 4, which requires minor gaps in coverage — the action list spans the full skill lifecycle in a user's words.

5 / 5

Completeness

Explicitly answers both what ("Find, use, create, install, share, update, and migrate agent skills stored in OpenViking") and when (five distinct "Use it when..." conditions with concrete trigger phrases). The when-clause is explicit and enumerated, matching the anchor-5 example rather than the weaker anchor-4 form.

5 / 5

Trigger Term Quality

Quotes natural user phrasings directly — "upload my skills", "save this as a skill", "迁移本地 skill", "把 skill 存到 OpenViking", "新建一个 skill" — plus situational triggers (search result names a skill, user asks to write/save/install/share). Anchor 5's bar of synonyms and natural terms is met in two languages.

5 / 5

Distinctiveness Conflict Risk

Anchored to OpenViking-specific URIs (viking://~/skills, viking://agent/skills) and distinctive migration triggers, so mostly distinct. However "when a task looks like one a stored skill would cover" is broad enough to fire alongside any skill that matches a task, keeping it below anchor 5.

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

examples/opencode-plugin/skills/openviking-skills/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.