CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openviking-rule-search

Retrieve applicable OpenViking Rules and check compliance. Use when planning an action or response subject to task-specific constraints.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./examples/dsh-memory-plugin/skills/openviking-rule-search/SKILL.md

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

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: every section adds non-obvious operational guidance, the workflow is explicitly sequenced with validation and re-check steps, and the Boundaries section doubles as thorough error recovery for failure modes like missing tools and truncated deliveries. The only meaningful gap is the absence of a concrete example of a task_context payload or tool call, which keeps actionability at 4.

DimensionReasoningScore

Conciseness

The body is ~40 lines with no padding: it never explains concepts Claude already knows ("Treat returned Rules as constraints, not as evidence that unobserved facts are true" is non-obvious operational guidance, not a tutorial), and even the tool-name alias list ("rule_search, openviking_rule_search, mcp__openviking__rule_search...") earns its tokens by handling real host variance. This matches the 'every token earns its place' anchor; it is not 4 because there is no section that could be trimmed without losing operational value.

5 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: "Build task_context from the user's goal, the planned action or decision, and concrete facts", "Apply a Rule when its applies_when condition is supported by the task context and no exception applies", and specific handling of "delivery.complete=false". It falls short of 5 only because no example task_context payload or sample tool invocation is given, leaving a minor gap between 'mostly executable' and copy-paste ready.

4 / 5

Workflow Clarity

Five clearly sequenced steps with explicit validation (step 3: "Review every returned Rule independently" against applies_when/exception conditions) and a re-check trigger (step 5: "Call the Rule search tool again when new information materially changes the task context"). The Boundaries section supplies error-recovery feedback loops for missing tools, failed requests, incomplete delivery, and compaction expiry ("If the remaining Rules cannot be retrieved, report the incomplete check and pause the action"), matching the anchor with explicit validation and feedback loops; no destructive/batch cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (references/, scripts/, assets/ are absent), and needs no external references; the body is well-organized into Goal, Workflow, and Boundaries sections. Per the simple-skill guideline this matches the top anchor; it is not 4 because there is no content that should have been split out or any organization gap.

5 / 5

Total

19

/

20

Passed

Description

62%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 answers both 'what' and 'when' in third person and anchors itself to a distinctive proprietary system (OpenViking Rules), but its action list is thin ('check compliance' is generic) and its trigger vocabulary misses natural synonyms. The broad 'when' clause is its main weakness, making activation criteria feel abstract rather than phrase-level concrete.

Suggestions

Replace the generic 'check compliance' with the skill's concrete operations, e.g. 'Retrieve applicable OpenViking Rules, evaluate each Rule's applies_when and exception conditions, and adjust the planned action to comply.'

Add natural trigger phrases and synonyms users would actually say, e.g. 'Use when the user mentions Rules, guidelines, policies, compliance, or asks to validate a plan against OpenViking Rules.'

Narrow the 'when' clause beyond 'planning an action or response subject to task-specific constraints', which matches nearly any task, to Rule-specific activation conditions that reduce overlap with general planning skills.

DimensionReasoningScore

Specificity

"Retrieve applicable OpenViking Rules and check compliance" names the domain plus two actions (retrieve, check compliance), matching the 'Processes PDF files and extracts content' anchor of domain + 1-2 concrete actions without comprehensive coverage. It is not 4 because only two actions are listed and 'check compliance' is generic, not several specific actions with minor gaps.

3 / 5

Completeness

Both parts are explicit: 'what' via "Retrieve applicable OpenViking Rules and check compliance" and 'when' via "Use when planning an action or response subject to task-specific constraints", matching the anchor where both exist but 'when' could be more specific. It is not 5 because the 'when' clause is abstract — nearly any task is 'subject to task-specific constraints' — and lacks concrete trigger phrases; not 3 because the 'Use when' guidance is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

Relevant keywords are present ("Rules", "compliance", "task-specific constraints"), but natural variations a user would say — guidelines, policies, validate a plan against the Rules — are absent, matching the 'Works with PDF files' anchor of some relevant keywords missing common synonyms. It is not 4 because coverage is too thin to count as 'good keyword coverage with a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

The proper noun "OpenViking Rules" carves out a clear niche unlikely to collide with unrelated skills, matching 'mostly distinct; minor overlap risk'. It is not 5 because the broad trigger ("planning an action or response subject to task-specific constraints") could fire in many planning contexts, leaving minor overlap risk with general planning or validation skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

volcengine/OpenViking

Path

examples/dsh-memory-plugin/skills/openviking-rule-search/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.