write-feature-docs
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.
Pare e solicite confirmação antes de instalar.
Revise o plano e obtenha o consentimento explícito do usuário antes de alterar arquivos.
Instalar com meu Agente
Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.
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.Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.
Recursos legíveis por agentes
Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.
Testar
Usando "write-feature-docs". Document APP-1234 from its product and technical specifications.
Resultado esperado:
A confirmed content design plan, a concise outline with verification labels, and a complete MDX feature page ready for review.
Usando "write-feature-docs". Create documentation for a shipped feature that has no specification.
Resultado esperado:
A research summary, targeted questions for unresolved behavior, and a documentation draft based on confirmed repository evidence.
Usando "write-feature-docs". Update the existing Agent Mode page and prepare a draft pull request.
Resultado esperado:
- 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.
Auditoria de segurança
Risco altoMost 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.
Preocupações de segurança confirmadas (1)
Itens de revisão de capacidade (2)
Estas são capacidades locais reais que podem ser esperadas para esta habilidade, portanto exigem revisão, mas não são contabilizadas como comportamento malicioso confirmado.
Fatores de risco
⚙️ Comandos externos (50)
🌐 Acesso à rede (2)
📁 Acesso ao sistema de arquivos (5)
🔑 Variáveis de ambiente (1)
Padrões detectados
Compartilhar e citar este relatório
Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.
Copiar link do relatório
https://skillstore.io/skills/warpdotdev-write-feature-docs/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/warpdotdev-write-feature-docs?utm_source=security_passport_badge)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>Cartão incorporável
<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>Citações acadêmicas (APA · BibTeX · CFF)
Citação 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/1Citação 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"
Pontuação do Skillstore
Por que esta pontuação Confiança das evidências: MédioO que você pode criar
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.
Teste estes prompts
Draft documentation for Warp feature [name] using spec [ID]. Find PRODUCT.md and TECH.md, then present the content design plan.
Research feature [name] without a spec. Verify behavior in [repository], identify unknowns, and ask only targeted questions before planning the page.
Document [feature] using [spec ID]. Prefer updating [existing page], verify UI paths, then present the content plan and outline separately.
Prepare a draft documentation pull request for [feature]. Verify release readiness, sanitize screenshots, list unverified claims, and include the confirmed content design plan.
Boas práticas
- 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.
Evitar
- 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.
Perguntas frequentes
Does this skill work without a product specification?
Can this skill run automatically after every release?
Which documentation formats does it produce?
How does it protect confidential technical information?
Are screenshots required?
What access does the workflow require?
Detalhes do desenvolvedor
Autor
warpdotdevLicença
MIT
Revisão da Skillstore
r1
Aviso de versão
O autor não declarou uma versão.
Referência
e5464e662405de6361fdde6b984f9ea865635f64
Atualidade da manutenção
08/09/2026
Uso
0 downloads · 0 visualizações
Estrutura de arquivos
📄 SKILL.md