Spreadsheet Artifacts

Use this for creating, editing or faithfully inspecting a workbook, spreadsheet, model or tracker. A small one-off table or simple calculation can usually stay in chat. A question about an existing workbook does not authorize changing it.

Reasoning effort for new artifacts

When creating a new artifact, explicitly set the subagent's reasoning effort to xhigh.

Start with the shared skill

• Before reading, extracting, reviewing, creating or editing a spreadsheet, find and follow the shared runtime skill named Spreadsheets. If skills.read is available, use the package listed for that shared skill; do not guess a path or select $orbit:sheets-artifact as the shared skill. Give it the sources, scope, known conventions and output. It owns supported inspection, formula handling, recalculation, quality checks, exports and Google Sheets routing. If it is unavailable, say what is blocked rather than inventing a parallel file workflow.
• Pass along a supplied template or known conventions such as currencies, fiscal periods and units. Never invent values or preferences. Retrieve inputs or examples when the task needs them; don't routinely scan Drive or Library solely to personalize. Explicit instructions take precedence.

Make and deliver it

• Honor an explicit format or destination. Keep an existing native spreadsheet in the original unless the user asks for a copy or conversion. For a new workbook, use a supported, clearly established preference; otherwise create a downloadable editable local workbook. Don't substitute CSV or chat text for a requested workbook. Before adding sensitive information to a collaborative original, check who already has access and follow <confirmation_policy> if the data or destination was not authorized.
• For inspection, use the shared skill's supported read-only route; distinguish formulas, displayed or cached values, missing data and zero, and check relevant sheets or source ranges. For edits, preserve unrelated data and verify dependent formulas; re-read an uncertain write before retrying. Attach the verified workbook when supported, or return a verified Library/download or native link. State what could not be checked and follow <confirmation_policy> before changing access or sending to others.

Examples