ワンクリックでManusで任意のスキルを実行

draft-reference

スター39

フォーク17

更新日2026年5月5日 02:37

Draft a new reference documentation page or update an existing one. Use for structured factual information meant for lookup — CLI commands, API endpoints, configuration options, keyboard shortcuts, error codes. Reference pages describe and only describe.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

warpdotdev

warpdotdev/docs

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Draft reference page

Draft a reference documentation page with structured, exhaustive information for developer lookup.

Workflow

Follow the workflow in .warp/skills/draft_docs/SKILL.md, using the reference template at .warp/templates/reference.md.

Content type rules

These rules are specific to reference pages (from the "Drafting by content type" section of AGENTS.md):

Be exhaustive — document every option, flag, and configuration value.
Use consistent formatting for parameters (e.g., --flag in backticks, description as a dash-separated list item).
Alphabetize entries where ordering doesn't matter.
Keep descriptions factual and concise — this is for lookup, not learning.
Include at least one practical example for each command or endpoint.
Adopt standard patterns ruthlessly — consistency is more important than style. Every entry must follow the same structure.
Structure should mirror the structure of the product it describes.
Use H2 for sections, H3 for subsections. Tables for multiple elements, lists for single.
Title convention: noun describing contents ("Keyboard shortcuts", "CLI commands")

Heading case

All headings (H1–H4) must use sentence case: capitalize only the first word and proper feature names.

✅ # CLI commands
✅ ## Running agents
❌ # CLI Commands
❌ ## Running Agents

Existing examples

Read 2-3 of these strong examples to match the existing pattern:

reference/cli/index.mdx
reference/api-and-sdk/index.mdx

このリポジトリの他の Skills

同じリポジトリ

sync-error-docs

warpdotdev/docs

Detect new platform error codes in warp-server that are missing documentation pages in the docs repo. Creates doc pages, astro.config.mjs (sidebar config) entries, and redirects for any gaps. Use on a weekly schedule or when error codes change.

2026-07-1039

sync-openapi-spec

warpdotdev/docs

Sync the public Oz Agent API OpenAPI spec from warp-server into the docs repo, regenerating `developers/agent-api-openapi.yaml` (the file that powers the Scalar API reference at `docs.warp.dev/api`). Use when the warp-server public API has changed, when the Scalar reference looks stale, or on a scheduled cadence to keep the public API docs aligned with the canonical spec.

2026-07-1039

sync-terminology

warpdotdev/docs

Sync the Warp terminology glossary from the Notion Dictionary to the repo. Fetches the Notion Dictionary page, compares with .warp/references/terminology.md, and opens a PR for any additions or changes. Flags repo-only terms that are missing from Notion. Use on a weekly schedule or manually when terminology changes.

2026-07-1039

update-changelog

warpdotdev/docs

Update the public changelog at docs.warp.dev/changelog with the latest stable release. Fetches changelog data from channel-versions, formats a new entry, and opens a PR. Use after a stable release ships (typically Fridays).

2026-07-1039

afdocs-audit

warpdotdev/docs

Audit docs.warp.dev for agent-friendly documentation issues using the AFDocs scorecard. Checks llms.txt, markdown availability, content negotiation, page size, URL stability, and content structure. Use when asked to check agent readiness, run an AFDocs audit, improve the docs score, or verify llms.txt and markdown support.

2026-07-1039

release-updates

warpdotdev/docs

Run weekly release docs updates with standalone scripts for changelog, licenses, and telemetry, plus Linux/Oz Warp artifact preparation. Defaults to running all tasks in order, and supports running only selected tasks.

2026-07-0939

name	draft_reference
description	Draft a new reference documentation page or update an existing one. Use for structured factual information meant for lookup — CLI commands, API endpoints, configuration options, keyboard shortcuts, error codes. Reference pages describe and only describe.

Draft reference page

Draft a reference documentation page with structured, exhaustive information for developer lookup.

Workflow

Follow the workflow in .warp/skills/draft_docs/SKILL.md, using the reference template at .warp/templates/reference.md.

Content type rules

These rules are specific to reference pages (from the "Drafting by content type" section of AGENTS.md):

Be exhaustive — document every option, flag, and configuration value.
Use consistent formatting for parameters (e.g., --flag in backticks, description as a dash-separated list item).
Alphabetize entries where ordering doesn't matter.
Keep descriptions factual and concise — this is for lookup, not learning.
Include at least one practical example for each command or endpoint.
Adopt standard patterns ruthlessly — consistency is more important than style. Every entry must follow the same structure.
Structure should mirror the structure of the product it describes.
Use H2 for sections, H3 for subsections. Tables for multiple elements, lists for single.
Title convention: noun describing contents ("Keyboard shortcuts", "CLI commands")

Heading case

All headings (H1–H4) must use sentence case: capitalize only the first word and proper feature names.

✅ # CLI commands
✅ ## Running agents
❌ # CLI Commands
❌ ## Running Agents

Existing examples

Read 2-3 of these strong examples to match the existing pattern:

reference/cli/index.mdx
reference/api-and-sdk/index.mdx