CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

false-positive-reviewer

Use when a user asks what AI-writing flags mean, whether detector output proves AI authorship, or wants a careful interpretation of possible false positives, especially for academic, hiring, publication, disciplinary, or other consequential decisions.

Quality

74%

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/false-positive-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, contract-driven instruction skill with concrete routing rules, named reason codes, and clear terminal behavior. Its weaknesses are moderate duplication (the human-reason factor list appears twice, and routing rules are restated) and interpretive steps that point to external skills instead of giving worked examples.

Suggestions

Deduplicate the human-reason factor list: state it once in the evidence lens and have workflow step 3 reference it ('apply the contextual factors listed above') instead of repeating an overlapping list.

Tighten the connection-contract section by merging the repeated router-return rules in 'Terminal behavior' and 'Stop conditions' into a single routing subsection.

Add one short worked example (e.g., a flag, a plausible human cause, and what evidence would reduce uncertainty) to make the interpretive steps of the workflow concrete rather than deferring entirely to ../avoid-ai-writing/SKILL.md.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no concept explanations) and is domain-specific throughout, but the human-reason factors are listed twice — in the evidence lens ('context mode, genre, second-language writing, technical register, editing software') and again in workflow step 3 ('genre, second-language writing, technical register, deadline pressure, editing tools, typography software') — and the connection-contract section has redundant routing restatements. This matches anchor 3 ('could be tightened') rather than 4, where trimming would be minor.

3 / 5

Actionability

As an instruction-only skill the guidance is concrete: specific router reason codes ('fresh_signal_collection_needed'), named envelope fields ('consequential_authorship_claim'), named evidence types ('source history, drafts, revision logs, direct discussion'), and explicit prohibitions ('Do not rewrite detector scores, invent confidence values'). It is below anchor 5 because steps like 'Explain the strongest signals and plausible human reasons' defer the actual interpretive method to the referenced skill rather than giving specific examples.

4 / 5

Workflow Clarity

The six-step workflow is clearly sequenced with decision checkpoints (step 4's router return when an audit is missing), explicit stop conditions, and terminal-behavior rules that prevent loops. It matches anchor 4 rather than 5 because there is no checkpoint validating the interpretation itself and several steps remain at the level of directives without error-recovery detail.

4 / 5

Progressive Disclosure

No bundle files exist, and the body is well-organized into clearly labeled sections; its external file references (../avoid-ai-writing/SKILL.md, ../avoid-ai-writing-router/references/handoff-contract.md, skill-graph.json, agency-role-lenses.md) are one level deep and signaled with explicit paths. This matches anchor 4 — good structure with minor gaps — rather than 5, since the references are cross-skill pointers rather than a deliberate split of this skill's own content, and the 76-line body exceeds the under-50-line simple-skill case.

4 / 5

Total

15

/

20

Passed

Description

70%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, trigger-rich description with excellent 'when' guidance and a well-delineated niche. Its main weakness is that the 'what' is conveyed implicitly through user-request phrasing instead of explicitly stating the skill's actions, which also limits the specificity of capability coverage.

Suggestions

Open with an explicit third-person statement of what the skill does (e.g., 'Interprets AI-writing detector flags and assesses false-positive risk...') before the 'Use when' clause, so the 'what' is stated rather than implied.

Add one or two more concrete capability actions (e.g., 'distinguishes deterministic detector hits from model-only editorial observations', 'recommends probative evidence such as drafts and revision logs') to lift specificity.

Include common user synonyms such as 'AI detector' or 'AI-detection' alongside 'detector output' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain (AI-writing flags, detector output, false positives) and 1-2 concrete actions ('careful interpretation of possible false positives', assessing whether 'detector output proves AI authorship'), but does not enumerate several specific actions. It sits at anchor 3 rather than 4 because the action coverage is not broad, and above 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

The 'when' is explicit and specific ('Use when a user asks what AI-writing flags mean...'), and a 'what' is present but only implied through the request phrasing ('wants a careful interpretation of possible false positives') rather than stated as the skill's own action. This matches anchor 4 where both exist with one less explicit, not 5 (the what is not concretely stated as a skill action) and not 3 (the what is not missing or merely weak).

4 / 5

Trigger Term Quality

Natural phrases users would say are well covered: 'AI-writing flags', 'detector output', 'proves AI authorship', 'false positives', plus decision contexts (academic, hiring, publication, disciplinary). It falls short of anchor 5 because common synonyms like 'AI detector', 'AI-detection', or 'plagiarism' are missing, but exceeds anchor 3 because the included terms are the natural phrasings, not jargon.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche — interpreting detector flags as possible false positives for consequential decisions — with triggers distinct from generic writing or detection skills. Minor overlap risk remains with a general AI-writing-detection/analysis skill, matching anchor 4 rather than 5.

4 / 5

Total

15

/

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/false-positive-reviewer/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.