history-and-undo
See a Leeway file's earlier versions or the drive's trash, and bring things back. Use when asked to undo, revert, restore, recover a deleted file, see who changed something, or show a file's history on the Leeway drive.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- history-and-undo
- description
- See a Leeway file's earlier versions or the drive's trash, and bring things back. Use when asked to undo, revert, restore, recover a deleted file, see who changed something, or show a file's history on the Leeway drive.
03 SKILL.md 正文
History and undo on the Leeway drive
Nothing written to a Leeway drive is lost straight away: every overwritten file keeps its earlier contents as versions, and deleted files and folders wait in the trash for 30 days.
Earlier versions of a file
list_versionswithpath: newest first, each withversion_id,at,size,revandby(the person, the app and the device that made it).- Show the person which version you mean (when and by whom), and read it with
read_fileif they want to compare. restorewithversion_idputs it back. What it replaces becomes a version itself, so a restore can be undone the same way.
Deleted files
deletewithpathmoves a file to the trash;recursive: trueis needed for a folder. It answers with adeleted_id. Check with the person before deleting anything they didn't name.list_deletedlists the trash, newest first;prefixnarrows it to one folder.restorewithdeleted_idbrings it back to where it was. If something now sits at that path,on_existschooses what happens; by default nothing is overwritten.toputs it somewhere else.
Who changed what
list_events lists recent activity, and each version's by names who made it.
What can't be done here
There is no tool to empty the trash or erase history: the trash empties itself after 30 days. If someone asks for a permanent erase, say so rather than deleting more.
Report
Say what you restored, from which version or deleted entry, and its path and rev now.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.