원클릭으로 Manus에서 모든 스킬 실행

draft-quickstart

스타0

포크1

업데이트2026년 5월 10일 14:46

Draft a new quickstart documentation page or update an existing one. Use for first-time experiences that get the reader to a working result fast (~10 minutes). Quickstarts focus on the critical path with minimal prerequisites and link to deeper guides for edge cases.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

slax-lab

slax-lab/slax-home

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Draft quickstart page

Draft a quickstart that gets the reader from zero to a working result in about 10 minutes.

Workflow

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

Content type rules

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

Give every quickstart a descriptive H1 title. Don't use a bare "Quickstart" — include the feature or topic name.
Minimize prerequisites — the reader should be able to start quickly.
Target ~10 minutes or less.
Keep steps focused on the critical path — defer edge cases and advanced options to other pages.
Steps can be less formal than full procedural content. Use heavy visual cues (code blocks, screenshots).
All procedural rules apply (focused steps, motivate steps, expected outcomes).
End with 2-3 actionable next steps linking to deeper content.
Title convention: "[Feature] quickstart" or "Quickstart for [product]"

Heading case

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

✅ # Cloud Agents quickstart
✅ ## Running your first cloud agent
❌ # Cloud Agents Quickstart
❌ ## Running Your First Cloud Agent

Existing examples

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

src/content/docs/agent-platform/cloud-agents/quickstart.md
src/content/docs/getting-started/quickstart/installation-and-setup.md

이 저장소의 다른 Skills

같은 저장소

afdocs-audit

slax-lab/slax-home

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-05-100

answer-question

slax-lab/slax-home

Answer questions about Warp, Oz, agents, terminal features, billing, pricing, troubleshooting, privacy, skills, MCP, integrations, or any other Warp-related topic. Use when a user, support person, or engineer asks a question that can be answered from Warp's documentation. Searches the docs, synthesizes a comprehensive answer, and provides links to relevant doc pages.

2026-05-100

check-for-broken-links

slax-lab/slax-home

Check the Warp Astro Starlight documentation for broken links by scanning source markdown files. Run the diagnostic script, review the output, fix broken links, and optionally notify Slack.

2026-05-100

create-pr

slax-lab/slax-home

Create a pull request in the docs repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing documentation for merge.

2026-05-100

docs-seo-audit

slax-lab/slax-home

Audit docs.warp.dev for SEO issues like duplicate titles, missing meta descriptions, title length problems, and H1 tag issues. Crawls the live sitemap, generates a report, and fixes issues in the source markdown. Use when asked to check SEO, fix duplicate titles, audit meta tags, improve search rankings, or run an SEO check on the docs site.

2026-05-100

draft-conceptual

slax-lab/slax-home

Draft a new conceptual documentation page or update an existing one. Use for pages that explain what something is, why it exists, and how it works — without step-by-step procedures. Examples include product overviews, architecture explanations, and design philosophy pages.

2026-05-100

name	draft_quickstart
description	Draft a new quickstart documentation page or update an existing one. Use for first-time experiences that get the reader to a working result fast (~10 minutes). Quickstarts focus on the critical path with minimal prerequisites and link to deeper guides for edge cases.

Draft quickstart page

Draft a quickstart that gets the reader from zero to a working result in about 10 minutes.

Workflow

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

Content type rules

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

Give every quickstart a descriptive H1 title. Don't use a bare "Quickstart" — include the feature or topic name.
Minimize prerequisites — the reader should be able to start quickly.
Target ~10 minutes or less.
Keep steps focused on the critical path — defer edge cases and advanced options to other pages.
Steps can be less formal than full procedural content. Use heavy visual cues (code blocks, screenshots).
All procedural rules apply (focused steps, motivate steps, expected outcomes).
End with 2-3 actionable next steps linking to deeper content.
Title convention: "[Feature] quickstart" or "Quickstart for [product]"

Heading case

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

✅ # Cloud Agents quickstart
✅ ## Running your first cloud agent
❌ # Cloud Agents Quickstart
❌ ## Running Your First Cloud Agent

Existing examples

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

src/content/docs/agent-platform/cloud-agents/quickstart.md
src/content/docs/getting-started/quickstart/installation-and-setup.md