Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
“Use for public LobeHub website documentation under docs/**, including self-hosting, deployment, migration, and configuration guides. Excludes product changelogs and source-code…”
Install Landing Docs Writer
$ npx skills add lobehub/lobehub --skill write-landing-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lobehub/lobehub write-landing-docs --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/lobehub/lobehub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-landing-docs .claude/skills/write-landing-docs && 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 "write-landing-docs" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/write-landing-docs into .claude/skills/write-landing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-landing-docs", 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/lobehub/lobehub/tree/canary/.agents/skills/write-landing-docsType 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 lobehub/lobehub --skill write-landing-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lobehub/lobehub write-landing-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-landing-docs .agents/skills/write-landing-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-landing-docs" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/write-landing-docs into .agents/skills/write-landing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-landing-docs", 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 lobehub/lobehub --skill write-landing-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lobehub/lobehub write-landing-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-landing-docs .cursor/skills/write-landing-docs && 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 "write-landing-docs" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/write-landing-docs into .cursor/skills/write-landing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-landing-docs", 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/lobehub/lobehub.git --path .agents/skills/write-landing-docs--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 lobehub/lobehub --skill write-landing-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lobehub/lobehub write-landing-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-landing-docs .gemini/skills/write-landing-docs && 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 "write-landing-docs" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/write-landing-docs into .gemini/skills/write-landing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-landing-docs", 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 lobehub/lobehub write-landing-docsInstalls 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 lobehub/lobehub --skill write-landing-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-landing-docs .github/skills/write-landing-docs && 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 "write-landing-docs" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/write-landing-docs into .github/skills/write-landing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-landing-docs", 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 lobehub/lobehub --skill write-landing-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lobehub/lobehub write-landing-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-landing-docs .opencode/skills/write-landing-docs && 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 "write-landing-docs" agent skill from https://github.com/lobehub/lobehub/tree/canary/.agents/skills/write-landing-docs into .opencode/skills/write-landing-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-landing-docs", 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
write-landing-docs- GitHub stars
- 83k
- Token cost
- ~259 tokens
- SKILL.md length
- 96 words
- Files
- 2 (incl. references)
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
About this skill
“Use for public LobeHub website documentation under docs/**, including self-hosting, deployment, migration, and configuration guides. Excludes product changelogs and source-code API docs.”
Landing Docs Writer is a skill in lobehub/lobehub (83k stars). Its SKILL.md is about 259 tokens, with 1 other file in the folder (references). Licence: Custom licence.
What it can do on your machine
Read from SKILL.md and the folder at commit 6aaeeee. 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
Landing Docs Writer loads about 259 tokens when it runs, and up to ~480 if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 96 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 96 words (~259 tokens).
“result. Keep English and Simplified Chinese versions aligned.”
- name
- write-landing-docs
Files
SKILL.md and 1 other file (references) in .agents/skills/write-landing-docs of lobehub/lobehub.
- SKILL.md
- references/self-hosting.md
Open the folder on GitHubat commit 6aaeeee
Compare with similar skills
Landing Docs Writer 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 |
|---|---|---|---|---|---|---|
| Landing Docs Writer this skilllobehub/lobehub | 83k | — | ~259 | Automated safety check: Pass | Custom licence | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None | |
| Heym Documentation Articlesheymrun/heym | 1.4k | — | ~780 | Automated safety check: Pass | Custom licence | |
| Aholo Viewer Docsmanycoretech/aholo-viewer | 1.1k | — | ~341 | Automated safety check: Pass | MIT | |
| Handsontable Docs Page Writinghandsontable/handsontable | 22k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| ISO 24495-3 Technical Plain LanguageGaZmagik/iso-24495 | 189 | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
Heym Documentation Articles
heymrun/heym
Creates and updates documentation articles for the Heym platform: category choice, manifest entry, markdown file and cross-links from existing pages.
Aholo Viewer Docs
manycoretech/aholo-viewer
Guides writing and maintaining Aholo Viewer documentation: README, AGENTS.md, architecture notes, bilingual manual pages and AI collaboration guides.
Handsontable Docs Page Writing
handsontable/handsontable
Rules for writing Handsontable guide pages: required frontmatter, page structure, framework-specific example embedding, writing style and sidebar registration.
ISO 24495-3 Technical Plain Language
GaZmagik/iso-24495
Applies plain language rules to software documentation, architecture explanations, code reviews and technical analysis, following the principles of ISO 24495-3:2026.
UX Writing and Docs Rules
scarletkc/agents
Judgment rules for user-facing text and docs: status output, diagnostics, error and help text, README structure, comments and titles, each backed by a real counter-example.
More from lobehub/lobehub
All 50 skills in this repoLobeHub Interactive Prototype
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
Git Worktree Cleanup
lobehub/lobehub
Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.
LobeHub Alint Rule Set Maintenance
lobehub/lobehub
Maintains LobeHub's model-backed alint rule set: writing rules, removing false positives against real code, deciding warn versus error and tracking token cost.
LobeHub Builtin Tool Authoring
lobehub/lobehub
Guides building LobeHub builtin agent tools, from the manifest and execution runtime to executors, chat UI renders and registry wiring.
LobeHub Data Fetching Layers
lobehub/lobehub
Explains how LobeHub client code fetches data through services, SWR store hooks and cache keys, and when to avoid useEffect fetching or duplicated state.
Related
Categories
Questions about Landing Docs Writer
How do I install Landing Docs Writer in Claude Code?
Run `npx skills add lobehub/lobehub --skill write-landing-docs -a claude-code`. Or copy the skill folder (.agents/skills/write-landing-docs in lobehub/lobehub) into .claude/skills/write-landing-docs in your project. Claude Code loads it when a task matches its description.
How do I install Landing Docs Writer in Codex?
Run `npx skills add lobehub/lobehub --skill write-landing-docs -a codex`. Or copy the skill folder (.agents/skills/write-landing-docs in lobehub/lobehub) into .agents/skills/write-landing-docs in your project. Codex loads it when a task matches its description.
Can I use Landing Docs Writer 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 lobehub/lobehub --skill write-landing-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-landing-docs, .gemini/skills/write-landing-docs, .github/skills/write-landing-docs and .opencode/skills/write-landing-docs in your project.
What does Landing Docs Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: Landing Docs Writer is instructions for the agent only.
Does Landing Docs Writer 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 Landing Docs Writer 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 Landing Docs Writer use?
Landing Docs Writer 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 Landing Docs Writer use?
About 259 tokens (SKILL.md is roughly 1k 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 221 tokens, read only when the agent opens those files.
What are the alternatives to Landing Docs Writer?
Skills that share tags, products or a category with Landing Docs Writer: Technical Writing Standard (cursor/plugins, 10k stars), Heym Documentation Articles (heymrun/heym, 1.4k stars), Aholo Viewer Docs (manycoretech/aholo-viewer, 1.1k stars) and Handsontable Docs Page Writing (handsontable/handsontable, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Landing Docs Writer?
lobehub (a GitHub organization) maintains it in lobehub/lobehub, which has 83,044 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 8, 2026.
Source: lobehub/lobehub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.