CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

domain-docs

Locate and maintain OpenMeter's package-level domain documentation. Use for code reviews, planning, implementation, debugging, or explanations that depend on product behavior, domain ownership, or cross-domain contracts, and when creating or editing domain READMEs. Do not use for mechanical changes with no domain behavior.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, lean, and actionable with concrete examples and a clear revision workflow, appropriate for an instruction-only skill. The main gap is implicit rather than explicit validation checkpoints in the workflow.

Suggestions

Add an explicit validation/feedback step to the 'Create or revise a domain README' workflow (e.g., 'Re-read the README against the changed code and confirm each assertion still holds; if not, fix and re-check') to make checkpoints concrete.

Tighten the 'Examples' block and its disclaimer — fold the 'not a registry' caveat into a single line so it earns its tokens more directly.

Consider whether the 'Choose a home' placement rules could be condensed into a tighter decision table to reduce inlined content.

DimensionReasoningScore

Conciseness

Lean and efficient prose that assumes competence; no padding about what READMEs or domain docs are. Not a 5 because a few explanatory passages (e.g., the ownership reasoning and the examples-with-disclaimer) could be trimmed further.

4 / 5

Actionability

Provides concrete guidance including specific file paths and a 6-step revision checklist with concrete actions. Not a 5 because some guidance stays at the principle level rather than fully executable steps, though the absence of code is appropriate for this instruction-only skill.

4 / 5

Workflow Clarity

The 'Create or revise a domain README' section gives a clear sequenced 6-step process. Not a 5 because validation checkpoints are implicit ('Review the result' in step 6) rather than explicit verify-and-fix loops; not capped at 3 since the skill is not destructive or batch-oriented.

4 / 5

Progressive Disclosure

Self-contained, well-organized into clear section headers with no nested references and appropriate placement. Not a 5 because at ~100 lines it is longer than the simple-skill exception allows, and it carries inlined content that maps to a single file structure.

4 / 5

Total

16

/

20

Passed

Description

92%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 specific, complete, and well-scoped, clearly stating both what the skill does and when to use it alongside an explicit negative boundary. Trigger term coverage is strong but not exhaustive of synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Locate and maintain', 'code reviews, planning, implementation, debugging, explanations', 'creating or editing domain READMEs') with comprehensive coverage of the skill's scope.

5 / 5

Completeness

Explicitly answers 'what' ('Locate and maintain OpenMeter's package-level domain documentation') and 'when' ('Use for... when creating or editing domain READMEs') with concrete trigger phrases and a negative boundary.

5 / 5

Trigger Term Quality

Good coverage of natural trigger phrases ('code reviews, planning, implementation, debugging, explanations', 'domain READMEs'), but a few common synonyms (e.g., 'docs', 'documentation') are lightly represented. Not a 5 because it stops short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped to OpenMeter package-level domain READMEs with distinct triggers and an explicit anti-trigger ('Do not use for mechanical changes'), giving it a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openmeterio/openmeter

Path

.agents/skills/domain-docs/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.