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/skills/openviking-rule-search/SKILL.md
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 an exemplary lean instruction skill: a clear five-step workflow with genuine validation checkpoints, feedback loops, and thorough failure-mode boundaries, organized into clean sections with no wasted tokens. Its one gap is actionability — the procedure references concrete fields and tool-name variants but never shows an example rule_search call or task_context payload, so the executor must invent the invocation format.

Suggestions

Add a short example showing the tool invocation, e.g. a sample task_context string and the call `rule_search(task_context="...")`, so the executor knows the expected parameter format.

Show one worked example of applying a returned Rule: a Rule with applies_when/exception fields and how the planned action is adjusted to comply, making the step-3 review concrete.

Briefly state what the tool response looks like (e.g., a list of Rules with URIs, applies_when, exception, and a delivery.complete flag) so the `delivery.complete=false` handling in Boundaries has a concrete referent.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and instructional throughout: sections state only goals, steps, and boundaries with no concept explanations or padding, assuming Claude's competence. Anti-drift check: the anchor-4 example of minor over-explanation does not appear anywhere in the text.

5 / 5

Actionability

The workflow names concrete fields (task_context, applies_when, exception, delivery.complete) and candidate tool names, but provides no example tool invocation or a sample task_context payload, leaving key execution details to guesswork. This matches 'some concrete guidance but incomplete / missing key details' rather than 4, which requires concrete commands with only minor gaps.

3 / 5

Workflow Clarity

Five clearly sequenced steps include an explicit validation checkpoint (review every returned Rule against applies_when/exception, then adjust to comply), a re-check feedback loop (step 5), and error-recovery handling for failed requests, incomplete deliveries, and compaction expiry in Boundaries. This matches the anchor with explicit validation steps and feedback loops for error recovery; no validation gaps are evident.

5 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references (no references/, scripts/, or assets/ directories exist and the body cites none), with well-organized Goal/Workflow/Boundaries sections. Per the rubric guideline for short simple skills, this earns a 5.

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 cleanly answers both what the skill does and when to use it, in a concise third-person style with a distinctive named system. Its main weaknesses are limited action coverage (only two verbs) and trigger terms that stay at the jargon level without natural user phrasing or synonyms.

Suggestions

Expand the 'what' with one or two more concrete actions (e.g., 'validate the planned action against every applicable Rule and adjust it to comply') to move specificity from 1-2 actions to several.

Add natural trigger phrases to the when-clause, such as 'Use when the user mentions rules, compliance checks, or task constraints, or when planning an action governed by OpenViking Rules', to broaden trigger term coverage.

Narrow the when-clause's scope (e.g., tie it to 'OpenViking Rules' or 'rule-governed tasks' specifically) to reduce overlap risk with generic constraint-checking or policy skills.

DimensionReasoningScore

Specificity

"Retrieve applicable OpenViking Rules" and "check compliance" name the domain and two concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage; it is not 4 because there are only two actions, not several.

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"). It is not 5 because the when-clause is broad and lacks concrete trigger phrases; it is not 3 because the when-clause is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Terms like "OpenViking Rules", "compliance", and "task-specific constraints" are domain-relevant but lean technical and omit the natural phrasing variations or synonyms users would say, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"OpenViking Rules" is a distinctive named system creating a clear niche, but the broad when-clause ("planning an action or response subject to task-specific constraints") could overlap with general policy/constraint skills, so it fits 'mostly distinct; minor overlap risk' rather than the minimal-conflict anchor 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/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.