Plain Writing
docwriter-org/plain-writing-skill
Writes and edits prose in a plain and boring style: simple everyday words, complete sentences, no dashes, no jargon, and no analogies.
Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following…
Install Prose
$ npx skills add static-web-server/static-web-server --skill prose -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install static-web-server/static-web-server prose --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/static-web-server/static-web-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prose .claude/skills/prose && 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" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/prose into .claude/skills/prose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose", 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/static-web-server/static-web-server/tree/master/.agents/skills/proseType 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 static-web-server/static-web-server --skill prose -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install static-web-server/static-web-server prose --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/prose .agents/skills/prose && 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" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/prose into .agents/skills/prose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose", 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 static-web-server/static-web-server --skill prose -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install static-web-server/static-web-server prose --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/prose .cursor/skills/prose && 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" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/prose into .cursor/skills/prose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose", 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/static-web-server/static-web-server.git --path .agents/skills/prose--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 static-web-server/static-web-server --skill prose -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install static-web-server/static-web-server prose --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/prose .gemini/skills/prose && 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" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/prose into .gemini/skills/prose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose", 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 static-web-server/static-web-server proseInstalls 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 static-web-server/static-web-server --skill prose -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/prose .github/skills/prose && 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" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/prose into .github/skills/prose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose", 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 static-web-server/static-web-server --skill prose -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install static-web-server/static-web-server prose --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/prose .opencode/skills/prose && 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" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/prose into .opencode/skills/prose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prose", 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.
Facts
- Skill name
prose- GitHub stars
- 2.4k
- Token cost
- ~971 tokens
- SKILL.md length
- 495 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following…
- Works in 5 steps: One sentence summary at the top of what… → Default state: Whether enabled by… → CLI example: A static-web-server… → …
- Tasks that involve Pull requests
- SKILL.md covers Writing Style, Document Structure, Feature Documentation and Terminology
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Prose is an agent skill from static-web-server/static-web-server. Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following project writing conventions
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests, Technical documentation and Commit messages. It works with Linux. The repository describes itself as: A cross-platform, high-performance and asynchronous web server for static files-serving. ⚡. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Pull requests
- Tasks that involve Technical documentation
- Tasks that involve Commit messages
Example prompts
- “/prose”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- One sentence summary at the top of what the feature does
- Default state: Whether enabled by default, and the flag to toggle it
- CLI example: A static-web-server invocation with the relevant flags
- Behavior: What happens when enabled vs disabled
- Related features: Cross-link to features that interact (e.g., compression-static → compression)
What it can do on your machine
Read from SKILL.md and the folder at commit 32ec4aa. 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
No scripts in the folder and no shell commands in SKILL.md.
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 loads about 971 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 495 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.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from static-web-server/static-web-server at commit 32ec4aa, republished under its Apache-2.0 licence (© static-web-server). 495 words, ~971 tokens.
Download SKILL.mdSave it as
.claude/skills/prose/SKILL.md (or your agent's skills folder).- name
- prose
- description
- Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following project writing conventions
Writing SWS Prose
Load this skill whenever writing or editing prose for this project: documentation in docs/, READMEs, design docs, PR descriptions, issue bodies, commit message bodies, or any other human-readable markdown.
When to load: editing any file under docs/, writing a commit message body, drafting a PR description or issue body, or producing any user-facing markdown for the SWS project.
Writing Style
- Avoid ambiguous characters: Do not use ambiguous Unicode characters, homoglyphs, and confusables in identifiers, code, code comments/docs or user input as they can lead to security issues.
- Be fact-focused: State what things are and what they do
- Avoid buzzwords: No "leverage", "synergy", "paradigm", etc.
- Avoid fluff: Every sentence should convey information
- Avoid weasel words: No "very", "really", "quite", "somewhat"
- Avoid dramatic terms: No "critical", "crucial", "vital", "essential" unless something will actually break
- Avoid figurative metaphors: Pick the literal word for the thing, not the analogy. "Blazing fast" → "sub-millisecond latency" or "serves files at line rate". "Battle-tested" → "used in production since 2019". Other recurring offenders: "under the hood" (just describe what's there), "out of the box" (just say "by default"), "first-class" (say what's actually supported). If you can't replace the metaphor with a literal noun or verb without losing meaning, you probably don't know what you mean yet.
- Be direct: Say what you mean without hedging
- Use concrete examples: Show, don't tell. Include CLI invocations and HTTP response snippets
- Use active voice: "SWS appends security headers to the response" not "Security headers are appended by SWS"
- Use present tense: Describe how the system works now, not how it was designed or how it will work
- Document current behavior only: Omit historical decisions, deprecated approaches, and planned future work
Show full SKILL.md (215 more words)Show less
Examples
Bad: "This feature is critical for ensuring optimal web server performance."
Good: "Static compression serves pre-compressed .br files from disk with zero CPU overhead, avoiding on-the-fly compression."
Bad: "SWS leverages advanced algorithms to enhance delivery."
Good: "SWS uses accept-encoding header negotiation to select the best compression algorithm (zstd, brotli, gzip, deflate) supported by the client."
Bad: "## Features that work out of the box"
Good: "## Enabled by default"
Document Structure
- Start with what the thing is
- Explain why it exists (what problem it solves)
- Explain what it does
- Show how to use it (if applicable)
- Provide examples (CLI invocations, config snippets, HTTP headers)
Feature Documentation
When documenting an SWS feature in docs/content/features/:
- One sentence summary at the top of what the feature does
- Default state: Whether enabled by default, and the flag to toggle it
- CLI example: A
static-web-serverinvocation with the relevant flags - Behavior: What happens when enabled vs disabled
- Related features: Cross-link to features that interact (e.g., compression-static → compression)
Terminology
- SWS: Static Web Server (the project). Use "SWS" after the first mention
- Pre-compressed / static compression: Serving
.br/.gz/.zstfiles from disk - On-the-fly / dynamic compression: Compressing responses in real-time
- Root directory: The
--rootdirectory from which files are served - Base path: The canonicalized root directory used for path containment checks
© static-web-server, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/prose of static-web-server/static-web-server.
Open the folder on GitHubat commit 32ec4aa
Compare with similar skills
Prose 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 this skillstatic-web-server/static-web-server | 2.4k | — | ~971 | Automated safety check: Pass | Apache-2.0 | |
| Plain Writingdocwriter-org/plain-writing-skill | 461 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Writing Stylepydantic/monty | 8.6k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Agent Stylepchalasani/claude-code-tools | 2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Neru Create PRy3owk1n/neru | 785 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Writingagentic-community/mcp-gateway-registry | 964 | — | ~3.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Writing Style
pydantic/monty
How to write prose that reads like human technical documentation rather than LLM output.
Agent Style
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
Neru Create PR
y3owk1n/neru
Commit working changes and open a Neru pull request the maintainer's way: conventional commit subjects, a PR title written for the changelog, the just ci gate, and the repo PR template filled…
Writing
agentic-community/mcp-gateway-registry
Write prose people will actually read. An agent skill from agentic-community/mcp-gateway-registry.
Prepare PR Files
QwenLM/qwen-code
Writes a PR title file and a template-filled PR body file from the current branch diff, without pushing, commenting or creating the pull request.
More from static-web-server/static-web-server
All 9 skills in this repoDesign
static-web-server/static-web-server
Design or review software architecture, API contracts, data models, and module boundaries for the Static Web Server (SWS) project
Issue Tracking
static-web-server/static-web-server
Triage, debug, fix, and document issues for the Static Web Server (SWS) project — bug reports, root cause analysis, fix implementation, and regression prevention
Performance
static-web-server/static-web-server
Optimize or review performance for the Static Web Server (SWS) project — profiling, bottlenecks, resource usage, compression, and caching
Rust Backend
static-web-server/static-web-server
Write or review Rust backend code for the Static Web Server (SWS) project — crates, modules, functions, types, error handling, and async code
Static File Serving
static-web-server/static-web-server
Serve static files and web assets with optimal headers, MIME types, compression, and caching for the Static Web Server (SWS) project
Testing
static-web-server/static-web-server
Write or review tests for the Static Web Server (SWS) project — unit tests, integration tests, test fixtures, and mocking strategies
Related
Works with
Categories
Questions about Prose
What does Prose do?
Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following…. Prose is an agent skill from static-web-server/static-web-server.
When should I use Prose?
Prose fits situations like: tasks that involve Pull requests; tasks that involve Technical documentation; tasks that involve Commit messages.
How do I install Prose in Claude Code?
Run `npx skills add static-web-server/static-web-server --skill prose -a claude-code`. Or copy the skill folder (.agents/skills/prose in static-web-server/static-web-server) into .claude/skills/prose in your project. Claude Code loads it when a task matches its description.
How do I install Prose in Codex?
Run `npx skills add static-web-server/static-web-server --skill prose -a codex`. Or copy the skill folder (.agents/skills/prose in static-web-server/static-web-server) into .agents/skills/prose in your project. Codex loads it when a task matches its description.
Can I use Prose 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 static-web-server/static-web-server --skill prose -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, .gemini/skills/prose, .github/skills/prose and .opencode/skills/prose in your project.
What does Prose need to run?
SKILL.md names no scripts, command-line tools or credentials: Prose is instructions for the agent only.
Does Prose 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 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. Review the folder before installing.
What licence does Prose use?
Prose is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Prose use?
About 971 tokens (SKILL.md is roughly 3.9k 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?
Skills that share tags, products or a category with Prose: Plain Writing (docwriter-org/plain-writing-skill, 461 stars), Writing Style (pydantic/monty, 8.6k stars), Agent Style (pchalasani/claude-code-tools, 2k stars) and Neru Create PR (y3owk1n/neru, 785 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prose?
static-web-server (a GitHub organization) maintains it in static-web-server/static-web-server, which has 2,372 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: static-web-server/static-web-server on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.