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 ./agent-plugins/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 lean behavioral skill: tightly written, well-structured, with a clear sequenced workflow, explicit validation checkpoints, feedback loops, and thorough failure-mode handling in the Boundaries section. The only notable gap is the absence of a worked example of `task_context` construction, which keeps actionability at 4.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and entirely prescriptive — no background on what rules engines are, no padding, every sentence instructs (e.g., "Include material unknowns instead of guessing them", "Read omitted compiled Rule URIs or the saved full result in bounded sections"). This matches anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place'); even the tool-name enumeration serves a concrete disambiguation purpose.

5 / 5

Actionability

For an instruction-only skill the guidance is concrete: it names the tool input (`task_context`), specific Rule fields to check (`applies_when`, `exception`), and the exact delivery flag semantics (`delivery.complete=false`). It misses a 5 because there is no example of how to construct or format `task_context` (string vs. object, illustrative content), leaving a minor gap in the most important executable step — anchor 4 ('Mostly executable guidance; concrete code or commands with minor gaps').

4 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with explicit validation built in: step 3 reviews every returned Rule against `applies_when`/`exception` before step 4 adjusts the plan, step 5 is a re-check feedback loop when context changes, and the Boundaries section adds error-recovery paths (missing tool, incomplete delivery, post-compaction refresh, pause if unretrievable). This matches anchor 5 ('Clear sequence with explicit validation steps; feedback loops for error recovery').

5 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained, and needs no external references; per the rubric's simple-skill guidance this can score 5 with well-organized sections alone. The Goal / Workflow / Boundaries structure is clean and each section is appropriately scoped, with no content that belongs in a separate file.

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 with a clear what/when structure in third person and a distinct domain name. Its main weaknesses are limited action coverage and abstract trigger phrasing that misses the natural terms users would actually say. It reads as a solid but not exemplary trigger description.

Suggestions

Add one or two more concrete actions to the 'what' clause, e.g., 'Retrieve applicable OpenViking Rules, check the planned action against them, and adjust it to comply' — this moves specificity from two generic actions toward comprehensive coverage.

Make the 'when' clause more concrete with natural trigger phrases, e.g., 'Use when planning an action or response that may be subject to task-specific rules, policies, or constraints, or when the user asks to check rule compliance.'

Include common user-facing synonyms (rules, policy, constraints, compliance, allowed/blocked) so the description matches how users naturally phrase these requests.

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 stays below level 4 because coverage is thin — no mention of what compliance checking involves (e.g., adjusting plans, flagging violations) — and above level 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Both parts are present: the 'what' is clear ("Retrieve applicable OpenViking Rules and check compliance") and the 'when' is an explicit "Use when..." clause. It does not reach 5 because the 'when' is generic ("planning an action or response subject to task-specific constraints") rather than concrete trigger phrases, matching anchor 4 ('when' could be more explicit or specific). It is above 3 since the 'when' is explicit, not merely implied.

4 / 5

Trigger Term Quality

Trigger keywords like "Rules", "compliance", and "constraints" are relevant but the phrasing "planning an action or response subject to task-specific constraints" is abstract, missing the natural variations users would say (e.g., "check the rules", "policy", "regulations", "allowed/blocked"). This fits anchor 3 ('Some relevant keywords but missing common variations or synonyms'), not 4, which requires broad natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

"OpenViking Rules" is a clearly named, proprietary-sounding niche with distinct triggers, so it is mostly distinguishable from generic skills (anchor 4). It does not reach 5 because the generic 'check compliance'/'constraints' framing could overlap with other policy- or compliance-checking skills, but it is well above anchor 3's overlap risk since the OpenViking qualifier is unambiguous.

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

agent-plugins/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.