CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

text-human

Humanizes code, docs, commits, articles, reddit/chat, javadoc -- strips AI artifacts, fixes unicode, fits register. Use when asked to humanize a file, commit or pasted text. Triggers: humanize, ai artifacts, unicode fix, article, reddit, javadoc, очеловечь.

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 ./.codex/plugins/brewtools/skills/text-human/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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.

Operationally rich with real commands, templates, and a well-sequenced gated workflow for a destructive in-place operation, but held back by duplicated flow-resolution logic and a bundle whose referenced pattern and flow files are entirely missing, leaving the actual humanization rules inaccessible.

Suggestions

Ship the referenced files (references/ai-patterns.md, references/human-patterns.md, references/flows/*.md) or inline their essential rules, since the two-pass strip/inject model is not executable without them.

Deduplicate the flow-resolution and user-gate logic: state it once in Phase 0 and have the Prompt contract section reference it instead of restating it.

Merge the two overlapping intro sections ('# Humanize text' and '# Text Humanizer') into one, and add a post-edit verification step (e.g., reviewing the diff for preserved meaning) to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

The flow-resolution and user-gate logic is stated twice (Prompt contract items 1/3 vs. "Argument parsing" step 4 and "Detection signals"), there are two overlapping intro sections ("# Humanize text" vs. "# Text Humanizer"), and the "Complete native workflow" paragraph is dense enough to need tightening. Everything is operational rather than padded, so it sits above 2 but below the "minor instances" bar for 4.

3 / 5

Actionability

Concrete and mostly executable: the exact command `git status --porcelain -- '<resolved path>'`, copy-paste PLAN/spawn-brief/report templates, a full flow table, and eight example invocations. The gap keeping it from 5 is that the core editing rules live in `@reference/ai-patterns.md` and `@reference/human-patterns.md`, which are not present in the bundle, and "Codex collaboration" assumes unspecified tooling.

4 / 5

Workflow Clarity

Clear Phase 0 -> 0.5 -> 1 -> Output sequence with an explicit destructive-operation precondition gate ("Empty -> proceed", "Unanswered -> only the clean ones; none clean -> stop, no edits") and an error-handling table ("never count unverified work done"), so the destructive/batch validation cap does not apply. Missing a post-edit verification loop, so it does not reach 5.

4 / 5

Progressive Disclosure

The body references `@reference/ai-patterns.md`, `@reference/human-patterns.md`, and five `@reference/flows/*.md` files, but the bundle contains no references/ directory at all -- every referenced path is dangling, so the one-level-deep design leads nowhere. SKILL.md itself is well-sectioned (not a monolithic wall), which keeps it above 1.

2 / 5

Total

13

/

20

Passed

Description

88%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 description: concrete actions, an explicit use-when clause, and a multilingual trigger list. The only weaknesses are a few missing natural synonyms and two overly broad trigger terms that create minor overlap risk with general editing skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("strips AI artifacts, fixes unicode, fits register") across a full domain list ("code, docs, commits, articles, reddit/chat, javadoc"), giving comprehensive coverage of the skill's capabilities with no real gaps.

5 / 5

Completeness

Explicitly answers both: what ("Humanizes code, docs, commits, articles, reddit/chat, javadoc -- strips AI artifacts, fixes unicode, fits register") and when ("Use when asked to humanize a file, commit or pasted text") with a concrete trigger list.

5 / 5

Trigger Term Quality

"Triggers: humanize, ai artifacts, unicode fix, article, reddit, javadoc, очеловечь" gives good natural keyword coverage including a Russian synonym, but misses common user phrasings like "make it sound human", "natural", or "less robotic".

4 / 5

Distinctiveness Conflict Risk

"humanize", "ai artifacts", and "очеловечь" form a clear niche with minimal conflict risk, but bare trigger terms "article" and "reddit" are broad and could fire for general writing or editing requests.

4 / 5

Total

18

/

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

kochetkov-ma/claude-brewcode

Path

.codex/plugins/brewtools/skills/text-human/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.