CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

preservation-verifier

Use when the user provides an original and rewritten version, asks whether a rewrite preserved protected content, or wants a deterministic check for code, frontmatter, quotes, tables, links, paths, numbers, headings, and residual AI-pattern regressions.

Quality

91%

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

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.

A tightly engineered verification skill: the deterministic path is executable and matches the real bundle, result handling and repair routing are unambiguous, and the bounded repair loop with explicit stop conditions is exemplary workflow design. The only weakness is repetition of the model-only/don't-overclaim rule across several sections, which could be consolidated.

DimensionReasoningScore

Conciseness

The body is dense and procedural with no concept explanations or fluff, but the model-only/don't-overclaim rule is stated three times ("Never claim it ran unless the current host executed it", "Report this review as model-only rather than claiming the deterministic validator performed it", "Report that portion separately as model-only semantic review") and the repair-loop bound is repeated across three sections, so some trimming is possible. Not 3 because there is no padded explanation of things Claude already knows; not 5 because the duplicated disclaimers and run-on paragraphs (e.g. the 'Use the explicit warn residual policy...' paragraph) exceed 'every token earns its place'.

4 / 5

Actionability

Gives fully executable, verified guidance: `node scripts/validate.js --residual-policy warn before.md after.md` matches the actual CLI, and `const { validate } = require("./scripts/validate.js")` matches the actual module export; both were confirmed against the bundled script. Result statuses (PASS/REVIEW/FAIL), envelope fields, and the repair-owner routing table ('returned text -> voice-preserving-rewriter', 'named file -> file-edit-in-place') are concrete and unambiguous, matching the copy-paste-ready anchor.

5 / 5

Workflow Clarity

The full verification loop is explicitly sequenced with validation checkpoints and a hard feedback-loop bound: require both versions (return to router if missing), run the deterministic validator, apply a separate semantic review, emit a status, route REPAIR only 'while the shared editing budget has room', verify once more, then 'Stop and report on a second verification failure. Do not start another repair loop.' This matches the anchor for clear sequence with explicit validation steps, feedback loops for error recovery, and checklists (PASS/REVIEW/FAIL criteria are each enumerated).

5 / 5

Progressive Disclosure

SKILL.md is a ~106-line procedural overview while 194KB of implementation (scripts/validate.js at 574 lines, scripts/patterns.js at 3,762 lines) is correctly externalized and referenced with executable usage; the heavy patterns data never leaks into the overview. Cross-skill references (`../avoid-ai-writing/SKILL.md`, `../avoid-ai-writing-router/references/handoff-contract.md`, `agency-role-lenses.md`, `skill-graph.json`) are clearly signaled and one level deep, matching the well-signaled one-level-deep-references anchor.

5 / 5

Total

19

/

20

Passed

Description

87%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 with an explicit 'Use when' trigger covering three concrete scenarios, a precise enumeration of the protected content types, and a distinctive niche (preservation verification plus residual AI-pattern regression checks). The only room for improvement is broader synonym coverage for trigger phrasing.

DimensionReasoningScore

Specificity

Enumerates concrete, verifiable objects — "deterministic check for code, frontmatter, quotes, tables, links, paths, numbers, headings, and residual AI-pattern regressions" — giving comprehensive coverage of what is checked. Not 3 because coverage is comprehensive rather than partial; not 5 because the action space is essentially one verification capability rather than multiple distinct actions (the anchor-5 pattern of several distinct verbs like extract/fill/merge/convert).

4 / 5

Completeness

Explicitly answers both parts: the what is a "deterministic check for code, frontmatter, quotes, tables, links, paths, numbers, headings, and residual AI-pattern regressions", and the when is an explicit "Use when" clause with three concrete trigger conditions (user supplies original and rewritten versions, asks whether protected content survived, wants a deterministic check). This matches the anchor for clearly and explicitly answering both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say in this situation: "provides an original and rewritten version", "asks whether a rewrite preserved protected content", plus the concrete content-type keywords. Not 5 because common synonyms and phrasings are missing — e.g. "before/after", "kept", "unchanged", "edit" — which the comprehensive-synonyms anchor expects; not 3 because the included terms are the natural ones for this task, not jargon.

4 / 5

Distinctiveness Conflict Risk

"asks whether a rewrite preserved protected content" and "residual AI-pattern regressions" carve out a clear niche with distinct triggers that no generic rewriting, diffing, or editing skill would claim. Not 4 because the overlap risk with generic compare/diff requests is minimal — the description is anchored specifically to rewrite preservation, not to file comparison in general.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

conorbronsdon/avoid-ai-writing

Path

skills/preservation-verifier/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.