CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

Quality

96%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 high-quality, actionable skill: domain-specific and concise, with copy-paste tool calls and clearly sequenced workflows that include explicit validation checkpoints for destructive and batch operations. Its only gap is progressive disclosure — a dense migration section could be split into a reference file for cleaner navigation.

Suggestions

Consider extracting the detailed 'Move local skills' classification rules (vendor prefixes, environment-bound conditions, clean-up-first flags) into a one-level-deep reference file (e.g. references/migration.md) with a clear pointer from SKILL.md to improve progressive disclosure.

The 'when a task looks like one a stored skill would cover' trigger in the description is broad; narrow it (e.g. to skill-authoring/install/migrate tasks) to reduce overlap risk with the openviking-memory skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it explains only OpenViking-specific details Claude would not know (URI expansion, tool-name prefixes, add_skill semantics, zip-upload flow) with no concept padding, fitting the score-5 'every token earns its place' anchor rather than the minor-over-explanation anchor at 4.

5 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: parameterized tool calls like find(query=..., context_type="skill") and add_skill(data=...), plus a complete zip/curl upload command, matching the score-5 anchor for copy-paste-ready code covering common cases.

5 / 5

Workflow Clarity

Multi-step processes (Create, Install, Move local skills) are clearly sequenced with explicit validation checkpoints — confirm-before-replace, user-approves-upload, and a tree-based verify step — and a classify→confirm→upload→verify→remember checklist; because validation is present the destructive-ops cap does not apply, matching the score-5 anchor.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, but the file is a single self-contained document (~125 lines) with a dense 'Move local skills' section whose classification rules could arguably live in a one-level-deep reference, fitting the score-4 'good structure, minor organization gaps' anchor better than the split-and-signaled anchor at 5.

4 / 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.

The description is strong: it states a comprehensive set of concrete actions, provides explicit multi-clause trigger guidance, and even quotes natural user phrases in English and Chinese. Its only weakness is a somewhat broad 'when a task looks like one a stored skill would cover' trigger that risks minor overlap with adjacent skills.

DimensionReasoningScore

Specificity

Lists seven concrete actions ('Find, use, create, install, share, update, and migrate agent skills') plus 'Covers the add_skill tool, running a skill's helper files, and which local skills must stay local' — comprehensive concrete coverage, matching the score-5 anchor rather than the several-actions-with-minor-gaps anchor at 4.

5 / 5

Completeness

Explicitly answers what ('Find, use, create, install, share, update, and migrate agent skills stored in OpenViking') and when via multiple concrete 'Use it when...' clauses, matching the score-5 anchor that requires both what and when with concrete trigger phrases; not capped at 3 since an explicit 'Use when' clause is present.

5 / 5

Trigger Term Quality

Direct quoted user phrases appear verbatim, including synonyms in two languages ('upload my skills', 'save this as a skill', '迁移本地 skill', '把 skill 存到 OpenViking', '新建一个 skill'), giving comprehensive natural-term coverage with synonyms, exceeding the good-coverage anchor at 4.

5 / 5

Distinctiveness Conflict Risk

The OpenViking-specific niche (viking://~/skills, viking://agent/skills, add_skill) is mostly distinct, but the broad trigger 'when a task looks like one a stored skill would cover' creates minor overlap risk with closely related skills such as openviking-memory, fitting the score-4 anchor better than the minimal-conflict anchor at 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
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.