CtrlK
BlogDocsLog inGet started
Tessl Logo

avoid-ai-writing-router

Use when a request combines AI-writing audit, rewrite, file editing, voice preservation, false-positive interpretation, verification, or when the user invokes Avoid AI Writing without naming a mode.

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/avoid-ai-writing-router/SKILL.md
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.

The body is a lean, well-structured orchestration overview with concrete routing rules, explicit feedback loops, and clean progressive disclosure into real reference files; the main gap is the absence of a single worked envelope example.

DimensionReasoningScore

Conciseness

The body is lean and well-organized, assumes Claude's competence, and never pads with concepts Claude already knows; every section adds routing/orchestration specifics that earn their tokens.

5 / 5

Actionability

Concrete, executable guidance throughout (named target skills, explicit edge semantics, enumerated envelope fields, stop conditions), but no end-to-end worked example showing a complete handoff envelope being constructed.

4 / 5

Workflow Clarity

Multi-stage sequencing is clearly laid out with an explicit verifier-FAIL-to-repair feedback loop, a pass cap, and validation gates ("Never mark an execution field as executed without host evidence"); minor checkpoints remain implicit rather than itemized as a checklist.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references (handoff-contract.md, skill-graph.json, routing-matrix.md, agency-role-lenses.md), each annotated with its purpose in the Authority chain; detailed material is appropriately split into the bundle.

5 / 5

Total

18

/

20

Passed

Description

66%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 provides rich, explicit trigger guidance with good natural keyword coverage and a clear niche, but it omits any statement of what the skill actually does, relying on the name to convey the routing/coordination role.

Suggestions

Add an explicit "what" clause, e.g. "Routes and coordinates the Avoid AI Writing Skills into a bounded workflow" before the "Use when" clause.

Soften jargon triggers like "false-positive interpretation" toward natural phrasing users would actually say, such as "checking whether AI-use claims are justified".

DimensionReasoningScore

Specificity

The description lists several concrete capability areas ("AI-writing audit, rewrite, file editing, voice preservation, false-positive interpretation, verification"), but they are framed as trigger nouns rather than actions the skill itself performs, leaving a minor gap.

4 / 5

Completeness

A strong, explicit "Use when ..." clause answers the "when" thoroughly, but the description never states what the skill does (route/coordinate/orchestrate); that "what" must be inferred from the name.

3 / 5

Trigger Term Quality

Good natural-term coverage ("AI-writing", "rewrite", "file editing", "verification", "Avoid AI Writing") with a few technical terms like "false-positive interpretation" and "voice preservation" that users would say less naturally.

4 / 5

Distinctiveness Conflict Risk

The AI-writing scope and the "invokes Avoid AI Writing without naming a mode" trigger give it a clear niche, but broad terms like "file editing" and "rewrite" carry minor overlap risk with general editing skills.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
conorbronsdon/avoid-ai-writing
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.