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

77%

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/agent-hook-plugin/hosts/cursor/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

85%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 compact, well-structured instruction skill: a clear five-step workflow with a re-check feedback loop, and a Boundaries section that covers every operational failure mode (missing tool, incomplete delivery, stale context) with specific, directive language. Its only weaknesses are minor — a partially redundant tool-name enumeration and the absence of an example task_context or Rule payload.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes competence — no concept explanations, tight steps, dense Boundaries. The one trimmable spot is the enumeration "rule_search, openviking_rule_search, mcp__openviking__rule_search, ov_rule_search, viking_rule_search", which is partially redundant with "or another server-qualified variant; use the exact registered name". Matches "minor instances of over-explanation that could be trimmed"; not 5 due to that redundancy, not 3 because everything else earns its place.

4 / 5

Actionability

Guidance is concrete and semantic-rich: build `task_context` from goal/action/facts, apply Rules via "applies_when" and "exception", handle "delivery.complete=false" with bounded reads of omitted URIs. The minor gap is that no example shows what a task_context payload or a returned Rule looks like, so the first call is guided by description rather than copy-paste-ready form. Matches anchor 4; not 5 (no example covering the common case), not 3 (nothing is pseudocode or missing key mechanics).

4 / 5

Workflow Clarity

Five clearly sequenced steps with an explicit feedback loop ("Call the Rule search tool again when new information materially changes the task context") and error-recovery handling for every failure mode: missing tool ("Report the unavailable check"), incomplete delivery (bounded section reads, pause if unretrievable), and expired lookups ("refresh Rules for the current task"). Matches anchor 5's "clear sequence with explicit validation steps; feedback loops for error recovery"; not 4 because checkpoints are explicit, not merely mostly present.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ exist) and nothing that belongs in a separate file; content is cleanly sectioned into Goal, Workflow, and Boundaries. Per the simple-skill guideline, this earns 5 with just well-organized sections; it is not 4 because there are no organization gaps to point to.

5 / 5

Total

18

/

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 is well-formed: third-person, concise, with a clear what and an explicit "Use when" clause anchored to a distinct system (OpenViking Rules). Its main weakness is thin capability coverage and missing natural trigger synonyms, leaving the when-clause somewhat abstract. It sits comfortably in the middle of the scale — solid but not exemplary.

Suggestions

Enumerate the concrete capabilities instead of the generic "check compliance" — e.g., "Retrieve compiled Rules that constrain a task, validate plans against each Rule's applies_when and exception conditions, and re-check when context changes."

Add natural trigger terms users would actually say — "rules", "policy", "compliance check", "constraints", and the tool names (rule_search) — so the skill triggers on real user phrasing, not just system jargon.

Make the "Use when" clause more concrete, e.g., "Use when the user mentions OpenViking Rules, policies, or compliance constraints, or before executing any action governed by registered Rules."

DimensionReasoningScore

Specificity

"Retrieve applicable OpenViking Rules and check compliance" names the domain and two actions (retrieve, check compliance), but stops there — no mention of validating against applies_when/exception conditions, re-checking, or handling incomplete deliveries. This matches the anchor "Names domain and 1-2 concrete actions, but not comprehensive"; it is above 2 because the actions are concrete and domain-specific, and below 4 because it does not list several specific actions.

3 / 5

Completeness

Both parts are present: the what ("Retrieve applicable OpenViking Rules and check compliance") and an explicit when ("Use when planning an action or response subject to task-specific constraints"). The when-clause is explicit but abstract — "task-specific constraints" is not a concrete trigger phrase — matching anchor 4 rather than 5; it is above 3 because a genuine "Use when..." clause exists.

4 / 5

Trigger Term Quality

Relevant keywords are present ("OpenViking Rules", "compliance", "task-specific constraints", "planning an action"), but common user phrasings and synonyms ("rules", "policy", "guidelines", tool names) are missing. Matches "Some relevant keywords but missing common variations or synonyms"; not 2 because the terms are not purely generic jargon, not 4 because coverage of natural user terms is thinner than "PDF files, forms, document extraction".

3 / 5

Distinctiveness Conflict Risk

"OpenViking Rules" pins a clear niche with minimal conflict risk, but "check compliance" and "planning an action or response subject to task-specific constraints" are broad enough to overlap with general policy/compliance skills, since nearly any task is "subject to constraints". Matches "Mostly distinct; minor overlap risk"; not 5 because the when-clause is not a distinct trigger, not 3 because the named system makes it more specific than a generic document/file skill.

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/agent-hook-plugin/hosts/cursor/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.