CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-reference-originality

Audit a website or digital experience against its supplied source references for originality and plagiarism risk. Use when Codex must compare current or historical site output with reference pages, capture packs, screenshots, copy, brands, numbers, images, assets, videos, layouts, motion, or code; raise evidence-backed red flags; distinguish common visual grammar from distinctive copying; and propose concrete fixes without making unsupported legal claims.

77

Quality

96%

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 well-engineered instructional skill: lean imperative workflow with numbered phases, explicit stop/escalation checkpoints, executable commands for the deterministic helper and git history searches, and appropriate one-level-deep offloading of the severity rubric to references/audit-rubric.md. The only weakness is mild repetition of the missing-evidence guardrail across sections.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no padding ("Treat the audit as an evidence exercise, not a vibe check"), but the missing-evidence principle is stated three times in different sections ("Do not clear a site after checking only its homepage screenshot", "Do not silently reduce a full-page or motion audit to one cover image", "Never turn missing evidence into a pass"), so it fits the efficient-with-minor-trimmable-instances anchor at 4 rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Fully concrete for an instruction skill: a copy-paste-ready script invocation ("python <skill-dir>/scripts/build_evidence_inventory.py --site <site-root> ..."), exact git commands ("git log -S", "git log --all --name-status"), and enumerated verdict strings ("Clear in checked scope", "Block release") cover the common cases; per the code-vs-instruction scoring note, absence of more code is not penalized.

5 / 5

Workflow Clarity

Six numbered phases in clear sequence with explicit validation checkpoints ("Stop and report an access gap when a promised reference is missing", "Treat its output as leads for human review, not an automatic verdict", "Include a row even when a high-risk category could not be checked") and a final completion checklist, matching the anchor with explicit validation steps and checklists; not the 4 anchor since checkpoints are not merely implied.

5 / 5

Progressive Disclosure

The body is the workflow overview, with one clearly signaled one-level-deep reference ("Read [references/audit-rubric.md](references/audit-rubric.md) before judging findings" — verified to exist and well-organized with its own contents list) and the helper script in scripts/build_evidence_inventory.py invoked via a full command; content is appropriately split with easy navigation, fitting the 5 anchor rather than the minor-organization-gaps anchor at 4.

5 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: third-person voice, explicit what-and-when structure, comprehensive natural trigger terms with synonyms, and a distinct niche. It clearly states the audit's scope boundary ("without making unsupported legal claims") as well.

DimensionReasoningScore

Specificity

Quotes multiple concrete actions: "Audit a website or digital experience against its supplied source references", "raise evidence-backed red flags", "distinguish common visual grammar from distinctive copying", and "propose concrete fixes" — a comprehensive set of specific capabilities, matching the anchor for multiple specific concrete actions with comprehensive coverage rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Explicitly answers both: what ("Audit a website or digital experience against its supplied source references for originality and plagiarism risk") and when ("Use when Codex must compare current or historical site output with reference pages..."), with concrete trigger phrases; not the 4 anchor since 'when' is fully explicit.

5 / 5

Trigger Term Quality

Natural trigger terms with synonyms are comprehensively covered: "website", "originality and plagiarism", "site output", "screenshots", "copy, brands, numbers, images, assets, videos, layouts, motion, or code" — matching the comprehensive-synonyms anchor rather than the few-natural-terms-missing anchor at 4.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — originality/plagiarism auditing against supplied source references — with distinct triggers ("capture packs", "originality matrices", "plagiarism risk") that minimal-conflict risk with other skills; not the 4 anchor since there is no meaningful overlap with closely related skills.

5 / 5

Total

20

/

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
MengTo/Skills
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.