CtrlK
BlogDocsLog inGet started
Tessl Logo

spreadsheet-agent

Authoring playbook for building agents that read or write tabular data — Google Sheets, Microsoft Excel, CSV, Airtable, Notion databases, or any spreadsheet. Use this when the user wants an agent that updates rows, reads cells, computes totals, generates reports from sheets, syncs data between spreadsheets, or automates anything involving rows, columns, ranges, or worksheets.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable playbook: the system-prompt template, worked examples, and completion criteria are concrete and validation-heavy, exactly right for a destructive/batch domain. The main costs are token redundancy (the missing-input policy is restated three times) and a single-file layout that inlines material which could be split into references.

Suggestions

Consolidate the missing-input policy into the system prompt template only, and reduce 'Required behavioral rules to enforce' to a one-line pointer ('enforce the sheet-selection, output-format, and completion rules from the template') to remove the triple statement of the same policy.

Move the 'Worked example (full)' builder walkthrough into a references/ file (e.g. references/example-agent.md) and keep a one-line pointer in SKILL.md, shortening the always-loaded body.

Trim overlap between 'When to use' and the frontmatter description — the body's keyword list largely duplicates trigger terms already in the description.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is densely prescriptive, but the missing-input policy is stated three times — once as its own section ('If no spreadsheet tool is attached...'), again nearly verbatim inside the template ('If no spreadsheet integration is available, stop and say...'), and again in 'Required behavioral rules' ('default only when exactly one relevant sheet/table is available') — which is avoidable repetition. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than level 4 (which would require only minor trimming) or level 2 (no known-concept padding, so not 'noticeably verbose' overall).

3 / 5

Actionability

Fully copy-paste-ready for its purpose: a complete system-prompt template with exact refusal strings ('I need access to your spreadsheet first...'), exact receipt formats ('Updated <N> rows in <Sheet name> > <Tab name>, range <A2:D17>'), a six-step worked example with a sample final reply, and a full second builder example. Every instruction is executable as written; this is an instruction-only skill whose guidance is maximally concrete, per the rubric's code_vs_instruction note.

5 / 5

Workflow Clarity

Sequences are explicit with validation checkpoints and feedback loops: read-before-write, dry-run-and-stop for destructive operations, verification by read-back or returned values, a 4-item completion-criteria checklist, and error recovery ('If a row fails to write, report the row number/id and reason'). Because validation/verification steps are explicitly present, the destructive/batch cap at 3 does not apply, and the content matches the level-5 anchor (sequence + explicit validation + feedback loops + checklist).

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body references none, so all navigation is internal — that part is clean. However, at ~117 lines with a full inlined system-prompt template plus two worked examples, content that could plausibly live in a separate reference (e.g. the full worked example) is inlined, which is a minor organization gap — the level-4 anchor ('good structure; most content appropriately placed; minor organization gaps') fits better than level 5, and far better than level 3 (sections are well-signaled and nothing is buried).

4 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: concrete actions, explicit what-and-when, third-person voice, and rich natural trigger terms across all major spreadsheet platforms. The only weaknesses are minor — a slight risk of firing for direct spreadsheet work (rather than agent building) and the absence of literal file-extension triggers.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'building agents that read or write tabular data', 'updates rows, reads cells, computes totals, generates reports from sheets, syncs data between spreadsheets' — with comprehensive coverage of the authoring-playbook domain across named platforms (Google Sheets, Microsoft Excel, CSV, Airtable, Notion). This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; it is not the level-4 anchor because there are no meaningful coverage gaps.

5 / 5

Completeness

Both parts are explicit: 'what' is 'Authoring playbook for building agents that read or write tabular data' and 'when' is the explicit 'Use this when the user wants an agent that updates rows, reads cells, computes totals...' with concrete trigger phrases. This exactly matches the level-5 anchor example structure.

5 / 5

Trigger Term Quality

Natural terms are comprehensive: product names ('Google Sheets, Microsoft Excel, CSV, Airtable, Notion databases') plus everyday synonyms ('rows, columns, ranges, worksheets', 'spreadsheet') and concrete user goals ('updates rows, reads cells, computes totals, generates reports'). Users would naturally say these when they need this skill; only trivial literal file extensions (e.g. '.xlsx') are absent, which is not enough to drop to level 4.

5 / 5

Distinctiveness Conflict Risk

The niche (authoring spreadsheet-automation agents) is distinct with clear triggers, but phrases like 'reads cells' or 'computes totals' could also fire for a user who merely wants data analyzed in a spreadsheet rather than an agent built, so there is minor overlap risk with a general spreadsheet-processing skill — the level-4 anchor ('mostly distinct; minor overlap risk with closely related skills') is the best fit.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mastra-ai/mastra
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.