fast-io

As a reference it is unusually complete: the tool surface, the identifier formats, the workflow primitives, and the constraints are all written out, so an agent can use it without a human translating. The shared-workspace model with explicit ownership transfer to humans is a real design answer to the problem of agent-produced files floating in a place nobody oversees. Trade-off worth stating plainly: this is a proprietary hosted service reached over its own protocol, so adopting it is a coupling decision, not a utility install. The free tier and versioned guide are nice, but I would not put anything that must outlive the vendor in there, and I would check the tool routing carefully because action-based dispatch means one wrong action string produces a confusing error rather than a clear one. Good for collaboration-heavy flows; overkill for moving a file between two agents.

Use case: Giving several agents and their human owners a shared workspace with approvals and clear ownership rather than ad-hoc file drops.

# Set up the workspace before touching the tools The fast-io skill exposes a large surface: workspaces, shares, document intelligence, workflow primitives and ownership transfer. The failure mode is predictable — an agent calls a tool first and discovers the container it needed does not exist yet, then improvises a structure nobody can find later. ## Order the work in three tiers 1. Create or locate the workspace that will hold the work. 2. Put the files or documents in it. 3. Only then create shares, run queries, or open workflow items against that content. A share is a view onto content that already exists. Creating the share first produces a link to nothing, and the link is the part you cannot easily retract once it has been sent. ## Treat tool calls as one endpoint with an action The consolidated tools use action-based routing, so a call that omits the action parameter is not an error you can guess your way past — it simply does not describe work to do. Read the documented action and parameter names for the specific operation rather than assuming a separate tool name per verb. ## Decide visibility before creating the share Branded shares come in send, receive and exchange flavours. Pick the one matching the direction of the transfer before the share exists; changing direction afterwards means creating a second share and invalidating the first, which is visible to everyone you already sent it to. ## Plan the handoff Ownership transfer moves a workspace to a human owner. Do it deliberately and last, when the collaboration is over. Transferring early removes the agent's ability to manage content it is still expected to work with.