write-feature-docs SKILL.md skillA
write-feature-docs from aiskillstore/marketplace is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aiskillstore/marketplace/write-feature-docs@git:20260904.3309fadPins git:20260904.3309fad in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aiskillstore/marketplace
- Path
pending/warpdotdev/write-feature-docs/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260904.3309fad, committed Sep 4, 2026
- Size
- 28,443 bytes
- Repository stars
- 471
- License
- none declared
Draft a complete documentation page for a new Warp feature from its PRODUCT.md and/or TECH.md spec. Use when an engineer has written a spec and needs to produce a first-pass MDX draft for the warpdotdev/docs repo. Also handles features without specs by researching the codebase first. Invoke this skill whenever an engineer mentions writing docs for a feature, drafting a docs page, creating feature documentation, starting the eng-docs workflow, or converting a spec into documentation. Requires…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# write-feature-docs Draft a complete documentation page for a new Warp feature. You read the feature's spec, verify technical claims by researching the codebase yourself, confirm the content design plan and then the outline with the engineer, and only then produce a complete MDX draft and open a draft PR in `warpdotdev/docs` — tagging the docs team for review. The engineer's job is to confirm what you couldn't verify from the spec and code — not to do a full accuracy review, not to polish prose, not to know docs conventions. ## The workflow 1. Find and read the spec files 2. Research the codebase to verify technical claims — minimize what the engineer needs to check 3. Present the content design plan and wait for confirmation — who the page is for 4. Present the outline and wait for confirmation — what the page will contain 5. Generate the complete MDX draft 5.5. Attempt screenshot capture via computer use (if available) 6. Open a draft PR in `warpdotdev/docs` and tag the docs team …
Read the whole file at its exact version.
How to install
mdr add aiskillstore/marketplace/write-feature-docs@sha256:2a5a5de2943a438bThe line at the top of this page pins the label git:20260904.3309fad, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_u267tcpafbwwjai3)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 4, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (28443 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
aiskillstore/marketplace · 471 stars · license none declared · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_u267tcpafbwwjai3 GET https://markdownregistry.com/api/v1/resolve?ref=aiskillstore/marketplace/write-feature-docs GET https://markdownregistry.com/api/v1/blob/2a5a5de2943a438b08807c43c471c27d330796a314e5ae3382c63b01aee2369a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.