How do I install the Yao Workspace skill?

Run npx skillmds add yaoapp/yao-workspace in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Yao Workspace safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Yao Workspace?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Yao Workspace free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Yao Workspace?

YaoApp (@yaoapp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Yao Workspace by yaoapp — Agent Skill

Name: Yao Workspace
Rating: 4.5 (4 reviews)
Author: YaoApp

Yao Workspace

Workspace file I/O expert. ALWAYS invoke this skill when you need to list workspaces, read or write files in a workspace on a remote node, or browse workspace directories. Use this for cross-node file operations — for local sandbox files, use standard filesystem tools instead.

YaoApp 1aeaaf2 3.8 KB Updated Sep 9, 2026

File contents

Workspace Tools

Five tools for managing workspaces and file I/O, called via bash.

workspace_list

List workspaces with summary info. Use workspace_get for full details.

tai tool workspace_list '{}'
tai tool workspace_list '{"node": "tai-node-1"}'

Parameter	Type	Required	Description
`node`	string	no	Filter by Tai node ID

workspace_get

Get full workspace details: name, owner, node, labels, timestamps.

tai tool workspace_get '{"id": "ws-abc123"}'

Parameter	Type	Required	Description
`id`	string	yes	Workspace ID

workspace_file_list

List files and directories in a workspace path.

tai tool workspace_file_list '{"id": "ws-abc123"}'
tai tool workspace_file_list '{"id": "ws-abc123", "path": "src/components"}'

Parameter	Type	Required	Description
`id`	string	yes	Workspace ID
`path`	string	no	Directory path (default ".")

workspace_file_read

Read file content from workspace. Returns text (UTF-8) or base64 encoded.

tai tool workspace_file_read '{"id": "ws-abc123", "path": "README.md"}'
tai tool workspace_file_read '{"id": "ws-abc123", "path": "image.png", "encoding": "base64"}'

Parameter	Type	Required	Description
`id`	string	yes	Workspace ID
`path`	string	yes	File path relative to workspace root
`encoding`	string	no	"text" (default) or "base64"

workspace_file_write

Write content to a file in workspace. For binary files, use base64 encoding.

tai tool workspace_file_write '{"id": "ws-abc123", "path": "output.txt", "content": "Hello World"}'
tai tool workspace_file_write '{"id": "ws-abc123", "path": "data.bin", "content": "base64data...", "encoding": "base64"}'

Parameter	Type	Required	Description
`id`	string	yes	Workspace ID
`path`	string	yes	File path relative to workspace root
`content`	string	yes	File content (text or base64 encoded)
`encoding`	string	no	"text" (default) or "base64"

Typical Workflow

workspace_list — discover available workspaces
workspace_get — get full details (node, labels)
workspace_file_list — browse directory structure
workspace_file_read — read specific files
workspace_file_write — write output files

Guidelines

Use workspace_list for discovery, workspace_get for details (list returns summaries only)
For large files (>1MB), prefer local filesystem operations if the workspace is mounted in the sandbox
Use encoding: "base64" for binary files (images, archives, etc.)
File paths are relative to the workspace root — do not use absolute paths
The current sandbox workspace ID is available via $CTX_WORKSPACE_ID
All output is JSON

---name: yao-workspacedescription: Workspace file I/O expert. ALWAYS invoke this skill when you need to list workspaces, read or write files in a workspace on a remote node, or browse workspace directories. Use this for cross-node file operations — for local sandbox files, use standard filesystem tools instead.--- # Workspace Tools Five tools for managing workspaces and file I/O, called via bash. ## workspace_list List workspaces with summary info. Use `workspace_get` for full details. ```bash tai tool workspace_list '{}' tai tool workspace_list '{"node": "tai-node-1"}' ``` | Parameter | Type | Required | Description | |-----------|--------|----------|--------------------------| | `node` | string | no | Filter by Tai node ID | ## workspace_get Get full workspace details: name, owner, node, labels, timestamps. ```bash tai tool workspace_get '{"id": "ws-abc123"}' ``` | Parameter | Type | Required | Description | |-----------|--------|----------|---------------| | `id` | string | yes | Workspace ID | ## workspace_file_list List files and directories in a workspace path. ```bash tai tool workspace_file_list '{"id": "ws-abc123"}' tai tool workspace_file_list '{"id": "ws-abc123", "path": "src/components"}' ``` | Parameter | Type | Required | Description | |-----------|--------|----------|--------------------------------| | `id` | string | yes | Workspace ID | | `path` | string | no | Directory path (default ".") | ## workspace_file_read Read file content from workspace. Returns text (UTF-8) or base64 encoded. ```bash tai tool workspace_file_read '{"id": "ws-abc123", "path": "README.md"}' tai tool workspace_file_read '{"id": "ws-abc123", "path": "image.png", "encoding": "base64"}' ``` | Parameter | Type | Required | Description | |------------|--------|----------|------------------------------------------| | `id` | string | yes | Workspace ID | | `path` | string | yes | File path relative to workspace root | | `encoding` | string | no | "text" (default) or "base64" | ## workspace_file_write Write content to a file in workspace. For binary files, use base64 encoding. ```bash tai tool workspace_file_write '{"id": "ws-abc123", "path": "output.txt", "content": "Hello World"}' tai tool workspace_file_write '{"id": "ws-abc123", "path": "data.bin", "content": "base64data...", "encoding": "base64"}' ``` | Parameter | Type | Required | Description | |------------|--------|----------|------------------------------------------| | `id` | string | yes | Workspace ID | | `path` | string | yes | File path relative to workspace root | | `content` | string | yes | File content (text or base64 encoded) | | `encoding` | string | no | "text" (default) or "base64" | ## Typical Workflow 1. `workspace_list` — discover available workspaces 2. `workspace_get` — get full details (node, labels) 3. `workspace_file_list` — browse directory structure 4. `workspace_file_read` — read specific files 5. `workspace_file_write` — write output files ## Guidelines - Use `workspace_list` for discovery, `workspace_get` for details (list returns summaries only) - For large files (>1MB), prefer local filesystem operations if the workspace is mounted in the sandbox - Use `encoding: "base64"` for binary files (images, archives, etc.) - File paths are relative to the workspace root — do not use absolute paths - The current sandbox workspace ID is available via `$CTX_WORKSPACE_ID` - All output is JSON

Frequently asked questions