Individual skill
write-page
Create or edit requested Page/Space content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.
OpenAI/dots/skills/write-page/SKILL.md
Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 71,156
- Repository last updated
- Nov 9, 2026
- License
- CC0-1.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Write and edit a page
Follow the user's voice, length, structure, presentation, and applicable Page/Space instructions. For requests to review existing content or draft or suggest changes, return feedback or a proposal; apply changes only when requested.
## Titles and opening
Title clarity is an absolute requirement. State the specific subject and purpose so the reader understands what the Page is for before reading the body. Use plain descriptive language with no slogans. Apply this to Page titles, subtitles, and section headings. Use only words, numbers, and spaces, except punctuation required by names or established terms such as C++, .NET, Q&A, or GPT-5.6. Use the native Page title and headings; do not add decorative lines beneath them.
Preserve titles the user explicitly requests and meaningful status such as Draft. Use the Page title as the document title; do not repeat it as the body's opening heading.
The opening content is essential to the reader's understanding of the whole Page. Establish what the Page covers, why it matters to this reader, and the main conclusion, decision, or task. Give enough context and scope to make the sections that follow easy to understand and show what the reader should learn or do.
## Writing quality
