CtrlK
BlogDocsLog inGet started
Tessl Logo

ov-experience-memory

Retrieve and apply OpenViking Experience memories through the Agent runtime's generic OpenViking search and read tools. Use before or during executable, multi-step, or tool-based work such as coding, file or data changes, configuration, deployment, workflow execution, and failure recovery when prior operational guidance could improve reliability. Do not use for casual chat or simple factual questions.

68

Quality

82%

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 ov-experience-memory in volcengine/OpenViking

SKILL.md
Quality
Evals
Security

Quality

Content

81%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-structured, actionable instruction skill with an explicit, validated multi-step workflow and error-recovery loops. It is slightly verbose in places and could move the legacy-server edge case to a reference file for leaner progressive disclosure.

Suggestions

Consolidate the repeated 'continue without Experience' caveats into a single Preconditions rule to reduce token redundancy (conciseness).

Move the 'Servers Without the Home Alias' legacy-server recovery detail into a separate reference file, leaving a one-line pointer in the main workflow (progressive_disclosure).

Add a short copy-pasteable example block showing the exact search call (tool name + target_uri + query + limit) for the most common runtime (actionability).

DimensionReasoningScore

Conciseness

The body is dense and operational, explaining OpenViking-specific mechanics (URIs, server versions) that Claude would not already know, but the phrase 'continue without Experience' and similar caveats recur several times and could be trimmed.

4 / 5

Actionability

Provides concrete, actionable guidance — exact URIs ('viking://~/memories/experiences'), 'limit=5', per-runtime tool names in a table, error signature 'INVALID_URI (HTTP 400)', and a sample query — with only minor gaps in copy-paste-ready form.

4 / 5

Workflow Clarity

The 8-step Retrieval Workflow is clearly sequenced with explicit validation ('Judge results by task, environment, preconditions, and likely effect; title similarity alone is insufficient'), a failure feedback loop (step 8: one focused follow-up search), and an error-recovery path for servers without the home alias.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no bundle files to navigate, but the version-specific 'Servers Without the Home Alias' edge case is inlined where a separate reference could keep the core workflow leaner.

4 / 5

Total

17

/

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, third-person description that clearly states capability and triggers with a useful negative boundary. It is comprehensive on completeness but could add a few more concrete action verbs and synonyms to push specificity and trigger coverage higher.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Retrieve and apply OpenViking Experience memories through...search and read tools') and enumerates several specific contexts (coding, file/data changes, configuration, deployment, workflow execution, failure recovery), but the verb set is essentially two actions, leaving minor coverage gaps relative to a fully comprehensive list.

4 / 5

Completeness

Explicitly answers both what ('Retrieve and apply OpenViking Experience memories through...search and read tools') and when ('Use before or during executable, multi-step, or tool-based work such as...') with concrete trigger phrases, and adds a negative boundary ('Do not use for casual chat or simple factual questions').

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('coding', 'file or data changes', 'configuration', 'deployment', 'failure recovery') plus an explicit 'Use before or during executable, multi-step, or tool-based work' trigger, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The 'OpenViking Experience memories' niche is specific and the negative-scope clause reduces misfires, but it still has minor overlap risk with general memory/recall skills.

4 / 5

Total

17

/

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.