Diagnose Gateway
openclaw/openclaw
Diagnose Gateway, config, secrets, channels, and port failures with read-only one-liners.
Diagnose sentence-level issues after structure is solid. An agent skill from jwynia/agent-skills.
$ npx skills add jwynia/agent-skills --skill prose-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jwynia/agent-skills prose-style --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "prose-style" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/prose-style into .claude/skills/prose-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-style", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/prose-styleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jwynia/agent-skills --skill prose-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jwynia/agent-skills prose-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/creative/fiction/craft/prose-style .agents/skills/prose-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prose-style" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/prose-style into .agents/skills/prose-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-style", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill prose-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jwynia/agent-skills prose-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/creative/fiction/craft/prose-style .cursor/skills/prose-style && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prose-style" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/prose-style into .cursor/skills/prose-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-style", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jwynia/agent-skills.git --path skills/creative/fiction/craft/prose-style--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jwynia/agent-skills --skill prose-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jwynia/agent-skills prose-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/creative/fiction/craft/prose-style .gemini/skills/prose-style && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prose-style" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/prose-style into .gemini/skills/prose-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-style", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jwynia/agent-skills prose-styleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jwynia/agent-skills --skill prose-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/creative/fiction/craft/prose-style .github/skills/prose-style && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prose-style" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/prose-style into .github/skills/prose-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-style", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill prose-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jwynia/agent-skills prose-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/creative/fiction/craft/prose-style .opencode/skills/prose-style && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prose-style" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/prose-style into .opencode/skills/prose-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose-style", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
prose-styleDiagnose 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. 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.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.
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.
Ships 2 files in scripts/ (TypeScript), which the agent can run.
Shell commands in SKILL.md call:
denoFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,968 words, ~3,994 tokens.
.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.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.
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:
The fundamental principle: Vigorous writing is concise. Every word earns its place.
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:
Diagnostic Checklist:
Interventions:
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:
Diagnostic Checklist:
Interventions:
Symptoms: Style overwhelms substance. Excessive adjectives and adverbs. Metaphors obscure rather than illuminate. Writing calls attention to itself rather than the story.
Key Questions:
Diagnostic Checklist:
Signs of Purple Prose:
Interventions:
Symptoms: Every sentence sounds the same. Every paragraph looks the same. Sentences start the same way. Reading feels like a drone.
Key Questions:
Diagnostic Checklist:
Interventions:
Symptoms: Prose feels indirect, weak. Agents are routinely hidden when they matter. Energy drains from sentences. Action feels distant.
Key Questions:
When Passive IS Appropriate:
Diagnostic Checklist:
Interventions:
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:
Levels of Diction:
| Level | Description | Example |
|---|---|---|
| High/Formal | Elevated, literary | "The conflagration consumed the edifice" |
| Middle/Standard | Educated but accessible | "The fire destroyed the building" |
| Low/Informal | Conversational | "The place burned down" |
Diagnostic Checklist:
Interventions:
From The Elements of Style, foundational guidance:
Caveat: These are principles, not laws. The goal is intentional choice, not mechanical obedience.
Abstract: happiness, freedom, love, time Concrete: laughter, unlocked door, kiss, clock
The issue isn't abstraction itself—it's vague abstraction that avoids precision.
| Trap | Description | Fix |
|---|---|---|
| Thesaurus abuse | Obscure synonyms for common words | Use the right word, even if repeated |
| Elegant variation | Different words for same thing | Repetition is fine; clarity matters |
| Jargon creep | Technical language where plain works | Use simplest word that fits |
The end of a sentence carries the most weight.
Parallel structure creates rhythm and emphasis:
Faulty parallelism:
| Length | Effect | Use For |
|---|---|---|
| Short | Punch, urgency | Emphasis, action, revelation |
| Medium | Clarity, flow | Default narrative |
| Long | Development, immersion | Building complexity, flowing prose |
The most reliable prose diagnostic: read it aloud.
What the ear catches that the eye misses:
"From the point of view of ear, Virginia Woolf never wrote a bad sentence." — Truman Capote
Rule: If you stumble reading it, revise it.
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.
Pattern: Stacking modifiers hoping something sticks. Problem: Weakens rather than strengthens description. Fix: Choose one right adjective. Or none—let the noun work.
Pattern: Writing in passive voice without intention. Problem: Prose loses energy and directness. Fix: Default to active. Use passive deliberately.
Pattern: Every sentence same length and structure. Problem: Creates droning effect; reader disengages. Fix: Vary intentionally. Short sentences punch. Long sentences flow.
Pattern: Style overwhelming substance. Problem: Reader sees the writing, not the story. Fix: Serve the story. Kill your darlings if they distract.
Pattern: Following every prescription mechanically. Problem: Loses the art in favor of rules. Fix: Understand principles, not just rules. Break rules intentionally.
When a writer presents prose problems:
Have writer read problematic passages aloud. What do they stumble on?
Based on identified state, provide specific fixes.
| story-sense State | Maps to Prose Style State |
|---|---|
| State 5.9: Prose is Flat | P1-P6 (diagnose which specifically) |
Do NOT use prose-style when:
Prose style is last-mile work. Complete developmental revision first.
Analyzes prose patterns for common issues.
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:
Analyzes rhythm and variety patterns.
deno run --allow-read scripts/rhythm.ts chapter.txt
deno run --allow-read scripts/rhythm.ts --text "Short. Then longer. Then short again."Reports:
Writer: "My beta readers say my prose is functional but forgettable."
Your approach:
Writer: "People say my writing is overwrought but I like rich prose."
Your approach:
Writer: "Different chapters feel like different writers."
Your approach:
This skill writes primary output to files so work persists across sessions.
Before doing any other work:
context/output-config.md in the projectexplorations/prose/ or a sensible location for this projectcontext/output-config.md if context network exists.prose-style-output.md at project root otherwiseFor this skill, persist:
| Goes to File | Stays in Conversation |
|---|---|
| Prose state diagnosis | Clarifying questions |
| Pattern identification | Discussion of specific passages |
| Voice baseline definition | Writer's experimentation |
| Recommended techniques | Real-time feedback |
Pattern: {story}-prose-{date}.md
Example: novel-chapter5-prose-2025-01-15.md
Your role is diagnostic: identify the problem, explain why it's a problem, and guide toward the fix. The writer does the writing.
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
SKILL.md and 2 other files (scripts) in skills/creative/fiction/craft/prose-style of jwynia/agent-skills.
Open the folder on GitHubat commit e02ec7e
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prose Style this skilljwynia/agent-skills | 170 | — | ~4k | Automated safety check: Pass | MIT | |
| Diagnose Gatewayopenclaw/openclaw | 392k | — | ~670 | Automated safety check: Pass | MIT | |
| Diagnosegithub/awesome-copilot | 40k | 1 repos | ~1k | Automated safety check: Pass | MIT | |
| Control UI Solidopenclaw/openclaw | 392k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Beautiful Prosesickn33/agentic-awesome-skills | 47k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Solidity Securitywshobson/agents | 40k | 12 repos | ~892 | Automated safety check: Pass | MIT |
openclaw/openclaw
Diagnose Gateway, config, secrets, channels, and port failures with read-only one-liners.
github/awesome-copilot
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…
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.
sickn33/agentic-awesome-skills
A hard-edged writing style contract for timeless, forceful English prose without modern AI tics.
wshobson/agents
Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns.
paperclipai/paperclip
Diagnose stalled, looping, or over-recovered Paperclip issue trees and propose a no-code product-rule plan.
jwynia/agent-skills
Diagnose devcontainer configuration problems and guide development environment setup.
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality.
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
jwynia/agent-skills
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.
jwynia/agent-skills
Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.
jwynia/agent-skills
Create and manipulate PowerPoint PPTX files programmatically.
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.
Prose Style fits situations like: prose feels flat; sentences are monotonous; word choices are generic; voice is inconsistent.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.