← Research & Writing CopilotCONTENT HISTORY
WHAT CHANGED
Update to Research & Writing Copilot
Snapshot Nov 3, 2026 · 18:48 UTC · version 0.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Research & Writing Copilot and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Create or revise technical documentation, tutorials, quickstarts, API guides, migration instructions and runbooks.",
"included_files": [],
"name": "write-documentation",
"skill_md_contents": "---\nname: write-documentation\ndescription: Create or revise technical documentation, tutorials, quickstarts, API guides, migration instructions and runbooks.\n---\n\n# Write Documentation\n\n**Shared standards.** Preserve the user's purpose and existing material; never fabricate evidence, URLs, quotations, citations, first-person experiences, interviews, tool runs or publication. Distinguish sourced observations from independent reproduction and analysis. Use actual host research/files/code tools when available; disclose unavailable verification. For current facts, verify fresh authoritative sources. Ask only when an essential constraint prevents useful work.\n\n## Procedure\n1. Identify document type: concept, tutorial, how-to, reference, troubleshooting, architecture, migration or runbook. Define target reader and expected completion outcome.\n2. Read user-provided code and docs before asserting commands, environment variables or API semantics. Verify current behavior against official docs/source when possible.\n3. For procedures: prerequisites → starting state → exact ordered steps → expected checks → failure modes → recovery/rollback for consequential changes.\n4. Separate runnable commands, placeholders and illustrative output. Never expose secrets or present untested commands as executed.\n5. Verify links, version-specific behavior, navigation and consistency. Keep docs task-oriented, not an article with marketing adjectives.\n## Deliver\nComplete appropriately structured document, including validation steps and clear unknowns where runtime or source cannot be inspected.\n\n## Related references\n- Read `../../references/documentation-patterns.md` when it materially informs this task.\n- Read `../../references/technical-examples.md` when it materially informs this task.\n- Read `../../references/evidence-policy.md` when it materially informs this task.\n"
}SHA-256 of public snapshot: cebbf85c1117dc13d207a329c67282fdc6ae589ba6ca1c3dd18d2b35f58b0208