AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Spreadsheets

skill-tiga001-captain-who-spreadsheets · by Tiga001

Create, edit, inspect, calculate, and render Microsoft Excel-compatible .xlsx workbooks. Use for formulas, typed data, formatting, tables, charts, images, multiple sheets, repeated or data-driven generation, and any other spreadsheet task.

— No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-tiga001-captain-who-spreadsheets

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-tiga001-captain-who-spreadsheets)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Spreadsheets? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Spreadsheets

Route by intent:

  • Read and verify: use the flat semantic office_spreadsheet tool only for inspect and render.
  • Create: use one saved Managed Builder from templates/builder.py with normal Python and the pinned managed spreadsheet runtime.
  • Edit an existing .xlsx: inspect first, then use one saved Workbook Editor from

templates/editor.py. It executes normal Python against the frozen source snapshot and publishes a distinct Host-gated save-as output.

For a workbook attachment, use attachments_list for this conversation or attachments_list_project for authorized project/task-tree attachments. Pass its exact returned readPath to the available office_spreadsheet reader; when using a script, bind that same path through run_command.inputs. These virtual paths are not workspace files. Use only tools actually provided in the current model request; do not invent a missing reader or Skill ref.

Do not call or invent native Office create or mutation operations. The model-facing Office tool is intentionally read/verify-only; all workbook writes go through the fixed Builder or Editor.

Managed scripts

Before materializing, choose one dedicated workspace-relative script directory. Reuse an existing plain directory when appropriate; otherwise create it first with one separate idempotent mkdir -p command. Record whether this task created it.

Use skills_list_resources to locate templates/builder.py for creation or templates/editor.py for an existing workbook. Materialize the chosen exact revision once into a new path in that prepared directory. Patch and rerun that same file; do not accumulate replacement scripts.

Both files are genuine Python. The managed Python 3.12.13 spreadsheet runtime provides openpyxl 3.1.5, xlsxwriter 3.2.9, numpy 2.5.2, and pandas 3.0.5. openpyxl remains the workbook authoring and Host validation engine; the additional libraries do not change the Builder/Editor workflow. The Editor's edit_workbook region may contain functions, loops, conditions, comprehensions, and imports from the pinned runtime. Never convert it into an AST, JSON, or artificial operation DSL. Keep the fixed CLI, input resolver, publication code, and edit markers unchanged.

Rely on the Host's automatic syntax preflight after every materialization or patch. Do not issue a model-authored syntax-check command; never request system Python, python -m, python -c, inline code, heredocs, package installation, or a command combined with &&, |, or ;.

Run one direct logical command:

  • Create: python .py --output
  • Edit: python .py --source --output

Every Builder or Editor command must declare exactly one static --output.

Omit runtimeProfile and observe. Bind every source workbook, image, CSV, attachment, or earlier artifact through run_command.inputs and use its logical mountPath below MYCOPILOT_INPUT_ROOT. The Host freezes the script, runtime, inputs, and target; redirects the declared Office output through private staging; reopens it with pinned openpyxl using data_only=False; and publishes atomically. Do not duplicate that gate in the script or call native validate. The fixed script saves once to the Host-provided output path; do not add another temporary file, candidate reopen, or os.replace layer. If a command returns running, wait on that same command session before using the output. Inspect artifactObservation after every terminal result and never blindly repeat a call that may have changed files.

The Host verifies this Run's materialization receipt and freezes the spreadsheets runtime, version, and integrity. It grants no additional command or file permission and never falls back to executables on PATH. Never supply package versions, guess a profile, or use runtimeProfile to replace the fixed Builder/Editor workflow with a self-authored script.

observe is optional best-effort Office file observation, not permission or command-success evidence. For a separately needed explicit observation, use kinds: ["office"] and exact expectedOutputs, resolved relative to cwd; it does not enumerate sibling files. Add additionalRoots only for separately authorized files/directories; recursive scans outside the workspace require read=all. Verified Builder/Editor outputs are observed automatically, so keep omitting observe for the normal workflow.

openpyxl stores formulas but does not calculate them. The Host reopen gate, formula inspection, and cached values do not prove recalculation. Claim calculated results only when a separate authoritative calculation engine returned explicit evidence.

Completion gate

  1. Inspect the source before editing and stop when preservation of an unsupported workbook feature cannot be established.
  2. Create or edit with one task-owned managed script; keep values, dates, booleans, and formulas typed.
  3. Require terminal command success and an artifactObservation confirming the expected .xlsx effect.
  4. Terminal success proves the Host reopened the private candidate with pinned openpyxl before

publication. Inspect the final sheet list, populated ranges, formula text, formats, tables, charts, images, and defined names; do not call native validate.

  1. For every final sheet, render the visual extent formed by its populated range plus every reported floating chart/image bound. Read each exact returned outputs[].readPath with the actually available read_image.path and record a verdict. If bounds, rendering, or image reading are unavailable, disclose incomplete coverage. Any later edit invalidates the ledger.
  2. Keep syntax, execution, package, calculation, and visual evidence separate. Report only checks that actually succeeded.
  3. Delete the exact task-owned Builder or Editor and temporary files. Use rmdir only if this task created the now-empty directory; preserve pre-existing files and never use recursive deletion.

Read [references/workflows.md](references/workflows.md) for creation, inputs, observation, and QA. Before editing an existing workbook, also read [references/editing-existing.md](references/editing-existing.md).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.