CtrlK
BlogDocsLog inGet started
Tessl Logo

beautiful-prose

A hard-edged writing style contract for timeless, forceful English prose without modern AI tics. Use when users ask for prose or rewrites that must be clean, exact, concrete, and free of AI cadence, filler, or therapeutic tone.

69

Quality

85%

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

The canonical home for this skill is beautiful-prose in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 well-structured, highly actionable style contract with concrete rules, examples, and a validation lint checklist. Its main weaknesses are minor redundancy in the opening summary and a dangling reference to a test-cases file that is not bundled.

Suggestions

Trim the 'What this skill does' summary so it does not restate the prohibition lists that follow, reducing redundancy.

Either bundle `references/test-cases.md` so the closing reference resolves, or remove the dangling 'See references/test-cases.md' line.

DimensionReasoningScore

Conciseness

Mostly lean rule-based content that assumes Claude's competence, with minor redundancy between the 'What this skill does' summary and the expanded prohibitions that could be trimmed.

4 / 5

Actionability

Concrete do/don't lists, specific positive constraints (prefer declarative sentences, strong verbs over adverbs), named registers with characteristics, a manual lint checklist, and bad/good examples make the guidance fully actionable for an instruction-only skill.

5 / 5

Workflow Clarity

The single action is unambiguous with a clear sequence (activate via prepend line, optional control tags, produce prose, run lint checklist, fix and re-check), and the lint checklist provides an explicit validation checkpoint with a fail-the-output feedback loop.

5 / 5

Progressive Disclosure

Well-organized sections with appropriate inline core rules and one clearly signaled one-level reference; minor gap is that the referenced `references/test-cases.md` is not present in the bundle.

4 / 5

Total

18

/

20

Passed

Description

82%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 is strong: it clearly states what the skill is and when to use it, with concrete trigger phrases and a distinct, low-conflict niche. Minor weakness is that discrete actions are implied rather than enumerated, appropriate for a style contract but not maximally specific.

DimensionReasoningScore

Specificity

Names the domain (forceful English prose) and the core action (producing/rewriting prose that is clean, exact, concrete) but does not enumerate multiple discrete actions, fitting the single-purpose style-contract nature.

3 / 5

Completeness

Explicitly states both what ('A hard-edged writing style contract for timeless, forceful English prose without modern AI tics') and when ('Use when users ask for prose or rewrites that must be clean, exact, concrete...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms 'prose', 'rewrites', 'clean', 'filler', 'AI cadence', 'therapeutic tone' give good coverage, though common variations like 'less robotic/AI-sounding' or 'punchy' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (anti-AI-cadence prose style) with distinct triggers ('AI cadence', 'therapeutic tone', 'filler') and minimal overlap risk with the mostly-technical skill ecosystem.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.