Update to Version Story Redline Compare
Snapshot Oct 24, 2026 · 13:14 UTC · version 0.33.0
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for merge
Full description — Now says: separately edited copies of one original document into one Word document, with each revision's edits as tracked changes labeled by who made them. Use when...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Sep 30, 2026 · 23:10 UTC
parallel revisions of the same original into one Word document with attributed tracked changes. Use when reviewers edited separate copies of a shared base.
Oct 24, 2026 · 13:14 UTC
separately edited copies of one original document into one Word document, with each revision's edits as tracked changes labeled by who made them. Use when several people edited copies of the same base document.
Skill instructions
Sep 30, 2026 · 23:10 UTC
Merge two or more parallel revisions of the same original into one Word document with attributed tracked changes. Use when reviewers edited separate copies of a shared base. # Merge parallel revisions 1. Identify one original and at leas...
Oct 24, 2026 · 13:14 UTC
"Merge two or more separately edited copies of one original document into one Word document, with each revision's edits as tracked changes labeled by who made them. Use when several people edited copies of the same base document." Call V...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,32 +1,6 @@ --- name: merge -description: Merge two or more parallel revisions of the same original into one Word document with attributed tracked changes. Use when reviewers edited separate copies of a shared base. +description: "Merge two or more separately edited copies of one original document into one Word document, with each revision's edits as tracked changes labeled by who made them. Use when several people edited copies of the same base document." --- -# Merge parallel revisions - -1. Identify one original and at least two revisions of it. Ask which draft everyone - started from when the shared base is unclear. If the drafts were written - independently, use the combine workflow. If they form a chronological chain, - use version history. -2. Confirm the author labels for the revisions. Do not guess authors. Revision order - does not change the result, so do not ask the user to order parallel edits. -3. Call `get_instructions`, then `create_merge`, passing attached files in `base_file` - and `next_version_files` (or accessible file paths), original file names, and the - confirmed `next_version_authors`. -4. Follow the upload instructions if the result asks for uploads, then call - `get_merged_document` until generation finishes. -5. Download and present the Word document in the conversation with its interactive - link. The user resolves competing tracked changes in Word. Use `read_text` only - when the user requests analysis. - -Excel is unsupported for this workflow. Explain that limitation before starting. - -Selected documents are uploaded to Version Story and stored in the user’s account. -Follow the user’s explicit instructions. Use only files they selected and that this -session can access. Complete OAuth through the host’s sign-in flow; never request -passwords or tokens in chat. If files are unavailable, ask the user to attach them. - -When a transfer or tool call fails, report it with `report_issue`, omitting document -contents and credentials, then explain the failure and stop. If the account limit is -reached, tell the user, give them the upgrade link from the message, and stop. +Call Version Story's `create_merge` tool. Its description says how to call it, and the message in each result says what to do next: follow them.
Full technical diff · 2 changed fields
changed /description
"Merge two or more parallel revisions of the same original into one Word document with attributed tracked changes. Use when reviewers edited separate copies of a shared base."
"Merge two or more separately edited copies of one original document into one Word document, with each revision's edits as tracked changes labeled by who made them. Use when several people edited copies of the same base document."
changed /skill_md_contents
"---\nname: merge\ndescription: Merge two or more parallel revisions of the same original into one Word document with attributed tracked changes. Use when reviewers edited separate copies of a shared base.\n---\n\n# Merge parallel revisions\n\n1. Identify one original and at least two revisions of it. Ask which draft everyone\n started from when the shared base is unclear. If the drafts were written\n independently, use the combine workflow. If they form a chronological chain,\n use version history.\n2. Confirm the author labels for the revisions. Do not guess authors. Revision order\n does not change the result, so do not ask the user to order parallel edits.\n3. Call `get_instructions`, then `create_merge`, passing attached files in `base_file`\n and `next_version_files` (or accessible file paths), original file names, and the\n confirmed `next_version_authors`.\n4. Follow the upload instructions if the result asks for uploads, then call\n `get_merged_document` until generation finishes.\n5. Download and present the Word document in the conversation with its interactive\n link. The user resolves competing tracked changes in Word. Use `read_text` only\n when the user requests analysis.\n\nExcel is unsupported for this workflow. Explain that limitation before starting.\n\nSelected documents are uploaded to Version Story and stored in the user’s account.\nFollow the user’s explicit instructions. Use only files they selected and that this\nsession can access. Complete OAuth through the host’s sign-in flow; never request\npasswords or tokens in chat. If files are unavailable, ask the user to attach them.\n\nWhen a transfer or tool call fails, report it with `report_issue`, omitting document\ncontents and credentials, then explain the failure and stop. If the account limit is\nreached, tell the user, give them the upgrade link from the message, and stop.\n"
"---\nname: merge\ndescription: \"Merge two or more separately edited copies of one original document into one Word document, with each revision's edits as tracked changes labeled by who made them. Use when several people edited copies of the same base document.\"\n---\n\nCall Version Story's `create_merge` tool. Its description says how to call it, and the message in each result says what to do next: follow them.\n"
Full snapshot data
{
"description": "Merge two or more separately edited copies of one original document into one Word document, with each revision's edits as tracked changes labeled by who made them. Use when several people edited copies of the same base document.",
"included_files": [],
"name": "merge",
"skill_md_contents": "---\nname: merge\ndescription: \"Merge two or more separately edited copies of one original document into one Word document, with each revision's edits as tracked changes labeled by who made them. Use when several people edited copies of the same base document.\"\n---\n\nCall Version Story's `create_merge` tool. Its description says how to call it, and the message in each result says what to do next: follow them.\n"
}SHA-256 of public snapshot: ef16e780ffc6437398d7d0738eb36a550dbf77746e55211243172f372fb956ee