beautiful-prose

Overview of beautiful-prose skill

beautiful-prose is a writing style contract for prose that should sound exact, forceful, and human. Use the beautiful-prose skill when you need a rewrite or first draft that cuts filler, avoids AI cadence, and keeps the language concrete and clean. It is best for editorial copy, essays, memos, explanations, and closing passages where tone matters as much as meaning.

Who should install beautiful-prose

Install beautiful-prose if you want a reusable instruction for beautiful-prose for Rewriting rather than a one-off prompt. It fits writers, editors, product teams, and agents that need a dependable voice for English prose. It is less useful if your goal is playful branding, casual chat, or highly ornate literary imitation.

What the skill is optimized for

The skill pushes output toward short, exact sentences, strong verbs, and image-bearing language. It also forbids common AI tells: filler, therapy voice, self-justifying hedges, and “not X, but Y” reversals. That makes the beautiful-prose skill useful when you care about trust, rhythm, and readability more than generic helpfulness.

Where it fits and where it does not

This is a style layer, not a subject-matter tutor. It improves how text sounds after you already know what you want to say. If you need structure, facts, citations, or persuasion strategy, pair beautiful-prose with a prompt that supplies those inputs clearly.

How to Use beautiful-prose skill

Install and activate beautiful-prose

Use the repo’s install path, then activate the skill in the request itself. The documented trigger is:

Apply the Beautiful Prose skill.

The beautiful-prose install step is straightforward: add the skill, then include the activation line before your task. The skill should be treated as active style guidance, not as a topic to discuss. In practice, ask for the result only.

Give the model the right input

The strongest beautiful-prose usage prompts define four things: task, audience, tone, and length. For example, instead of “make this better,” say what kind of prose you need and what the output must accomplish.

Strong prompt:
Apply the Beautiful Prose skill. Register: literary_modern. Density: standard. Heat: cool. Rewrite this 300-word memo so it sounds decisive and clean, but not harsh.

Weak prompt:
Make this sound nicer.

The first gives the skill something to shape. The second leaves too much guesswork.

Read these files first

Start with SKILL.md to see the voice contract and forbidden patterns. Then open references/test-cases.md to understand what the skill considers a good match and what failure looks like. If you are deciding whether to adopt it into a workflow, those two files tell you more than a quick skim of the repo tree.

Use the control tags deliberately

The optional tags change output quality in meaningful ways:

• REGISTER sets the rhetorical frame.
• DENSITY controls compression.
• HEAT controls sharpness.
• LENGTH controls scale.

If you are doing beautiful-prose for Rewriting, keep the tags aligned with the source text. A dense legal paragraph usually needs DENSITY: standard or dense; a public-facing memo often works better with HEAT: cool. Do not use every tag by default. Add only the ones that change the result.

beautiful-prose skill FAQ

Is beautiful-prose only for creative writing?

No. The skill is strongest when prose must be clear, forceful, and polished without sounding theatrical. It works for essays, internal memos, explanations, and refined rewrites. It is less suited to playful copy or marketing language that wants overt enthusiasm.

How is it different from an ordinary prompt?

A normal prompt asks for “better writing” and leaves style vague. beautiful-prose gives a repeatable contract: what to avoid, what cadence to aim for, and how to activate it. That usually produces more consistent results across different tasks and agents.

Is the beautiful-prose skill beginner-friendly?

Yes, if you can supply a plain request and a target length. Beginners get the best results by pasting the source text and stating the desired tone in one sentence. The skill is simple to trigger, but it works best when the request is specific.

When should I not use beautiful-prose?

Do not use it when you need a neutral corporate template, a conversational chatbot reply, or a highly technical spec that should stay sterile. If the deliverable depends on legal precision, citations, or structured argumentation, use a domain prompt first and beautiful-prose second.

How to Improve beautiful-prose skill

Give stronger source material

The biggest quality gain comes from better input. Provide the original text, the intended audience, and the exact job the rewrite must do. For example: “Cut this from 500 words to 180, keep the warning intact, and make it sound calm but firm.” That is more useful than asking for style alone.

Watch for the common failure modes

The main failure modes are overcompression, decorative cadence, and accidental softness. If the output feels generic, ask for more concrete nouns and fewer abstractions. If it feels too severe, lower HEAT. If it sounds polished but empty, add facts, examples, or a sharper thesis.

Iterate with line-level guidance

After the first pass, improve the result by naming the problem precisely: “Remove the summary ending,” “make the opening harder,” or “replace abstract claims with direct description.” For beautiful-prose, line-level feedback is more effective than asking for a full rewrite again.

Use the references as a quality checklist

The repository’s test cases show the intended behavior: no em dashes, no reversal clichés, no filler transitions, and no therapy tone. Treat those as editing checks when reviewing output. If you want the beautiful-prose skill to stay useful over time, keep feeding it tasks that reward precision, not generic polish.