Agent Style
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes.
$ npx skills add rohitg00/pro-workflow --skill writing-guidelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rohitg00/pro-workflow writing-guidelines --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/rohitg00/pro-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing-guidelines .claude/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/rohitg00/pro-workflow/tree/main/skills/writing-guidelines into .claude/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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/rohitg00/pro-workflow/tree/main/skills/writing-guidelinesType 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 rohitg00/pro-workflow --skill writing-guidelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rohitg00/pro-workflow writing-guidelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohitg00/pro-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing-guidelines .agents/skills/writing-guidelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-guidelines" agent skill from https://github.com/rohitg00/pro-workflow/tree/main/skills/writing-guidelines into .agents/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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 rohitg00/pro-workflow --skill writing-guidelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rohitg00/pro-workflow writing-guidelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohitg00/pro-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing-guidelines .cursor/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/rohitg00/pro-workflow/tree/main/skills/writing-guidelines into .cursor/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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/rohitg00/pro-workflow.git --path skills/writing-guidelines--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 rohitg00/pro-workflow --skill writing-guidelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rohitg00/pro-workflow writing-guidelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohitg00/pro-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing-guidelines .gemini/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/rohitg00/pro-workflow/tree/main/skills/writing-guidelines into .gemini/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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 rohitg00/pro-workflow writing-guidelinesInstalls 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 rohitg00/pro-workflow --skill writing-guidelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rohitg00/pro-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing-guidelines .github/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/rohitg00/pro-workflow/tree/main/skills/writing-guidelines into .github/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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 rohitg00/pro-workflow --skill writing-guidelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rohitg00/pro-workflow writing-guidelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohitg00/pro-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing-guidelines .opencode/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/rohitg00/pro-workflow/tree/main/skills/writing-guidelines into .opencode/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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.
writing-guidelinesApply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes.
Writing Guidelines is an agent skill from rohitg00/pro-workflow. Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy", "draft the docs", "word this error".
Its SKILL.md is about 590 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 Brand voice and tone, Technical documentation and Plain language and style rules. The repository describes itself as: Claude Code learns from your corrections: self-correcting memory that compounds over 50+ sessions. Context engineering, parallel worktrees, agent teams, and 17 battle-tested…
Read from SKILL.md and the folder at commit 86d5f27. 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.
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.
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.
Writing Guidelines loads about 593 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 305 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); files beside SKILL.md are not scanned.
Without a licence we can't republish the file, so here is its outline and opening line. It has 305 words (~593 tokens).
“Write for a reader who is busy and did not see your work. Readability beats cleverness; clarity beats completeness.”
Just SKILL.md in skills/writing-guidelines of rohitg00/pro-workflow.
Open the folder on GitHubat commit 86d5f27
Writing Guidelines 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 |
|---|---|---|---|---|---|---|
| Writing Guidelines this skillrohitg00/pro-workflow | 2.9k | — | ~593 | Automated safety check: Pass | None | |
| Agent Stylepchalasani/claude-code-tools | 2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Simple Englishropensci/ckanr | 104 | 3 repos | ~2k | Automated safety check: Pass | MIT | |
| Adk Style GuideBrainDAO/adk-ts | 119 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Documentation Patternsyonatangross/orchestkit | 290 | — | ~830 | Automated safety check: Pass | MIT | |
| Technical Writingcitypaul/.dotfiles | 740 | — | ~2.5k | Automated safety check: Pass | MIT |
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
ropensci/ckanr
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before…
BrainDAO/adk-ts
ADK-TS brand voice, terminology, and writing conventions. An agent skill from BrainDAO/adk-ts.
yonatangross/orchestkit
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides.
citypaul/.dotfiles
Writing developer-facing prose that can be skimmed first and trusted enough to finish — READMEs, guides, tutorials, reference docs, proposals, PR descriptions, release notes.
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
rohitg00/pro-workflow
Start, structure, and grow a persistent research wiki indexed in pro-workflow's SQLite knowledge base.
rohitg00/pro-workflow
Provider-agnostic multi-LLM deliberation. An agent skill from rohitg00/pro-workflow.
rohitg00/pro-workflow
Compile a structured literature survey on any AI/ML topic. An agent skill from rohitg00/pro-workflow.
rohitg00/pro-workflow
Query pro-workflow wikis via SQLite FTS5 BM25 retrieval. An agent skill from rohitg00/pro-workflow.
rohitg00/pro-workflow
Auto-grow a pro-workflow wiki by running a budget-capped BFS research loop over pluggable source fetchers (web, arXiv, GitHub).
rohitg00/pro-workflow
Render a self-contained HTML viewer for a pro-workflow wiki.
Categories
Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Writing Guidelines is an agent skill from rohitg00/pro-workflow. Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes.
Writing Guidelines fits situations like: editing documentation; any text a human will read.
Run `npx skills add rohitg00/pro-workflow --skill writing-guidelines -a claude-code`. Or copy the skill folder (skills/writing-guidelines in rohitg00/pro-workflow) into .claude/skills/writing-guidelines in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rohitg00/pro-workflow --skill writing-guidelines -a codex`. Or copy the skill folder (skills/writing-guidelines in rohitg00/pro-workflow) into .agents/skills/writing-guidelines 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 rohitg00/pro-workflow --skill writing-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-guidelines, .gemini/skills/writing-guidelines, .github/skills/writing-guidelines and .opencode/skills/writing-guidelines in your project.
SKILL.md names no scripts, command-line tools or credentials: Writing Guidelines is instructions for the agent only.
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. Review the folder before installing.
No licence was found for Writing Guidelines or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
About 593 tokens (SKILL.md is roughly 2.4k 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 Writing Guidelines: Agent Style (pchalasani/claude-code-tools, 2k stars), Simple English (ropensci/ckanr, 104 stars), Adk Style Guide (BrainDAO/adk-ts, 119 stars) and Documentation Patterns (yonatangross/orchestkit, 290 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rohitg00 (a GitHub user) maintains it in rohitg00/pro-workflow, which has 2,907 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on September 29, 2026.
Source: rohitg00/pro-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.