Навыки write-feature-docs

📦

write-feature-docs

Name: write-feature-docs
Author: warpdotdev

Ревизия содержимого r1 Высокий риск ⚙️ Внешние команды🌐 Доступ к сети📁 Доступ к файловой системе🔑 Переменные окружения

Draft Warp Feature Documentation

Feature specifications do not automatically become accurate, publishable documentation. This skill verifies implementation details, confirms audience and structure, drafts MDX, and prepares a reviewable pull request.

Поддерживает: Claude Codex Code(CC)

⚠️ 38 Плохо

Остановитесь и запросите подтверждение перед установкой.

Проверьте план и получите явное согласие пользователя перед изменением файлов.

Установить с помощью моего Агента

Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.

Запрос агента

Review the Skillstore skill "write-feature-docs" from https://skillstore.io/skills/warpdotdev-write-feature-docs.md and its manifest at https://skillstore.io/api/skills/warpdotdev-write-feature-docs/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.

Ресурсы для AI-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Markdown-детали GET /skills/warpdotdev-write-feature-docs.md Подписанный manifest GET /api/skills/warpdotdev-write-feature-docs/manifest Подписанный lockfile GET /api/skills/warpdotdev-write-feature-docs/lockfile

Протестировать

Использование «write-feature-docs». Document APP-1234 from its product and technical specifications.

Ожидаемый результат:

A confirmed content design plan, a concise outline with verification labels, and a complete MDX feature page ready for review.

Использование «write-feature-docs». Create documentation for a shipped feature that has no specification.

Ожидаемый результат:

A research summary, targeted questions for unresolved behavior, and a documentation draft based on confirmed repository evidence.

Использование «write-feature-docs». Update the existing Agent Mode page and prepare a draft pull request.

Ожидаемый результат:

An updated MDX page following Warp style and template rules.
Validated screenshots or explicit reviewer placeholders.
A draft pull request containing the content plan and unresolved review items.

Аудит безопасности

Высокий риск

v1 • 04.09.2026 Открыть версионный отчет

Most detections are Markdown backticks, code fences, relative links, or benign GitHub examples and are false positives. The fixed pull request body path creates a local tampering risk, and optional UI capture can expose sensitive data when images enter a public documentation change. No prompt injection or malicious intent was found.

Просканировано файлов

464

Проанализировано строк

Пункты проверки

Ложные срабатывания проигнорированы

Подтверждённые проблемы безопасности (1)

Высокий

SKILL.md:19

Screen capture upload

5.5. Attempt screenshot capture via computer use (if available)

The skill directs computer-use capture of product UI and later places accepted images in a public documentation change. Its privacy checklist reduces, but cannot eliminate, accidental disclosure.

Пункты проверки возможностей (2)

Это реальные локальные возможности, которые могут ожидаться для этого навыка, поэтому они требуют проверки, но не считаются подтверждённым вредоносным поведением.

Средний

SKILL.md:411

Temp directory access

Write the body to `/tmp/pr-body.md` using whatever file-writing method is available (a file-creation

The workflow writes sensitive pull request content to a fixed shared path, /tmp/pr-body.md. A stale file or symbolic-link race could alter content or overwrite another writable target.

Средний

SKILL.md:413

Temp directory access

gh pr create --draft --body-file /tmp/pr-body.md ...

The command uploads content from the predictable /tmp/pr-body.md path. Another local process could replace that file before gh reads it, causing unintended pull request content.

Факторы риска

⚙️ Внешние команды (50)

🌐 Доступ к сети (2)

SKILL.md:69 SKILL.md:72

📁 Доступ к файловой системе (5)

SKILL.md:214 SKILL.md:215 SKILL.md:358 SKILL.md:411 SKILL.md:413

🔑 Переменные окружения (1)

SKILL.md:102

Обнаруженные паттерны

Screen capture upload

Аудитор:: codex

Поделиться и цитировать этот отчет

Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.

Открыть версионный отчет

Копировать ссылку на отчёт

https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Значок Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/warpdotdev-write-feature-docs/security.svg)](https://skillstore.io/skills/warpdotdev-write-feature-docs?utm_source=security_passport_badge)

Значок HTML

<a href="https://skillstore.io/skills/warpdotdev-write-feature-docs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-write-feature-docs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Встраиваемая карточка

<iframe src="https://skillstore.io/embed/skills/warpdotdev-write-feature-docs.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Академические ссылки (APA · BibTeX · CFF)

Цитата APA

warpdotdev. (2026). write-feature-docs security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1

Цитата BibTeX

@techreport{warpdotdev-warpdotdev-write-feature-docs-2026,
  author = {warpdotdev},
  title = {write-feature-docs security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "write-feature-docs security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "warpdotdev"
date-released: "2026-09-04"
url: "https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1"
identifiers:
  - type: other
    value: "skillstore:warpdotdev-write-feature-docs:audit:1"
    description: "Skillstore immutable audit report identifier"

Оценка Skillstore

Почему такая оценка Достоверность доказательств: Средний

Архитектура

Сопровождаемость

Контент

Сообщество

Соответствие спецификации

Что вы можете построить

Document a shipped feature

Convert an approved product or technical specification into an accurate first-pass documentation page.

Reduce documentation research

Verify implementation details and isolate only the questions that require subject matter expertise.

Prepare a reviewable update

Create or update an MDX page and open a structured draft pull request for editorial review.

Попробуйте эти промпты

Draft from a specification

Draft documentation for Warp feature [name] using spec [ID]. Find PRODUCT.md and TECH.md, then present the content design plan.

Research a feature without a spec

Research feature [name] without a spec. Verify behavior in [repository], identify unknowns, and ask only targeted questions before planning the page.

Update an existing page

Document [feature] using [spec ID]. Prefer updating [existing page], verify UI paths, then present the content plan and outline separately.

Prepare the full review workflow

Prepare a draft documentation pull request for [feature]. Verify release readiness, sanitize screenshots, list unverified claims, and include the confirmed content design plan.

Лучшие практики

Keep the engineer present for separate content plan and outline confirmations.
Validate feature and specification tokens before using them in shell or GitHub searches.
Mark unresolved claims clearly and exclude confidential implementation details from public drafts.

Избегать

Do not run the workflow unattended or combine the two required confirmation stages.
Do not publish technical specification details before an engineer confirms they are public.
Do not include screenshots containing private repositories, credentials, personal information, or customer data.

Часто задаваемые вопросы

Does this skill work without a product specification?

Yes. It researches the relevant repository first, then asks targeted questions about gaps that code cannot resolve.

Can this skill run automatically after every release?

No. It requires an interactive engineer. Warp uses the separate missing_docs workflow for release-triggered documentation.

Which documentation formats does it produce?

It produces MDX pages based on Warp templates for feature, conceptual, procedural, reference, troubleshooting, quickstart, or guide content.

How does it protect confidential technical information?

It flags internal implementation details from TECH.md and requires engineer confirmation before including them in public documentation.

Are screenshots required?

No. Screenshot capture is optional. Failed, unavailable, unsafe, or unverified captures remain explicit placeholders for a documentation reviewer.

What access does the workflow require?

It needs relevant repository access and GitHub CLI authentication. Screenshot capture also needs an available computer use tool.

Сведения для разработчиков

Автор

warpdotdev

Лицензия

MIT

Ревизия Skillstore

Примечание о версии

Автор не указал версию.

Репозиторий

https://github.com/warpdotdev/common-skills/tree/b811c24365ae505bfc9646458957b886e29110b5/.agents/skills/write-feature-docs

Ссылка

e5464e662405de6361fdde6b984f9ea865635f64

Актуальность поддержки

08.09.2026

Использование

0 загрузок · 0 просмотров

Структура файлов

📄 SKILL.md