Menu

Individual skill

docs-artifact

0upvotes

Use when creating, editing, or reviewing a document for the user (Word, Google Docs, or a document delivered as PDF), or when the task calls for a standalone written deliverable such as a memo, report, proposal, or brief. Also use to answer questions that require inspecting an existing document; not for a short chat reply, message draft, or quick rewrite that can stay in chat.

OpenAI/dots/skills/docs-artifact/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
Yes
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,238
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

# Document Artifacts

Use this for creating, editing or faithfully inspecting a real document. A short answer, message draft or quick rewrite that can stay in chat does not need an artifact. A question about an existing document does not authorize changing it.

## Reasoning effort for new artifacts

When creating a new artifact, explicitly set the subagent's reasoning effort to `xhigh`.

## Start with the shared skill

- Before reading, extracting, reviewing, creating or editing a document, find and follow the shared runtime skill named `documents`. If `skills.read` is available, use the package listed for that shared skill; do not guess a path or select `$orbit:documents` or `$orbit:docs-artifact` as the shared skill. Give it the request, sources, output and relevant dot context. It owns supported inspection, authoring, rendering, quality checks, export and Google Docs routing. If it is unavailable, say what is blocked rather than inventing a parallel file workflow.
- Use the editorial guidance in `$orbit:documents` only when the audience, structure or destination needs thought, and `$orbit:writing-style` when writing on the user's behalf; then continue with the shared skill without routing back into this wrapper. Pass along the template or known relevant conventions. Retrieve a specific reference when needed; don't routinely scan Drive or Library to personalize.

## Make and deliver it
Back to top