
Workspace
- 35 installs
- 186 repo stars
- Updated August 4, 2026
- aws-samples/sample-strands-agent-with-agentcore
Workspace is a Claude Code skill that gives an AI agent read and write access to a shared session workspace so files can pass between skills.
About
This skill gives an AI agent unified read and write access to files in the current session workspace. A developer adds it to a Strands agent so one skill's output (code-agent files, Word, Excel, images) can be read or handed to another skill. It abstracts path conventions and handles text and base64 binary content, with userId and sessionId injected automatically.
- Provides workspace_list, workspace_read, and workspace_write over a shared session
- Lets one skill pass a file to another within the same isolated session
- Handles text and base64 binary files with automatic userId and sessionId injection
Workspace by the numbers
- 35 all-time installs (skills.sh)
- Ranked #8,710 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
workspace capabilities & compatibility
- Capabilities
- file management
What workspace says it does
Read and write files in the shared session workspace. Use this to access files created by any skill
Files written here are immediately available to all other skills in the session
npx skills add https://github.com/aws-samples/sample-strands-agent-with-agentcore --skill workspaceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 35 |
|---|---|
| repo stars | ★ 186 |
| Last updated | August 4, 2026 |
| Repository | aws-samples/sample-strands-agent-with-agentcore ↗ |
What it does
Let an agent read and write session files so skills can share outputs like documents and images.
Who is it for?
Multi-skill agent sessions where one tool's output file must be read or reused by another tool.
When should I use this skill?
The agent needs to access files created by another skill or hand a file from one skill to another in the same session.
By the numbers
- 3 core operations (workspace_list, workspace_read, workspace_write)
- 5 documented path prefixes
Files
Workspace
Provides unified read/write access to all files in the current session. The userId and sessionId are injected automatically — you only specify the logical path.
Path Conventions
| Prefix | What it accesses |
|---|---|
code-agent/<file> | Files created by the code agent (auto-synced) |
code-interpreter/<file> | Files saved by code interpreter via output_filename |
documents/powerpoint/<file> | PowerPoint presentations |
documents/word/<file> | Word documents |
documents/excel/<file> | Excel spreadsheets |
documents/image/<file> | Images from other tools |
Note: Code interpreter only saves to workspace whenoutput_filenameis set inexecute_code. Files fromexecute_commandorfile_operationsstay inside the sandbox.
Usage
See everything in the session:
workspace_list()
workspace_list("code-agent/")Read a file the code agent created:
workspace_read("code-agent/calculator.png") # binary → base64
workspace_read("code-agent/report.md") # text → stringPass a file from one skill to another:
result = workspace_read("documents/excel/data.xlsx") # encoding: base64
workspace_write("code-agent/data.xlsx", result["content"], encoding="base64")Notes
- Text files return
encoding: "text"with plain string content - Binary files (images, Office docs, PDF, etc.) return
encoding: "base64" workspace_writeaccepts both encodings — use"base64"for binary- Files written here are immediately available to all other skills in the session
UI Guidance (from tools-config)
Path conventions (userId/sessionId injected automatically):
code-agent/<file>— files from the code agentdocuments/powerpoint/<file>— PowerPointdocuments/word/<file>— Worddocuments/excel/<file>— Exceldocuments/image/<file>— images
Binary vs text: images/PDFs/Office files are returned base64-encoded (encoding: "base64"); use the same encoding when writing them back.