ISO 24495 Text Audit
GaZmagik/iso-24495
Audits a Markdown or text file or folder you choose for plain-language problems such as legalese, wordy phrases and long sentences, reporting each finding with file and line.
How to write a function/hook/action reference section, and how to write or rework a whole app's multi-page doc set (Overview/Features/Talk to the Agent/Cross-App Use/Developer Guide): plain-language…
Install Writing Reference Docs
$ npx skills add BuilderIO/agent-native --skill writing-reference-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuilderIO/agent-native writing-reference-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/BuilderIO/agent-native.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-reference-docs .claude/skills/writing-reference-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 "writing-reference-docs" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/writing-reference-docs into .claude/skills/writing-reference-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-reference-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/BuilderIO/agent-native/tree/main/.agents/skills/writing-reference-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 BuilderIO/agent-native --skill writing-reference-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuilderIO/agent-native writing-reference-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-reference-docs .agents/skills/writing-reference-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 "writing-reference-docs" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/writing-reference-docs into .agents/skills/writing-reference-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-reference-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 BuilderIO/agent-native --skill writing-reference-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuilderIO/agent-native writing-reference-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-reference-docs .cursor/skills/writing-reference-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 "writing-reference-docs" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/writing-reference-docs into .cursor/skills/writing-reference-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-reference-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/BuilderIO/agent-native.git --path .agents/skills/writing-reference-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 BuilderIO/agent-native --skill writing-reference-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuilderIO/agent-native writing-reference-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-reference-docs .gemini/skills/writing-reference-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 "writing-reference-docs" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/writing-reference-docs into .gemini/skills/writing-reference-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-reference-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 BuilderIO/agent-native writing-reference-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 BuilderIO/agent-native --skill writing-reference-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-reference-docs .github/skills/writing-reference-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 "writing-reference-docs" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/writing-reference-docs into .github/skills/writing-reference-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-reference-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 BuilderIO/agent-native --skill writing-reference-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 BuilderIO/agent-native writing-reference-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-reference-docs .opencode/skills/writing-reference-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 "writing-reference-docs" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/writing-reference-docs into .opencode/skills/writing-reference-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-reference-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
writing-reference-docs- GitHub stars
- 7.1k
- Token cost
- ~3.5k tokens
- SKILL.md length
- 1,920 words
- Files
- 1
- Skills in repo
- 102
- Repo updated
- First seen
- Licence
- None found
At a glance
How to write a function/hook/action reference section, and how to write or rework a whole app's multi-page doc set (Overview/Features/Talk to the Agent/Cross-App Use/Developer Guide): plain-language…
- Works in 8 steps: Match heading level to role. Hooks that… → Open with plain-language purpose, then… → List real arguments as a short bullet… → …
- Editing a packages/core/docs/content reference page
- SKILL.md covers Rule, Why, How and Don't, plus 6 more sections
- Calls pnpm
What it does
Writing Reference Docs is an agent skill from BuilderIO/agent-native. How to write a function/hook/action reference section, and how to write or rework a whole app's multi-page doc set (Overview/Features/Talk to the Agent/Cross-App Use/Developer Guide): plain-language signature, real arguments, escalating examples grounded in a real app, verified agent behavior, trimmed prose with no em dashes or semicolons. Use when writing or editing a packages/core/docs/content reference page, or reworking a template-<app.mdx doc set.
Its SKILL.md is about 3.5k 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 Writing & Content, covering Markdown and Plain language and style rules. The repository describes itself as: A framework for building agentic apps.
When your agent uses it
- Editing a packages/core/docs/content reference page
- Reworking a template-<app.mdx doc set
Example prompts
- “/writing-reference-docs”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Match heading level to role. Hooks that solve the same kind of problem
- Open with plain-language purpose, then link out. State what the
- List real arguments as a short bullet list, matching the actual
- Give two or more escalating examples. The first is the simplest
- Ground every example in a real reference app's real action, not an
- Close with the one behavior fact a reader needs, in one or two
- Prose rules, every sentence: no em dashes, no semicolons (this
- Example values must mean something to a reader with zero app context.
What it can do on your machine
Read from SKILL.md and the folder at commit e16da0c. 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
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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
Writing Reference Docs loads about 3.5k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 1,920 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,920 words (~3,510 tokens).
“This came out of rewriting client-data.mdx's hook sections (useActionQuery, useActionMutation, callAction, useDbSync) section by section with the user. It captures the shape that emerged so the next reference section starts from it instead of reinventing it.”
- name
- writing-reference-docs
- scope
- dev
- metadata.internal
- true
Files
Just SKILL.md in .agents/skills/writing-reference-docs of BuilderIO/agent-native.
Open the folder on GitHubat commit e16da0c
Compare with similar skills
Writing Reference Docs 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 Reference Docs this skillBuilderIO/agent-native | 7.1k | — | ~3.5k | Automated safety check: Pass | None | |
| ISO 24495 Text AuditGaZmagik/iso-24495 | 189 | 1 repos | ~817 | Automated safety check: Pass | MIT | |
| Moai Domain HTML Reportmodu-ai/moai-adk | 1.2k | — | ~6.4k | Automated safety check: Notes | Apache-2.0 | |
| Pnasnexus Significancebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Rational Red Blue Debatedigoal/blog | 8.6k | — | ~2.2k | Automated safety check: Pass | GPL-2.0 | |
| Markdown Document StructurerArabelaTso/Skills-4-SE | 253 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Moai Domain HTML Report
modu-ai/moai-adk
Markdown-to-single-file-HTML report renderer. An agent skill from modu-ai/moai-adk.
Pnasnexus Significance
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters.
Rational Red Blue Debate
digoal/blog
Answer general or cross-domain questions with a non-pleasing rational mode: adversarial red-team and blue-team expert analysis, mutually exclusive conclusions, up to five debate rounds, saved…
Markdown Document Structurer
ArabelaTso/Skills-4-SE
Reorganizes markdown documents into well-structured, consistent format while preserving content and improving readability.
Suiko
nwiizo/suiko
日本語文書のAI由来の均一さ、翻訳調、不自然さ、論旨、読解負荷を、決定的なRust CLIと目視で診断し、依頼に応じて書く・直す。日本語の学術論文・研究報告では、中心命題、用語、論証、DOCX/PDF納品を監査契約で確認する。Use when the user explicitly mentions suiko, asks whether Japanese text looks…
More from BuilderIO/agent-native
All 102 skills in this repoActions
BuilderIO/agent-native
How to create and run agent actions. An agent skill from BuilderIO/agent-native.
Client Methods
BuilderIO/agent-native
Client method surface rules. An agent skill from BuilderIO/agent-native.
Adding A Feature
BuilderIO/agent-native
The four-area checklist every new feature must complete. An agent skill from BuilderIO/agent-native.
Address Feedback
BuilderIO/agent-native
Triage feedback from docs, issues, Slack threads, or pasted notes into verified bugs, UX proposals, unclear questions, and skipped noise.
Audit Log
BuilderIO/agent-native
Durable, access-scoped, append-only record of who changed what app data, when, and whether it was the agent or a human.
Automations
BuilderIO/agent-native
Event-triggered and schedule-triggered automations with natural-language conditions.
Related
Categories
Questions about Writing Reference Docs
What does Writing Reference Docs do?
How to write a function/hook/action reference section, and how to write or rework a whole app's multi-page doc set (Overview/Features/Talk to the Agent/Cross-App Use/Developer Guide): plain-language…. Writing Reference Docs is an agent skill from BuilderIO/agent-native. How to write a function/hook/action reference section, and how to write or rework a whole app's multi-page doc set (Overview/Features/Talk to the Agent/Cross-App Use/Developer Guide): plain-language signature, real arguments, escalating examples grounded in a real app, verified agent behavior, trimmed prose with no em dashes or semicolons.
When should I use Writing Reference Docs?
Writing Reference Docs fits situations like: editing a packages/core/docs/content reference page; reworking a template-<app.mdx doc set.
How do I install Writing Reference Docs in Claude Code?
Run `npx skills add BuilderIO/agent-native --skill writing-reference-docs -a claude-code`. Or copy the skill folder (.agents/skills/writing-reference-docs in BuilderIO/agent-native) into .claude/skills/writing-reference-docs in your project. Claude Code loads it when a task matches its description.
How do I install Writing Reference Docs in Codex?
Run `npx skills add BuilderIO/agent-native --skill writing-reference-docs -a codex`. Or copy the skill folder (.agents/skills/writing-reference-docs in BuilderIO/agent-native) into .agents/skills/writing-reference-docs in your project. Codex loads it when a task matches its description.
Can I use Writing Reference Docs 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 BuilderIO/agent-native --skill writing-reference-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/writing-reference-docs, .gemini/skills/writing-reference-docs, .github/skills/writing-reference-docs and .opencode/skills/writing-reference-docs in your project.
What does Writing Reference Docs need to run?
Going by SKILL.md and its folder, Writing Reference Docs needs the command-line tools its instructions call (pnpm).
Does Writing Reference Docs 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 Writing Reference Docs 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 Writing Reference Docs use?
No licence was found for Writing Reference Docs or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Writing Reference Docs use?
About 3.5k tokens (SKILL.md is roughly 14k 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 Writing Reference Docs?
Skills that share tags, products or a category with Writing Reference Docs: ISO 24495 Text Audit (GaZmagik/iso-24495, 189 stars), Moai Domain HTML Report (modu-ai/moai-adk, 1.2k stars), Pnasnexus Significance (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Rational Red Blue Debate (digoal/blog, 8.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Reference Docs?
BuilderIO (a GitHub organization) maintains it in BuilderIO/agent-native, which has 7,087 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 8, 2026.
Source: BuilderIO/agent-native on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.