← Version StoryCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Version Story
Snapshot Sep 30, 2026 · 23:10 UTC · version 0.29.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "compare",
"description": "Compare document versions and create a PDF redline or Word tracked-changes file. Use when the user requests a comparison, redline, blackline, or explanation of changes.",
"included_files": [],
"skill_md_contents": "---\nname: compare\ndescription: Compare document versions and create a PDF redline or Word tracked-changes file. Use when the user requests a comparison, redline, blackline, or explanation of changes.\n---\n\n# Compare documents\n\n1. Identify the original and revised documents. Ask which is the original if unclear.\n2. Call `get_instructions` for the current connector workflow.\n3. Use `create_comparison` for files: pass attached files in `base_file` and\n `comparison_files`, or accessible file paths. Use `create_comparison_from_links`\n for HTTPS document links. Follow the upload instructions only when the result\n asks for uploads.\n4. Use `get_redlines` to obtain the finished documents. Leave `download_options` unset\n for the normal viewable redline. Request `word_redline` when the user asks for Word\n or tracked changes.\n5. Download and present the actual result file in the conversation, with the interactive\n redline link. Use the file presentation supported by this OpenAI environment.\n6. If the user requests an explanation of the changes, use `read_text` as the source\n for that analysis. A request for a redline alone does not request a summary.\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"
}SHA-256: 8e68e7975d9638a91d3a126889c4fdba448a6f9f70b6b965b78945e8ebc181c3