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

The body is an exemplary instruction-only skill: a tight, well-sequenced workflow with concrete field names, explicit validation checkpoints, and thorough error-handling boundaries covering missing tools, incomplete delivery, and context compaction. Its only real gap is the absence of a concrete example of the tool call itself (parameter shape for `task_context` and the invocation format), which keeps actionability at 4 rather than 5.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes Claude's competence: no general concepts are explained, every section (Goal, Workflow, Boundaries) carries only task-specific instructions such as "Treat returned Rules as constraints, not as evidence that unobserved facts are true" and "delivery.complete=false means some matched Rules are absent". Even the tool-name enumeration serves discovery rather than padding, so every token earns its place.

5 / 5

Actionability

The guidance is mostly executable: a five-step workflow anchored in concrete field names (`task_context`, `applies_when`, `exception`, `delivery.complete`) and specific fallback behaviors. It falls short of fully executable because the tool invocation itself is never shown (no example call or parameter shape for `task_context`) and "Read omitted compiled Rule URIs or the saved full result in bounded sections" leaves the retrieval mechanism unspecified — minor gaps, matching the level-4 anchor.

4 / 5

Workflow Clarity

The workflow is a clear five-step sequence with explicit validation (step 3: review every Rule against `applies_when` and `exception`) and genuine feedback loops: re-call on materially changed context (step 5), handle incomplete delivery by reading omitted Rules in bounded sections, and refresh after context compaction. This is not a destructive/batch operation and validation is present, so no cap applies; it matches the level-5 anchor with error-recovery paths (report unavailable check, pause if Rules cannot be retrieved).

5 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no bundle files present and no external references needed; per the rubric's guideline, well-organized sections (Goal, Workflow, Boundaries) suffice for a 5. Structure is clean and each section is clearly signaled with nothing inlined that belongs elsewhere.

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 is well-formed: third-person voice, a clear two-part what/when structure with an explicit "Use when" clause, and a distinctive named domain (OpenViking Rules). Its main weaknesses are a thin action list and an abstract, narrow trigger vocabulary that leans on "constraints" without synonyms users would naturally say. It sits comfortably above mediocre but below the exemplary examples in the rubric.

Suggestions

Expand the action list beyond two verbs, e.g. "Retrieve applicable OpenViking Rules, validate the planned action against each Rule's applies_when and exception conditions, and adjust the plan for compliance".

Broaden trigger terms with natural synonyms and variations users would actually say, e.g. "Use when planning an action or response subject to task-specific constraints, rules, policies, or compliance requirements".

Make the "when" clause more concrete by naming the situations that call for the skill, such as "when the user asks to check rules, verify compliance, or plan an action under policy constraints".

DimensionReasoningScore

Specificity

"Retrieve applicable OpenViking Rules and check compliance" names the domain (OpenViking Rules) and exactly two concrete actions, matching the anchor "Names domain and 1-2 concrete actions, but not comprehensive". It is not a 4 because there is no list of several specific actions (e.g., what compliance checking involves or what outputs are produced), and not a 2 because the actions are concrete rather than minimal or generic.

3 / 5

Completeness

Both parts are present: the "what" ("Retrieve applicable OpenViking Rules and check compliance") and an explicit "Use when" clause ("Use when planning an action or response subject to task-specific constraints"). The "when" is explicit but abstract — it names no concrete trigger phrases like "when the user mentions rules, policies, or compliance requirements" — so it fits "Has both 'what' and 'when'; 'when' could be more explicit or specific" rather than the level-5 anchor.

4 / 5

Trigger Term Quality

The description includes some relevant keywords a user might say ("Rules", "compliance", "task-specific constraints") but misses common variations and synonyms such as "policies", "guidelines", "regulations", or "restrictions", matching the anchor "Some relevant keywords but missing common variations or synonyms". It is above a 2 because the terms present are domain-relevant rather than purely generic, but below a 4 because coverage of natural phrasings is narrow.

3 / 5

Distinctiveness Conflict Risk

The named system "OpenViking Rules" creates a clear niche with tool-specific triggers, making it mostly distinct from other skills. However, the when-clause "planning an action or response subject to task-specific constraints" is broad — many tasks could be framed as constraint-subject — leaving minor overlap risk with generic policy/constraint-checking skills, which fits the level-4 anchor rather than "minimal conflict risk" at 5.

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