doc-coauthoring
Coauthor Clear Documents with Structured Review
Important documents often fail because context, structure, and reader assumptions remain unclear. This skill guides collaborative drafting, focused revision, and reader testing through a repeatable three-stage workflow.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "doc-coauthoring" from https://skillstore.io/skills/sickn33-doc-coauthoring.md and its manifest at https://skillstore.io/api/skills/sickn33-doc-coauthoring/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "doc-coauthoring". Create a decision document for adopting a managed event queue.
Expected outcome:
Decision: Adopt a managed event queue. Context explains current delivery failures. Options compare cost, ownership, and reliability. The recommendation records risks, mitigations, and success measures.
Using "doc-coauthoring". Help structure an RFC for replacing session storage.
Expected outcome:
The RFC covers goals, current constraints, proposed architecture, migration steps, failure handling, observability, security considerations, alternatives, and open questions.
Using "doc-coauthoring". Test whether new engineers can understand this deployment guide.
Expected outcome:
Reader testing finds unclear prerequisites and an undefined rollback condition. The revised guide adds access requirements, verification steps, rollback ownership, and expected recovery time.
Security Audit
SafeAll eight static findings are false positives caused by Markdown tool names, a legitimate Claude URL, and ordinary documentation prose. No malicious command execution, network reconnaissance, prompt injection, or data exfiltration intent was found.
Risk Factors
⚙️ External commands (6)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-doc-coauthoring/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-doc-coauthoring?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-doc-coauthoring?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-doc-coauthoring/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-doc-coauthoring.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). doc-coauthoring security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-doc-coauthoring/audits/5BibTeX citation
@techreport{sickn33-sickn33-doc-coauthoring-2026,
author = {sickn33},
title = {doc-coauthoring security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-doc-coauthoring/audits/5},
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: "doc-coauthoring security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-doc-coauthoring/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-doc-coauthoring:audit:5"
description: "Skillstore immutable audit report identifier"
Compare variants
7 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
zhanlincui-doc-coauthoring
2026-08-21
doc-coauthoring
2026-08-21
7spade-doc-coauthoring
2026-08-21
sickn33-doc-coauthoring
2026-08-21
astrabit-cpt-doc-coauthoring
2026-08-21
davila7-doc-coauthoring
2026-08-21
azeem-2-doc-coauthoring
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Draft a Product Requirements Document
Build a product requirements document that aligns goals, constraints, stakeholders, and acceptance criteria.
Develop a Technical RFC
Develop an RFC or technical specification with explicit trade-offs, dependencies, risks, and unresolved questions.
Record a Team Decision
Create a decision record or proposal that explains context, alternatives, rationale, and expected impact.
Try These Prompts
Help me coauthor a [document type] for [audience]. The desired outcome is [outcome]. Start by asking me the essential context questions.
I have a draft of [document]. Review its structure and ask questions about missing context. Then help me revise one section at a time.
Use this template: [template]. Gather context from the materials I provide and propose a section order. Identify the section with greatest uncertainty. For each section, brainstorm options before drafting. Apply only the changes I approve.
Coauthor an executive decision document from [context]. Track unresolved assumptions and stakeholder concerns during drafting. After revision, test the document with a fresh sub-agent. Report comprehension gaps, repair affected sections, and repeat testing until the stated exit criteria pass.
Best Practices
- Provide the audience, desired outcome, constraints, and source materials before drafting begins.
- Give specific feedback about what to keep, remove, combine, or clarify after each section.
- Verify facts, links, permissions, and technical claims before approving the final document.
Avoid
- Do not request a polished final document before sharing essential context.
- Do not grant integrations broader access than the document task requires.
- Do not treat fresh-reader feedback as a substitute for domain expert review.