← Version Story Redline CompareCONTENT HISTORY
WHAT CHANGED
changed
changed
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 version-history
Full description — Now says: into one Word document that attributes each surviving change to the version that introduced it. Use when the user asks
Observed in instructions or declared skills. Runtime behavior has not been tested.
Save Version Story Redline Compare and check future changes in Following.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Before
Sep 30, 2026 · 23:10 UTC
and create one Word document attributing surviving changes to their source versions. Use for requests about
After
Oct 24, 2026 · 13:14 UTC
into one Word document that attributes each surviving change to the version that introduced it. Use when the user asks
Skill instructions
Before
Sep 30, 2026 · 23:10 UTC
Trace changes through successive versions of a document and create one Word document attributing surviving changes to their source versions. Use for requests about how a document evolved or who introduced a change. # Trace a document’s h...
After
Oct 24, 2026 · 13:14 UTC
"Trace changes through successive versions of a document into one Word document that attributes each surviving change to the version that introduced it. Use when the user asks how a document evolved or who introduced a change." Call Vers...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,30 +1,6 @@ --- name: version-history -description: Trace changes through successive versions of a document and create one Word document attributing surviving changes to their source versions. Use for requests about how a document evolved or who introduced a change. +description: "Trace changes through successive versions of a document into one Word document that attributes each surviving change to the version that introduced it. Use when the user asks how a document evolved or who introduced a change." --- -# Trace a document’s history - -1. Establish the versions in chronological order, oldest first. If the user has not - specified the order, propose it from the names or dates and obtain confirmation. - Incorrect ordering changes attribution. -2. Confirm each version’s author label with the user. Use supplied names and do not - invent authors. -3. Call `get_instructions`, then `create_version_history` with the attached files in - `version_files` (or accessible paths) in the confirmed order, original file names, - and the confirmed `version_authors`. -4. Follow the upload instructions if the result asks for uploads, then call - `get_version_history_document` until ready. -5. Download and present the Word document in the conversation. Use `read_text` when - the user requests an explanation or asks about a particular change. - -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_version_history` 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
BEFORE
"Trace changes through successive versions of a document and create one Word document attributing surviving changes to their source versions. Use for requests about how a document evolved or who introduced a change."
AFTER
"Trace changes through successive versions of a document into one Word document that attributes each surviving change to the version that introduced it. Use when the user asks how a document evolved or who introduced a change."
changed /skill_md_contents
BEFORE
"---\nname: version-history\ndescription: Trace changes through successive versions of a document and create one Word document attributing surviving changes to their source versions. Use for requests about how a document evolved or who introduced a change.\n---\n\n# Trace a document’s history\n\n1. Establish the versions in chronological order, oldest first. If the user has not\n specified the order, propose it from the names or dates and obtain confirmation.\n Incorrect ordering changes attribution.\n2. Confirm each version’s author label with the user. Use supplied names and do not\n invent authors.\n3. Call `get_instructions`, then `create_version_history` with the attached files in\n `version_files` (or accessible paths) in the confirmed order, original file names,\n and the confirmed `version_authors`.\n4. Follow the upload instructions if the result asks for uploads, then call\n `get_version_history_document` until ready.\n5. Download and present the Word document in the conversation. Use `read_text` when\n the user requests an explanation or asks about a particular change.\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"
AFTER
"---\nname: version-history\ndescription: \"Trace changes through successive versions of a document into one Word document that attributes each surviving change to the version that introduced it. Use when the user asks how a document evolved or who introduced a change.\"\n---\n\nCall Version Story's `create_version_history` 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": "Trace changes through successive versions of a document into one Word document that attributes each surviving change to the version that introduced it. Use when the user asks how a document evolved or who introduced a change.",
"included_files": [],
"name": "version-history",
"skill_md_contents": "---\nname: version-history\ndescription: \"Trace changes through successive versions of a document into one Word document that attributes each surviving change to the version that introduced it. Use when the user asks how a document evolved or who introduced a change.\"\n---\n\nCall Version Story's `create_version_history` 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: 9f7f25cdcdf33eb5aa703ffa8d9374b482c6bdf3d9745a41eac8e985f99c77c2