CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

natural-writing

To rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.

Quality

73%

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 ./instructions/r2/core/skills/natural-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 skill body is efficient and actionable, encoding skill-specific rules with concrete examples, an input template, and a validation checklist rather than generic writing advice. Its main gaps are minor: a couple of vague filler bullets and an implicit rather than explicitly ordered workflow.

DimensionReasoningScore

Conciseness

The body is lean, rule-dense bullet lists that assume Claude's competence and never explain concepts Claude already knows; only minor redundancy exists (e.g. 'Be direct and concise — cut extra words' overlaps 'Cut the fluff — remove extra adjectives and filler words').

4 / 5

Actionability

As an instruction-only skill, the guidance is concrete and executable — named banned phrases ('dive into,' 'unleash,' 'game-changing'), explicit punctuation rules, and a fill-in input template — though a few best-practice bullets ('Hook user with interesting ideas', 'Ensure no gaps, ambiguity, misunderstanding, vague constructs, conflicts, or inconsistencies remain') are vague filler.

4 / 5

Workflow Clarity

The implied sequence (confirm intent via the template, rewrite, validate against the checklist, obtain user approval) is supported by an explicit validation_checklist with checkpoints like 'Read the output aloud' and the user-approval gate; the sequence is never presented as ordered steps, keeping it just below the top anchor.

4 / 5

Progressive Disclosure

The body is well organized into clear sections with all content appropriately inline at this size and no bundle files (references/, scripts/, assets/ are absent); it slightly exceeds the 50-line simple-skill threshold and could split the banned-phrase lists into a reference file, so it fits 'good structure; minor organization gaps'.

4 / 5

Total

16

/

20

Passed

Description

61%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 communicates a clear and fairly distinctive capability with naturally worded trigger terms, but it omits any 'use when' trigger guidance and does not enumerate multiple concrete actions, leaving both completeness and specificity at mid-level.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to humanize, de-AI, or naturalize text, or complains it sounds robotic or like ChatGPT wrote it.'

List a couple more concrete actions to lift specificity, such as 'rewrites emails, blog posts, and docs; strips AI giveaway phrases, hype, and robotic phrasing'.

Include common user synonyms and phrasings (humanize, make it sound like me, less robotic, remove the AI tone) to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("rewrite text") with a concrete outcome ("clear, natural, honest human tone") and specific exclusions ("no AI slop, hype, or robotic phrasing"), but lists only one main action rather than several, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

The 'what' is clear (rewrite text into a natural human tone without AI markers), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric explicitly caps at 3.

3 / 5

Trigger Term Quality

Natural phrases like "AI slop", "robotic phrasing", "hype", and "human tone" are terms users genuinely say, but common variations such as "humanize", "make it sound like me", or "de-AI" are missing, fitting the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The anti-AI-slop rewriting niche carries distinct markers (specific banned-phrase framing), with only minor overlap risk against general writing and editing skills.

4 / 5

Total

14

/

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

griddynamics/rosetta

Path

instructions/r2/core/skills/natural-writing/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.