Agent skill

Prose Style

by jwynia in jwynia/agent-skills

Diagnose sentence-level issues after structure is solid. An agent skill from jwynia/agent-skills.

MITAuto-check passed

Install Prose Style

skills CLI
$ npx skills add jwynia/agent-skills --skill prose-style -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills prose-style --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/craft/prose-style .claude/skills/prose-style && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prose-style
GitHub stars
170
Token cost
~4k tokens
SKILL.md length
1,968 words
Files
3 (incl. scripts)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Diagnose sentence-level issues after structure is solid. An agent skill from jwynia/agent-skills.

  • Works in 4 steps: Identify the Problem Type → Apply the Read-Aloud Test → Check Multiple Levels → …
  • Prose feels flat
  • SKILL.md covers Core Principle, The Prose States, The Strunk & White Principles and Word Choice Reference, plus 4 more sections
  • Runs TypeScript scripts from its folder; calls deno

What it does

Prose Style is an agent skill from jwynia/agent-skills. Diagnose sentence-level issues after structure is solid. Use when prose feels flat, sentences are monotonous, word choices are generic, or voice is inconsistent.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/prose-check.ts` and `scripts/rhythm.ts`).

The licence is MIT.

When your agent uses it

  • Prose feels flat
  • Sentences are monotonous
  • Word choices are generic
  • Voice is inconsistent

Example prompts

  • “/prose-style”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Identify the Problem Type
  2. Apply the Read-Aloud Test
  3. Check Multiple Levels
  4. Recommend Interventions

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • deno

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prose Style loads about 4k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 1,968 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,968 words, ~3,994 tokens.

Download SKILL.mdSave it as .claude/skills/prose-style/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
prose-style
description
Diagnose sentence-level issues after structure is solid. Use when prose feels flat, sentences are monotonous, word choices are generic, or voice is inconsistent.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.type
diagnostic
metadata.mode
diagnostic+assistive
metadata.domain
fiction

Prose Style: Diagnostic Skill

You diagnose sentence-level craft problems in fiction. Your role is to identify why prose fails to serve the story and guide writers toward vigorous, intentional writing.

Core Principle

Style is not decoration; style is content.

The way something is written shapes what it means. As Truman Capote observed:

"I believe a story can be wrecked by a faulty rhythm in a sentence—especially if it occurs toward the end—or a mistake in paragraphing, even punctuation."

Prose style operates at multiple levels simultaneously:

  • Word choice (diction)
  • Sentence structure (syntax)
  • Paragraph flow (rhythm)
  • Voice (the writer's distinctive presence)

The fundamental principle: Vigorous writing is concise. Every word earns its place.


The Prose States

State P1: Flat Prose

Symptoms: Prose is functional but unmemorable. Sentences deliver information but have no rhythm or distinction. Writing doesn't enhance the story—it merely delivers it.

Key Questions:

  • Is there sentence variety (length, structure)?
  • Are word choices precise or generic?
  • Is there any rhythm or is it monotonous?
  • Does the prose have any distinctive quality?

Diagnostic Checklist:

  • Sentences vary in length (short, medium, long)
  • Sentences vary in structure (simple, compound, complex)
  • Word choices are specific, not generic
  • Prose has identifiable rhythm

Interventions:

  • Read aloud to hear the rhythm (or lack thereof)
  • Mark sentence lengths—look for variation
  • Replace vague words with specific ones
  • Vary sentence openings (don't always start with subject-verb)

State P2: Unclear Writing

Symptoms: Reader has to reread sentences. Meaning is obscured by abstraction or missing context. Pronouns lack clear antecedents. The curse of knowledge operates.

Key Questions:

  • Are there too many abstractions?
  • Is assumed knowledge preventing clarity?
  • Are pronoun antecedents clear?
  • Is logic visible or compressed?

Diagnostic Checklist:

  • Concrete language outweighs abstract
  • Context provided for specialized terms
  • Every pronoun has obvious referent
  • Logical steps are visible, not compressed

Interventions:

  • Substitute concrete for abstract
  • Add context where curse of knowledge operates
  • Check every pronoun has an obvious referent
  • Expand compressed thinking—show the steps

State P3: Overwrought Prose (Purple Prose)

Symptoms: Style overwhelms substance. Excessive adjectives and adverbs. Metaphors obscure rather than illuminate. Writing calls attention to itself rather than the story.

Key Questions:

  • Are there adjective/adverb stacks?
  • Do metaphors illuminate or obscure?
  • Is style calling attention to itself?
  • Does richness serve the work or overwhelm it?

Diagnostic Checklist:

  • No more than 1-2 adjectives per noun
  • Adverbs used sparingly, intentionally
  • Metaphors clarify rather than confuse
  • Prose serves story, not writer's ego

Signs of Purple Prose:

  • Adjective stacking: "beautiful, gorgeous, stunning sunset"
  • Adverb abuse: "ran quickly, desperately, frantically"
  • Overwrought metaphor: comparisons that obscure
  • Mismatched register: elevated language for mundane content

Interventions:

  • Cut modifiers ruthlessly
  • Choose one right adjective, not three approximations
  • Replace overwrought metaphors with simpler images
  • Let nouns and verbs do the work

State P4: Monotonous Prose

Symptoms: Every sentence sounds the same. Every paragraph looks the same. Sentences start the same way. Reading feels like a drone.

Key Questions:

  • Are sentences all similar lengths?
  • Are paragraphs all similar lengths?
  • Do sentences start the same way?
  • Is there any variation in rhythm?

Diagnostic Checklist:

  • Sentence lengths vary significantly
  • Paragraph lengths vary (including singles for punch)
  • Sentence openings vary (not all subject-verb)
  • Rhythm shifts between sections

Interventions:

  • Consciously vary sentence length
  • Use short sentences for punch, long for flow
  • Vary paragraph length for rhythm
  • Change sentence structure (simple, compound, complex)
  • Vary sentence openings (modifiers, dependent clauses)

State P5: Passive Voice Overuse

Symptoms: Prose feels indirect, weak. Agents are routinely hidden when they matter. Energy drains from sentences. Action feels distant.

Key Questions:

  • Are agents hidden when they matter?
  • Does prose feel indirect?
  • Is passive used intentionally or by default?
  • Would active voice add energy?

When Passive IS Appropriate:

  • Agent is unimportant ("The building was constructed in 1890")
  • Agent is unknown ("Mistakes were made")
  • Deliberately hiding the actor
  • Emphasis at sentence end ("The patient was murdered by his own doctor!")
  • Focus is on receiver ("Kennedy was assassinated")

Diagnostic Checklist:

  • Passive voice used intentionally, not by default
  • Important agents named, not hidden
  • Active voice predominates in action sequences
  • Passive serves emphasis where used

Interventions:

  • Default to active voice
  • Check each passive: is it intentional?
  • If passive, does it serve emphasis, mystery, or receiver-focus?
  • Convert default passives to active

State P6: Inconsistent Voice

Symptoms: Diction level shifts randomly. Sentence structure varies wildly without purpose. Different sections feel like different writers. Narrator doesn't sound like one person.

Key Questions:

  • Does diction level shift without purpose?
  • Does sentence structure vary wildly?
  • Do different sections feel consistent?
  • Is there a baseline voice to return to?

Levels of Diction:

LevelDescriptionExample
High/FormalElevated, literary"The conflagration consumed the edifice"
Middle/StandardEducated but accessible"The fire destroyed the building"
Low/InformalConversational"The place burned down"

Diagnostic Checklist:

  • Diction level consistent for narrator
  • Shifts in voice are intentional, not accidental
  • Tone consistent across manuscript
  • Relationship to reader (distance/intimacy) maintained

Interventions:

  • Establish baseline voice (diction level, rhythm patterns)
  • Vary from baseline intentionally for effect
  • Ensure shifts are character/scene-driven, not author inconsistency
  • Audit for intrusive author voice in close POV

The Strunk & White Principles

From The Elements of Style, foundational guidance:

  1. Use the active voice (generally)
  2. Put statements in positive form
  3. Use definite, specific, concrete language
  4. Omit needless words
  5. Avoid a succession of loose sentences
  6. Express coordinate ideas in similar form (parallelism)
  7. Keep related words together
  8. Place the emphatic words at the end

Caveat: These are principles, not laws. The goal is intentional choice, not mechanical obedience.


Word Choice Reference

Concrete vs. Abstract

Abstract: happiness, freedom, love, time Concrete: laughter, unlocked door, kiss, clock

The issue isn't abstraction itself—it's vague abstraction that avoids precision.

  • Weak: "happiness"
  • Strong: "the particular happiness of a child with a new dog"
Common Word Choice Traps
TrapDescriptionFix
Thesaurus abuseObscure synonyms for common wordsUse the right word, even if repeated
Elegant variationDifferent words for same thingRepetition is fine; clarity matters
Jargon creepTechnical language where plain worksUse simplest word that fits

Sentence Structure Reference

The Punch Position

The end of a sentence carries the most weight.

  • Weak: "It was a dark night, I remember"
  • Strong: "I remember: it was a dark night"
Parallelism

Parallel structure creates rhythm and emphasis:

  • "Veni, vidi, vici"
  • "It was the best of times, it was the worst of times"

Faulty parallelism:

  • Wrong: "She likes reading, to swim, and runs"
  • Right: "She likes reading, swimming, and running"
Sentence Variety Guide
LengthEffectUse For
ShortPunch, urgencyEmphasis, action, revelation
MediumClarity, flowDefault narrative
LongDevelopment, immersionBuilding complexity, flowing prose

The Read-Aloud Test

The most reliable prose diagnostic: read it aloud.

What the ear catches that the eye misses:

  • Awkward rhythm
  • Repeated words
  • Sentences that don't breathe
  • Missing transitions
  • Overwrought passages

"From the point of view of ear, Virginia Woolf never wrote a bad sentence." — Truman Capote

Rule: If you stumble reading it, revise it.


Anti-Patterns

The Thesaurus Abuser

Pattern: Replacing common words with obscure synonyms for variety. Problem: Sacrifices clarity for artificial variety. Fix: Use the right word, even if you used it recently.

The Adjective Hoarder

Pattern: Stacking modifiers hoping something sticks. Problem: Weakens rather than strengthens description. Fix: Choose one right adjective. Or none—let the noun work.

Show full SKILL.md (779 more words)Show less
The Passive Defaulter

Pattern: Writing in passive voice without intention. Problem: Prose loses energy and directness. Fix: Default to active. Use passive deliberately.

The Monotone

Pattern: Every sentence same length and structure. Problem: Creates droning effect; reader disengages. Fix: Vary intentionally. Short sentences punch. Long sentences flow.

The Purple Writer

Pattern: Style overwhelming substance. Problem: Reader sees the writing, not the story. Fix: Serve the story. Kill your darlings if they distract.

The Rule Slave

Pattern: Following every prescription mechanically. Problem: Loses the art in favor of rules. Fix: Understand principles, not just rules. Break rules intentionally.


Diagnostic Process

When a writer presents prose problems:

1. Identify the Problem Type
  • Does it feel flat/boring? → P1 (Flat Prose)
  • Is it hard to follow? → P2 (Unclear Writing)
  • Does it feel overwritten? → P3 (Overwrought)
  • Does everything sound the same? → P4 (Monotonous)
  • Does it feel weak/indirect? → P5 (Passive Overuse)
  • Does the voice shift randomly? → P6 (Inconsistent Voice)
2. Apply the Read-Aloud Test

Have writer read problematic passages aloud. What do they stumble on?

3. Check Multiple Levels
  • Word level: precision, redundancy
  • Sentence level: variety, clarity, parallelism
  • Paragraph level: length, flow, transitions
  • Voice level: consistency, diction, tone
4. Recommend Interventions

Based on identified state, provide specific fixes.


Integration with story-sense

story-sense StateMaps to Prose Style State
State 5.9: Prose is FlatP1-P6 (diagnose which specifically)
When to Hand Off
  • To revision: When prose issues require systematic pass through manuscript
  • To dialogue: When prose problems appear specifically in dialogue
  • To scene-sequencing: When rhythm problems are at scene level, not sentence level
Prerequisites

Do NOT use prose-style when:

  • Structure is still broken (fix structure first)
  • Scenes need cutting (don't polish what will be cut)
  • Character arcs incomplete (fix story before prose)

Prose style is last-mile work. Complete developmental revision first.


Available Tools

prose-check.ts

Analyzes prose patterns for common issues.

bash
deno run --allow-read scripts/prose-check.ts chapter.txt
deno run --allow-read scripts/prose-check.ts --text "The passive sentence was written..."

Detects:

  • Passive voice percentage
  • Weak verb frequency
  • Adverb density
  • Filter word usage
  • Adjective stacking
rhythm.ts

Analyzes rhythm and variety patterns.

bash
deno run --allow-read scripts/rhythm.ts chapter.txt
deno run --allow-read scripts/rhythm.ts --text "Short. Then longer. Then short again."

Reports:

  • Sentence length distribution
  • Paragraph length variation
  • Opening word variety
  • Rhythm score (variety metric)

Example Interactions

Example 1: Flat Prose

Writer: "My beta readers say my prose is functional but forgettable."

Your approach:

  1. Identify state: P1 (Flat Prose)
  2. Run rhythm.ts to check variety
  3. Ask: "Read a paragraph aloud. What do you notice?"
  4. Check: sentence lengths, word precision, rhythm
  5. Recommend: vary sentence length, replace generic words with specific
Example 2: Purple Prose

Writer: "People say my writing is overwrought but I like rich prose."

Your approach:

  1. Identify state: P3 (Overwrought)
  2. Distinguish: Rich prose serves the story; purple overwhelms it
  3. Ask: "Does the style serve the story or call attention to itself?"
  4. Check for: adjective stacking, adverb abuse, mixed metaphors
  5. Recommend: cut modifiers, simplify metaphors, let strong nouns/verbs work
Example 3: Inconsistent Voice

Writer: "Different chapters feel like different writers."

Your approach:

  1. Identify state: P6 (Inconsistent Voice)
  2. Ask: "What's your narrator's baseline voice?"
  3. Check: diction level shifts, rhythm pattern changes
  4. Recommend: establish baseline, vary intentionally from it

Output Persistence

This skill writes primary output to files so work persists across sessions.

Output Discovery

Before doing any other work:

  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found or no entry for this skill, ask the user first:
    • "Where should I save output from this prose-style session?"
    • Suggest: explorations/prose/ or a sensible location for this project
  4. Store the user's preference:
    • In context/output-config.md if context network exists
    • In .prose-style-output.md at project root otherwise
Primary Output

For this skill, persist:

  • Prose state diagnosis - which style issues apply
  • Sentence-level patterns - identified strengths and weaknesses
  • Voice baseline notes - established voice characteristics
  • Intervention recommendations - specific techniques to try
Conversation vs. File
Goes to FileStays in Conversation
Prose state diagnosisClarifying questions
Pattern identificationDiscussion of specific passages
Voice baseline definitionWriter's experimentation
Recommended techniquesReal-time feedback
File Naming

Pattern: {story}-prose-{date}.md Example: novel-chapter5-prose-2025-01-15.md

What You Do NOT Do

  • You do not rewrite prose for writers
  • You do not diagnose before structure is solid (hand off to story-sense)
  • You do not make mechanical rules absolute
  • You do not dismiss rich prose as automatically "purple"

Your role is diagnostic: identify the problem, explain why it's a problem, and guide toward the fix. The writer does the writing.


Key Insight

Prose is invisible when it works. The reader should experience the story, not notice the writing. When prose calls attention to itself—whether through flatness, confusion, or excess—it interrupts the dream.

The goal is not "good writing" in the abstract. The goal is writing that serves this specific story, these specific characters, this specific moment. Sometimes that means sparse. Sometimes rich. Always intentional.

© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in skills/creative/fiction/craft/prose-style of jwynia/agent-skills.

  • SKILL.md
  • scripts/prose-check.ts
  • scripts/rhythm.ts

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Prose Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prose Style compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prose Style this skilljwynia/agent-skills170—~4kAutomated safety check: PassMIT
Diagnose Gatewayopenclaw/openclaw392k—~670Automated safety check: PassMIT
Diagnosegithub/awesome-copilot40k1 repos~1kAutomated safety check: PassMIT
Control UI Solidopenclaw/openclaw392k—~3.9kAutomated safety check: PassMIT
Beautiful Prosesickn33/agentic-awesome-skills47k2 repos~1.4kAutomated safety check: PassMIT
Solidity Securitywshobson/agents40k12 repos~892Automated safety check: PassMIT

Similar skills

  • Diagnose Gateway

    openclaw/openclaw

    Diagnose Gateway, config, secrets, channels, and port failures with read-only one-liners.

    392k GitHub stars~670 tokensUpdated today
    Auto-check passed
  • Diagnose

    github/awesome-copilot

    Official

    Perform a systematic diagnostic scan of an AI workflow across 5 quality dimensions — prompt quality, context efficiency, tool health, architecture fitness, and safety — producing a scored report…

    40k GitHub starsUsed in 1 repo~1k tokens
    Agent WorkflowsAuto-check passed
  • Control UI Solid

    openclaw/openclaw

    Port or review OpenClaw Control UI code moving from Lit 3 and Web Awesome to Solid 2, including components, projections, lifecycle boundaries, and migration proof.

    392k GitHub stars~3.9k tokensUpdated today
    Auto-check passed
  • Beautiful Prose

    sickn33/agentic-awesome-skills

    A hard-edged writing style contract for timeless, forceful English prose without modern AI tics.

    47k GitHub starsUsed in 2 repos~1.4k tokens
    Writing & ContentAuto-check passed
  • Solidity Security

    wshobson/agents

    Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns.

    40k GitHub starsUsed in 12 repos~892 tokens
    Backend & APIsAuto-check passed
  • Diagnose Why Work Stopped

    paperclipai/paperclip

    Diagnose stalled, looping, or over-recovered Paperclip issue trees and propose a no-code product-rule plan.

    99k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

More from jwynia/agent-skills

All 111 skills in this repo
  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    170 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    170 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    170 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed
  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    170 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Questions about Prose Style

What does Prose Style do?

Diagnose sentence-level issues after structure is solid. An agent skill from jwynia/agent-skills. Prose Style is an agent skill from jwynia/agent-skills. Diagnose sentence-level issues after structure is solid.

When should I use Prose Style?

Prose Style fits situations like: prose feels flat; sentences are monotonous; word choices are generic; voice is inconsistent.

How do I install Prose Style in Claude Code?

Run `npx skills add jwynia/agent-skills --skill prose-style -a claude-code`. Or copy the skill folder (skills/creative/fiction/craft/prose-style in jwynia/agent-skills) into .claude/skills/prose-style in your project. Claude Code loads it when a task matches its description.

How do I install Prose Style in Codex?

Run `npx skills add jwynia/agent-skills --skill prose-style -a codex`. Or copy the skill folder (skills/creative/fiction/craft/prose-style in jwynia/agent-skills) into .agents/skills/prose-style in your project. Codex loads it when a task matches its description.

Can I use Prose Style in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill prose-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prose-style, .gemini/skills/prose-style, .github/skills/prose-style and .opencode/skills/prose-style in your project.

What does Prose Style need to run?

Going by SKILL.md and its folder, Prose Style needs TypeScript for the scripts in its folder and the command-line tools its instructions call (deno). Our summary lists: Node.js.

Does Prose Style access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prose Style safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Prose Style use?

Prose Style is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prose Style use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prose Style?

Skills that share tags, products or a category with Prose Style: Diagnose Gateway (openclaw/openclaw, 392k stars), Diagnose (github/awesome-copilot, 40k stars), Control UI Solid (openclaw/openclaw, 392k stars) and Beautiful Prose (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prose Style?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 170 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.