CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jev-assert

Asserts a UI expectation semantically by asking TypeSafe's Jev model whether an outcome holds in a page's captured text state, mapped to a verify-behavior receipt. Use when an exact locator or string match is brittle; triggers on "assert semantically", "does the page show", "semantic UI assertion", "/jev-assert".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/quality/jev-assert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, with a copy-paste-ready script invocation, explicit failure semantics, and a gated three-step workflow. Its weaknesses are repetition of the same safety rules across four sections, meta authoring checklists that consume runtime context, and a thin-index design whose referenced rule and eval files are not present in the bundle.

Suggestions

Ship the referenced files (rules/provenance.md, rules/state-extraction.md, rules/receipt-mapping.md, evals/evals.json, evals/triggers.jsonl) in the bundle or inline their essentials — the thin-index design currently points at paths that do not exist alongside SKILL.md.

State each invariant once and cross-reference it: the text-only/no-screenshot rule and the unobtainable-never-guess rule each appear 3-4 times across the workflow table, "Why Jev", Core Principles, and Anti-patterns.

Trim or relocate the Evaluation and Definition of Done sections — they are skill-authoring checklists, not runtime guidance, and their tokens compete with operational context.

DimensionReasoningScore

Conciseness

Mostly efficient (table-form workflow, terse receipt example), but the text-only/no-screenshot rule is stated four times and the unobtainable-never-guess rule three times across the Workflow gates, "Why Jev", Core Principles, and Anti-patterns; the Evaluation and Definition of Done sections are authoring-time meta content rather than runtime guidance. Fits "could be tightened" better than "minor instances".

3 / 5

Actionability

Fully executable guidance: the committed `node ${CLAUDE_SKILL_DIR}/scripts/jev-call.mjs` call with a concrete expectation example, --state-file and stdin paths, threshold flags, TYPESAFE_API_KEY contract, explicit failure semantics, a --self-test command, and the exact receipt output format. The script ships in the bundle and covers the common case.

5 / 5

Workflow Clarity

Three sequenced steps each with an explicit gate (provenance guard, text-state capture, mapping), plus offline self-test validation — clear checkpoints. Not 5 because there is no explicit recovery loop: the provenance guard "is refused" but the body never says what the caller should do next.

4 / 5

Progressive Disclosure

Structure and signaling are excellent ("This SKILL.md is a thin index", one-level-deep links in a table), but scored against the actual bundle the referenced rules/provenance.md, rules/state-extraction.md, rules/receipt-mapping.md, and evals/* files are absent — only scripts/jev-call.mjs ships. The thin-index navigation breaks at every rule-file link, so the disclosure promise is not fulfilled in this bundle.

3 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description: it concretely specifies the assertion pipeline (Jev model over captured text state → verify-behavior receipt) and gives an explicit 'Use when' clause with natural trigger phrases. The only weaknesses are a slightly narrow action vocabulary and one broad trigger phrase with minor overlap risk.

DimensionReasoningScore

Specificity

"Asserts a UI expectation semantically by asking TypeSafe's Jev model whether an outcome holds in a page's captured text state, mapped to a verify-behavior receipt" explicitly names the input, mechanism, and output. Not 5 because it describes a single capability rather than multiple concrete actions; above 3 because the full pipeline is specified rather than just 1-2 generic actions.

4 / 5

Completeness

Explicitly answers both: what ("Asserts a UI expectation semantically by asking TypeSafe's Jev model… mapped to a verify-behavior receipt") and when ("Use when an exact locator or string match is brittle; triggers on…") with concrete trigger phrases — the exact shape of the anchor-5 example.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present: "assert semantically", "does the page show", "semantic UI assertion", "/jev-assert", plus the condition "Use when an exact locator or string match is brittle". Not 5 because common synonyms (e.g., "does the page say", "semantic check") are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (semantic UI assertion via the Jev model) with distinct trigger terms, distinguishing it from generic verification skills. Not 5 because "does the page show" is a broad natural phrase that could plausibly fire for non-semantic page-check requests.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 missing, 5 suspicious

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/quality/jev-assert/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.