Menu

Individual skill

write-page

0upvotes

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/Codex/plugins/pages/skills/write-page/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
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,245
Repository last updated
Nov 10, 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.

**Required before any Page edit:** read [Edit requests](references/edit-requests.md) in full and the selected tool's active schema before calling `edit_page` or `patch_page`. This includes small wording fixes, title changes, structural edits and recovery edits.

Read linked references only when their workflow applies. Read each needed reference and tool definition separately, not the whole skill and tool catalog in one output. If an output is clipped, retrieve the missing relevant instructions before writing.

## 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.
Back to top