Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
Write documentation following Metabase's conversational, clear, and user-focused style.
Install Docs Write
$ npx skills add tmcfarlane/oh-my-cursor --skill docs-write -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tmcfarlane/oh-my-cursor docs-write --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/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/docs-write .claude/skills/docs-write && 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 "docs-write" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/docs-write into .claude/skills/docs-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-write", 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/tmcfarlane/oh-my-cursor/tree/main/skills/docs-writeType 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 tmcfarlane/oh-my-cursor --skill docs-write -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tmcfarlane/oh-my-cursor docs-write --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/docs-write .agents/skills/docs-write && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs-write" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/docs-write into .agents/skills/docs-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-write", 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 tmcfarlane/oh-my-cursor --skill docs-write -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tmcfarlane/oh-my-cursor docs-write --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/docs-write .cursor/skills/docs-write && 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 "docs-write" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/docs-write into .cursor/skills/docs-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-write", 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/tmcfarlane/oh-my-cursor.git --path skills/docs-write--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 tmcfarlane/oh-my-cursor --skill docs-write -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tmcfarlane/oh-my-cursor docs-write --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/docs-write .gemini/skills/docs-write && 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 "docs-write" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/docs-write into .gemini/skills/docs-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-write", 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 tmcfarlane/oh-my-cursor docs-writeInstalls 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 tmcfarlane/oh-my-cursor --skill docs-write -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/docs-write .github/skills/docs-write && 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 "docs-write" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/docs-write into .github/skills/docs-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-write", 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 tmcfarlane/oh-my-cursor --skill docs-write -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tmcfarlane/oh-my-cursor docs-write --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/docs-write .opencode/skills/docs-write && 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 "docs-write" agent skill from https://github.com/tmcfarlane/oh-my-cursor/tree/main/skills/docs-write into .opencode/skills/docs-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-write", 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
docs-write- GitHub stars
- 110
- Used in
- 3 other repos
- Token cost
- ~716 tokens
- SKILL.md length
- 307 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write documentation following Metabase's conversational, clear, and user-focused style.
- Works in 3 steps: Who is this for? Match complexity to… → What do they need? Get them to the… → What did you struggle with? Those common…
- Editing documentation files (markdown
- Calls bun
- Tasks that involve Markdown
What it does
Docs Write is an agent skill from tmcfarlane/oh-my-cursor. Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
Its SKILL.md is about 720 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 Documents & Office, covering Markdown. The repository describes itself as: Like “oh-my-opencode”, but for Cursor IDE. Multi-agent orchestration, natively, using nothing but a few config files. The licence is MIT.
When your agent uses it
- Editing documentation files (markdown
- Tasks that involve Markdown
Example prompts
- “/docs-write”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Grep, Bash, Glob
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Who is this for? Match complexity to audience. Don't oversimplify hard things or overcomplicate simple ones.
- What do they need? Get them to the answer fast. Nobody wants to be in docs longer than necessary.
- What did you struggle with? Those common questions you had when learning? Answer them (without literally including the question).
What it can do on your machine
Read from SKILL.md and the folder at commit 5bad458. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteGrepBashGlob
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bun
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
Docs Write loads about 716 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 307 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Grep, Bash, Glob
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 tmcfarlane/oh-my-cursor at commit 5bad458, republished under its MIT licence (© tmcfarlane). 307 words, ~716 tokens.
Download SKILL.mdSave it as
.claude/skills/docs-write/SKILL.md (or your agent's skills folder).- name
- docs-write
- description
- Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
- allowed-tools
- Read, Write, Grep, Bash, Glob
Documentation Writing Skill
@./../_shared/metabase-style-guide.md
When writing documentation
Start here
- Who is this for? Match complexity to audience. Don't oversimplify hard things or overcomplicate simple ones.
- What do they need? Get them to the answer fast. Nobody wants to be in docs longer than necessary.
- What did you struggle with? Those common questions you had when learning? Answer them (without literally including the question).
Writing process
Draft:
- Write out the steps/explanation as you'd tell a colleague
- Lead with what to do, then explain why
- Use headings that state your point: "Set SAML before adding users" not "SAML configuration timing"
Edit:
- Read aloud. Does it sound like you talking? If it's too formal, simplify.
- Cut anything that doesn't directly help the reader
- Check each paragraph has one clear purpose
- Verify examples actually work (don't give examples that error)
Polish:
- Make links descriptive (never "here")
- Backticks only for code/variables, bold for UI elements
- American spelling, serial commas
- Keep images minimal and scoped tight
Format:
- Run prettier on the file after making edits:
bun run prettier --write <file-path> - This ensures consistent formatting across all documentation
Common patterns
Instructions:
Run:
\`\`\`
command-to-run
\`\`\`
Then:
\`\`\`
next-command
\`\`\`
This ensures you're getting the latest changes.Not: "(remember to run X before Y...)" buried in a paragraph.
Headings:
- "Use environment variables for configuration" ✅
- "Environment variables" ❌ (too vague)
- "How to use environment variables for configuration" ❌ (too wordy)
Links:
- "Check out the SAML documentation" ✅
- "Read the docs here" ❌
Watch out for
- Describing tasks as "easy" (you don't know the reader's context)
- Using "we" when talking about Metabase features (use "Metabase" or "it")
- Formal language: "utilize", "reference", "offerings"
- Too peppy: multiple exclamation points
- Burying the action in explanation
- Code examples that don't work
- Numbers that will become outdated
Quick reference
© tmcfarlane, MIT. 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 skills/docs-write of tmcfarlane/oh-my-cursor.
Open the folder on GitHubat commit 5bad458
Used in 3 other repositories
We found 18 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in tmcfarlane/oh-my-cursor, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Docs Write 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 |
|---|---|---|---|---|---|---|
| Docs Write this skilltmcfarlane/oh-my-cursor | 110 | 3 repos | ~716 | Automated safety check: Notes | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 26k | 7 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Gzh Designisjiamu/gzh-design-skill | 3.9k | 1 repos | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| Crosspostingwasp-lang/wasp | 19k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
Crossposting
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
- Official
Review The Docs
supabase/supabase
Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).
More from tmcfarlane/oh-my-cursor
All 14 skills in this repoDebugging
tmcfarlane/oh-my-cursor
Systematic 4-phase debugging with root cause investigation. An agent skill from tmcfarlane/oh-my-cursor.
Documentation Engineer
tmcfarlane/oh-my-cursor
Technical documentation expert for creating clear, comprehensive documentation.
Planning
tmcfarlane/oh-my-cursor
Technical implementation planning and architecture design. An agent skill from tmcfarlane/oh-my-cursor.
Codebase Search
tmcfarlane/oh-my-cursor
Search and navigate large codebases efficiently. An agent skill from tmcfarlane/oh-my-cursor.
Cursor Image Generation
tmcfarlane/oh-my-cursor
Generate and iterate images in Cursor using the built-in image model and strong prompts.
Design Patterns Implementation
tmcfarlane/oh-my-cursor
Apply appropriate design patterns (Singleton, Factory, Observer, Strategy, etc.) to solve architectural problems.
Related
Categories
Questions about Docs Write
What does Docs Write do?
Write documentation following Metabase's conversational, clear, and user-focused style. Docs Write is an agent skill from tmcfarlane/oh-my-cursor. Write documentation following Metabase's conversational, clear, and user-focused style.
When should I use Docs Write?
Docs Write fits situations like: editing documentation files (markdown; tasks that involve Markdown.
How do I install Docs Write in Claude Code?
Run `npx skills add tmcfarlane/oh-my-cursor --skill docs-write -a claude-code`. Or copy the skill folder (skills/docs-write in tmcfarlane/oh-my-cursor) into .claude/skills/docs-write in your project. Claude Code loads it when a task matches its description.
How do I install Docs Write in Codex?
Run `npx skills add tmcfarlane/oh-my-cursor --skill docs-write -a codex`. Or copy the skill folder (skills/docs-write in tmcfarlane/oh-my-cursor) into .agents/skills/docs-write in your project. Codex loads it when a task matches its description.
Can I use Docs Write 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 tmcfarlane/oh-my-cursor --skill docs-write -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-write, .gemini/skills/docs-write, .github/skills/docs-write and .opencode/skills/docs-write in your project.
What does Docs Write need to run?
Going by SKILL.md and its folder, Docs Write needs the command-line tools its instructions call (bun). Its frontmatter pre-approves these tools: Read, Write, Grep, Bash, Glob.
Does Docs Write 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 Docs Write safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Docs Write use?
Docs Write is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docs Write use?
About 716 tokens (SKILL.md is roughly 2.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 Docs Write?
Skills that share tags, products or a category with Docs Write: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and Gzh Design (isjiamu/gzh-design-skill, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs Write?
tmcfarlane (a GitHub user) maintains it in tmcfarlane/oh-my-cursor, which has 110 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on July 2, 2026.
Source: tmcfarlane/oh-my-cursor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.