Individual skill

analysis-workspace

Large analyses and file delivery: scratch staging, chunked batches, run-code aggregation, CSV/XLSX exports. Use when work exceeds one context window or the user wants a file.

templates/analytics/.agents/skills/analysis-workspace/SKILL.md

Read pinned source

Source commit ff01b4009091c2140edb34d6f790ec64e7823356

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
7,643
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Analysis Workspace

Analysis files live in the same Resources workspace users inspect and manage in
the app. Use normal path conventions:

- `scratch/...` for temporary staging files, per-item memos, raw API pulls, and
  other agent working data. These are hidden from the Resources view by default.
- Descriptive folders such as `analysis/q2-churn/` only for files the user
  should keep, inspect, or manage after the analysis.

The `run-code` helpers (`workspaceRead`, `workspaceWrite`, `workspaceAppend`,
`workspaceList`) and `saveToFile` write through this Resources-backed file
store. Use them to stage intermediate results that would overflow the context
window, then read them back selectively for synthesis.