← 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": "Start researching, writing or editing with Research & Writing Copilot; identify the right focused workflow for a topic, notes, draft, article, report or publication target.",
"included_files": [],
"name": "get-started",
"skill_md_contents": "---\nname: get-started\ndescription: Start researching, writing or editing with Research & Writing Copilot; identify the right focused workflow for a topic, notes, draft, article, report or publication target.\n---\n\n# Get Started\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## Route the user's goal\nIdentify one primary result, not an inventory of every possible writing task.\n- Question or topic requiring facts → `research-question` then `deep-research` when substantial.\n- Link, paper or evidence requiring assessment → `verify-sources` or `literature-review`.\n- Existing draft with possible errors → `fact-check-draft`; wording/style only → `edit-for-clarity`.\n- Version, pricing or policy update → `refresh-existing-content`.\n- Research synthesis → `synthesize-evidence` and `write-research-report`.\n- Technology decision → `technology-comparison`.\n- Technical article → `write-technical-article`.\n- Docs/how-to → `write-documentation`; learning explainer → `write-explainer`.\n- Medium/LinkedIn adaptation → `adapt-for-publication`.\n- Multi-deliverable request → `build-content-package`.\n- Final quality gate → `review-publication`.\n## Execution rules\nIdentify audience, requested artifact, time scope and material constraints from available context. When the user supplied a draft or file, read it before proposing a rewrite. Do not force deep web research for simple rewriting of provided text. If no browsing tools exist, describe scope and evidence limitations rather than asserting current facts. Make a useful deliverable immediately when possible.\n## Deliver\nOne completed artifact or the most useful next step, with actual citations and explicit unresolved gaps where needed.\n\n## Related references\n- Read `../../references/workflow-routing.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: 9369510cfa8cb9e580743e48c0fe650f6587f4f8f11bb5850bc6dbf59a819aa7