CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ov-skills

Load when an agent needs to manage, install, update, remove, or validate OpenViking skills via the `ov skills` CLI. Trigger on explicit user requests about skill management, when the user mentions `ov skills`, `install skill`, `update skill`, `delete skill`, `validate skill`, or when an agent needs to discover what skills are available on the OpenViking server.

62

Quality

78%

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

Quality

Content

63%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 well-organized CLI reference with clear sequencing, explicit permission/safety guidance, and post-operation verification steps. Its main weaknesses are the absence of any inline executable command examples (all patterns deferred to a missing examples/commands.md) and Runtime Resources references that point to files not shipped in the bundle.

Suggestions

Inline 3-5 complete example commands (e.g., `ov skills add <github-url> --wait`, `ov skills show <name> -L 2 -o json`, `ov skills remove <name> --yes`) so command construction does not depend entirely on examples/commands.md, which is not present in the bundle.

Ship the referenced files — examples/commands.md, docs/upgrade-guide.md, and docs/source-types.md — inside the skill bundle (e.g., under references/); currently 'Runtime Resources' points to files that do not exist alongside SKILL.md.

Trim the 'Load When' section, which largely duplicates the trigger phrases already stated in the frontmatter description.

DimensionReasoningScore

Conciseness

The body is dense with CLI-specific facts Claude would not know (flag long-forms like `--uri` vs `--parent-auto-create`, `--yes` confirmation semantics, background-task checking), but the 'Load When' and 'Goal' sections partially restate the frontmatter description — minor trimming possible, matching anchor 4 rather than the lean 5.

4 / 5

Actionability

Provides concrete subcommands, aliases, and flags but zero complete example commands — construction is delegated entirely to `examples/commands.md` ("Construct the command with flags from `examples/commands.md` only"), which is not present in the bundle, so key executable details are missing (anchor 3, not 4's 'concrete commands with minor gaps').

3 / 5

Workflow Clarity

The four-step workflow is clearly sequenced, and destructive operations have checkpoints — confirmation prompts with `--yes` fallback, warnings that `remove --all` is destructive, and a Verification section with post-condition checks for add/remove/update — so the destructive-operation cap does not apply; it sits at anchor 4 rather than 5 because there is no explicit fix-and-retry feedback loop.

4 / 5

Progressive Disclosure

Sections are well organized and 'Runtime Resources' clearly signals one-level-deep references with descriptions, but none of the three referenced files (examples/commands.md, docs/upgrade-guide.md, docs/source-types.md) exist in the skill bundle (references/, scripts/, assets/ are absent and no examples/ or docs/ directories ship), so the deferral is dangling — structure is present but the split content is absent, matching anchor 3 rather than 4.

3 / 5

Total

14

/

20

Passed

Description

83%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 that explicitly covers both what the skill does and when to load it, with concrete and natural trigger phrases. Only minor gaps remain: a few missing synonyms (add/remove/list skill) and slight overlap risk from generic trigger terms.

DimensionReasoningScore

Specificity

Enumerates concrete lifecycle actions ("manage, install, update, remove, or validate OpenViking skills via the `ov skills` CLI") but omits the listing/searching/inspecting operations the skill also covers, matching the 4 anchor (several specific actions, minor gaps) rather than the comprehensive 5.

4 / 5

Completeness

Explicitly answers both what ("manage, install, update, remove, or validate OpenViking skills via the `ov skills` CLI") and when ("Load when an agent needs to... Trigger on explicit user requests... when the user mentions `ov skills`...") with concrete trigger phrases, matching the 5 anchor; anchor 4's caveat that 'when' could be more explicit does not apply.

5 / 5

Trigger Term Quality

Includes literal user phrases ("ov skills", "install skill", "update skill", "delete skill", "validate skill") but misses natural synonyms such as "add skill", "remove skill", and "list/search skills", fitting anchor 4 (good coverage, a few natural terms missing) rather than the 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to a distinct niche ("OpenViking skills", "OpenViking server"), but generic triggers like "install skill" and "validate skill" could overlap with other skill-management tools, matching anchor 4 (mostly distinct, minor overlap risk) rather than the minimal-conflict 5.

4 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

volcengine/OpenViking

Path

examples/skills/ov-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.