CtrlK
BlogDocsLog inGet started
Tessl Logo

de-ai-ify

Remove AI-generated jargon and restore human voice to text. Use when the user asks to de-AI-ify, humanize, remove AI tone, or make text sound less machine-generated.

66

Quality

78%

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 ./.agents/skills/de-ai-ify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, simple skill body that clearly catalogues patterns to remove and add, with a useful before/after example. It is weakened by first-person filler and an under-specified, validation-free transformation workflow.

Suggestions

Cut the first-person filler ("I'll create a de-AI-ified version..." and "Let me de-AI-ify your text!") and the redundant opening line; start directly with the substantive guidance to improve conciseness.

Replace the abstract "Apply de-AI-ification" step with a concrete procedure: scan for each pattern category, apply the listed replacements, then re-read the result to confirm no robotic parallelism or three-item lists remain.

Add a verification checkpoint to the workflow, e.g. re-read the edited file and confirm removed patterns no longer appear before reporting the change log.

DimensionReasoningScore

Conciseness

Mostly efficient with lean lists, but first-person filler ("I'll create a de-AI-ified version...", "Let me de-AI-ify your text!") and the opening restatement of the title add tokens without earning their place.

2 / 3

Actionability

Provides concrete examples of patterns to remove and a clear before/after, but the core transformation step ("Apply de-AI-ification") is abstract with no concrete procedure for how to decide and apply edits.

2 / 3

Workflow Clarity

Steps are listed (read, create copy with suffix, apply, change log) but the sequence lacks any validation checkpoint and the actual edit step is not broken into a verifiable procedure.

2 / 3

Progressive Disclosure

A simple single-purpose skill with well-organized sections and no bundle files needed; structure is clear and navigable per the simple-skills scoring note.

3 / 3

Total

9

/

12

Passed

Description

100%

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 concise, third-person description that names concrete actions, gives natural trigger terms, and explicitly pairs capability with when-to-use guidance. No weaknesses to address.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Remove AI-generated jargon", "restore human voice to text") rather than vague language, matching the anchor for listing specific concrete actions.

3 / 3

Completeness

Explicitly states both what it does and when to use it via a "Use when the user asks to..." trigger clause.

3 / 3

Trigger Term Quality

Covers natural user phrasings ("de-AI-ify", "humanize", "remove AI tone", "make text sound less machine-generated") that users would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a specific niche (AI-tone removal) with distinct, narrow triggers unlikely to collide with other skills.

3 / 3

Total

12

/

12

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
heyitsnoah/claudesidian
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.