Prose
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…
Covers package READMEs, project docs and plain prose: namespace imports in examples, emoji and detail preservation, where docs live, docs that change with the code, and no empty qualifiers, unbacked…
Install Documentation Conventions
$ npx skills add eser/stack --skill documentation-conventions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install eser/stack documentation-conventions --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/eser/stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/documentation-conventions .claude/skills/documentation-conventions && 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 "documentation-conventions" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/documentation-conventions into .claude/skills/documentation-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-conventions", 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/eser/stack/tree/main/.agents/skills/documentation-conventionsType 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 eser/stack --skill documentation-conventions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install eser/stack documentation-conventions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/documentation-conventions .agents/skills/documentation-conventions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "documentation-conventions" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/documentation-conventions into .agents/skills/documentation-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-conventions", 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 eser/stack --skill documentation-conventions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install eser/stack documentation-conventions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/documentation-conventions .cursor/skills/documentation-conventions && 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 "documentation-conventions" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/documentation-conventions into .cursor/skills/documentation-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-conventions", 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/eser/stack.git --path .agents/skills/documentation-conventions--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 eser/stack --skill documentation-conventions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install eser/stack documentation-conventions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/documentation-conventions .gemini/skills/documentation-conventions && 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 "documentation-conventions" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/documentation-conventions into .gemini/skills/documentation-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-conventions", 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 eser/stack documentation-conventionsInstalls 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 eser/stack --skill documentation-conventions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/documentation-conventions .github/skills/documentation-conventions && 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 "documentation-conventions" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/documentation-conventions into .github/skills/documentation-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-conventions", 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 eser/stack --skill documentation-conventions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install eser/stack documentation-conventions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/documentation-conventions .opencode/skills/documentation-conventions && 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 "documentation-conventions" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/documentation-conventions into .opencode/skills/documentation-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-conventions", 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
documentation-conventions- GitHub stars
- 128
- Token cost
- ~410 tokens
- SKILL.md length
- 135 words
- Files
- 4 (incl. references)
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Covers package READMEs, project docs and plain prose: namespace imports in examples, emoji and detail preservation, where docs live, docs that change with the code, and no empty qualifiers, unbacked…
- Editing READMEs
- SKILL.md covers Always and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Changelog entries
What it does
Documentation Conventions is an agent skill from eser/stack. Covers package READMEs, project docs and plain prose: namespace imports in examples, emoji and detail preservation, where docs live, docs that change with the code, and no empty qualifiers, unbacked claims, em dashes or generated rhythm. Use when writing or editing READMEs, docs, skill files, ADR text, backlog items, changelog entries, commit messages or code comments.
Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/triggers.json`, `references/prose.md` and `references/readmes.md`).
It sits in Development, covering Technical documentation, Commit messages and Architecture decision records. The repository describes itself as: The Portability Solution for Your Code! 🚀 Powered By Deno and JavaScript.
When your agent uses it
- Editing READMEs
- Changelog entries
- Commit messages
Example prompts
- “Use the documentation-conventions skill to cover package READMEs, project docs and plain prose: namespace imports in examples, emoji and detail…”
- “/documentation-conventions”
What it can do on your machine
Read from SKILL.md and the folder at commit 64939e6. 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
Documentation Conventions loads about 410 tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 135 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 135 words (~410 tokens).
“Rules for what the repository's documents say and how they say it.”
- name
- documentation-conventions
Files
SKILL.md and 3 other files (references) in .agents/skills/documentation-conventions of eser/stack.
- SKILL.md
- evals/triggers.json
- references/prose.md
- references/readmes.md
Open the folder on GitHubat commit 64939e6
Compare with similar skills
Documentation Conventions 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 |
|---|---|---|---|---|---|---|
| Documentation Conventions this skilleser/stack | 128 | — | ~410 | Automated safety check: Pass | Custom licence | |
| Prosestatic-web-server/static-web-server | 2.4k | — | ~971 | Automated safety check: Pass | Apache-2.0 | |
| Agent Stylepchalasani/claude-code-tools | 2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Documentationaiskillstore/marketplace | 430 | 1 repos | ~2.7k | Automated safety check: Pass | None | |
| Swig Conventionsswig/swig | 6.3k | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| Docsbrickbots/PiFinder | 250 | — | ~6.2k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Agent Style
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
Documentation
aiskillstore/marketplace
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation.
Swig Conventions
swig/swig
SWIG source and contribution conventions: clang-format / code formatting, C/C++ comment style (quotes, widths, function header blocks), parser.y new-code rules, alphabetical ordering of makefile…
Docs
brickbots/PiFinder
Author and edit PiFinder's user-facing documentation in the project's house style.
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.
More from eser/stack
All 13 skills in this repoEser Rules Manager
eser/stack
Picks the skills a task needs and maintains the rules in .agents/skills.
Architecture Guidelines
eser/stack
System design in eserstack: double-layered hexagonal architecture, explicit adapter composition, public API and CLI surface, request metadata, testing strategy, ADRs.
Coding Practices
eser/stack
Language-neutral code quality rules for eserstack, TypeScript and Go.
Enrichment
eser/stack
Interviews the user about a plan, decision or idea in rounds, level by level down a decision tree, until both share one understanding; facts are researched by sub-agents, decisions stay with the user.
Go Practices
eser/stack
Go conventions for eserstack's ajan framework, services and FFI bridge.
Javascript Practices
eser/stack
TS and JS conventions for eserstack packages: namespace imports, mod.ts entries, cross-runtime APIs, explicit checks, async, tests and laroux React components.
Related
Categories
Questions about Documentation Conventions
What does Documentation Conventions do?
Covers package READMEs, project docs and plain prose: namespace imports in examples, emoji and detail preservation, where docs live, docs that change with the code, and no empty qualifiers, unbacked…. Documentation Conventions is an agent skill from eser/stack. Covers package READMEs, project docs and plain prose: namespace imports in examples, emoji and detail preservation, where docs live, docs that change with the code, and no empty qualifiers, unbacked claims, em dashes or generated rhythm.
When should I use Documentation Conventions?
Documentation Conventions fits situations like: editing READMEs; changelog entries; commit messages.
How do I install Documentation Conventions in Claude Code?
Run `npx skills add eser/stack --skill documentation-conventions -a claude-code`. Or copy the skill folder (.agents/skills/documentation-conventions in eser/stack) into .claude/skills/documentation-conventions in your project. Claude Code loads it when a task matches its description.
How do I install Documentation Conventions in Codex?
Run `npx skills add eser/stack --skill documentation-conventions -a codex`. Or copy the skill folder (.agents/skills/documentation-conventions in eser/stack) into .agents/skills/documentation-conventions in your project. Codex loads it when a task matches its description.
Can I use Documentation Conventions 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 eser/stack --skill documentation-conventions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documentation-conventions, .gemini/skills/documentation-conventions, .github/skills/documentation-conventions and .opencode/skills/documentation-conventions in your project.
What does Documentation Conventions need to run?
SKILL.md names no scripts, command-line tools or credentials: Documentation Conventions is instructions for the agent only.
Does Documentation Conventions 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 Documentation Conventions 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 Documentation Conventions use?
Documentation Conventions has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Documentation Conventions use?
About 410 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.
What are the alternatives to Documentation Conventions?
Skills that share tags, products or a category with Documentation Conventions: Prose (static-web-server/static-web-server, 2.4k stars), Agent Style (pchalasani/claude-code-tools, 2k stars), Documentation (aiskillstore/marketplace, 430 stars) and Swig Conventions (swig/swig, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Documentation Conventions?
eser (a GitHub user) maintains it in eser/stack, which has 128 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 3, 2026.
Source: eser/stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.