calc-spreadsheets

Create, open or edit Calc spreadsheets: ODS default; XLSX for Excel compatibility.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/_office/skills/calc-spreadsheets/SKILL.md

Quality

Content

78%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 tight, actionable body with executable examples and clear rules that earns the simple-skill exceptions; its only real gaps are the unexplained file_id linkage, the unshown create_chart shape, and one duplicated UI rule.

Suggestions

Clarify where file_id comes from — e.g. note that the create response returns the file_id used by edit — to close the sequence gap between the two examples.

Show a minimal create_chart chart object (or point to where its shape is documented), since it is the one operation named without an example.

De-duplicate the no-auto-open rule, which appears both in the UI-ownership paragraph and in the final practical rule bullet.

Dimension	Reasoning	Score
Conciseness	The body is lean: two complete JSON examples plus terse practical rules, with no explanation of concepts Claude already knows. It falls short of anchor 5 only through minor redundancy — the no-auto-open rule is stated twice ('must not open a document modal or Desktop surface automatically' and again in the final bullet 'Do not open Calc/Desktop automatically') and the UI-ownership paragraph could be tightened.	4 / 5
Actionability	Two copy-paste-ready tool calls (create with CSV content, edit with set_cells) and concrete operation guidance (rows / append_rows / set_cells) match 'mostly executable; concrete code or commands with minor gaps'. Not a 5 because the create_chart path is named but its chart-object shape is never shown, and the edit example's file_id provenance is unexplained.	4 / 5
Workflow Clarity	The create → edit sequence is clear with format-selection and blank-request rules ('For a blank workbook request, create a simple workbook... do not call status first'), fitting anchor 4's 'clear sequence with most checkpoints present; minor validation gaps'. The linkage from create's response to the edit example's file_id 'abc123' is left implicit, and there is no post-edit verification, keeping it below 5.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no external bundle files (no references/, scripts/, or assets/ directories exist, and the body references none), and the content is well-organized into Overview, Workflow, and Practical rules sections — the rubric's simple-skill exception for a well-organized short skill applies directly.	5 / 5
	Total	17 / 20 Passed

Description

66%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.

The description is concise and concrete, with a clear what and distinct format-level triggers, but it omits any explicit 'use when' trigger guidance, which caps completeness and weakens trigger coverage of natural user phrases like workbook/budget.

Suggestions

Add a 'Use when...' clause with explicit trigger phrases, e.g. 'Use when the user asks for a spreadsheet, workbook, editable table, budget, or Calc/ODS file, or needs Excel/XLSX compatibility.'

Include natural synonyms and extensions users actually say — workbook, budget, .ods, .xlsx — to broaden trigger term coverage.

Mention one or two more of the skill's actual capabilities (e.g., formulas or embedded charts) to close the coverage gap.

Dimension	Reasoning	Score
Specificity	"Create, open or edit Calc spreadsheets" lists three concrete actions in a named domain (Calc/ODS/XLSX), matching anchor 4's 'several specific actions; minor gaps in coverage'. It is not a 5 because capabilities the skill actually supports (formulas, embedded charts, budget tables) go unmentioned.	4 / 5
Completeness	The 'what' is clear (create/open/edit spreadsheets, ODS default, XLSX for Excel compatibility), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3, which is exactly the anchor ('clear what, when missing or only weakly implied').	3 / 5
Trigger Term Quality	The description carries good natural keywords — "Calc spreadsheets", "ODS", "XLSX", "Excel" — but misses common variations users would say such as "workbook", "budget", "table", and the file extensions ".ods"/".xlsx", so it fits anchor 4 (good coverage, a few natural terms missing) rather than anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Calc spreadsheets: ODS default; XLSX for Excel compatibility" carves a clear spreadsheet niche with distinct format triggers, distinct from document/presentation skills. It is not a 5 because without explicit 'use when' guidance and with generic terms like 'spreadsheet', it could still overlap with other table/spreadsheet-adjacent skills — fitting anchor 4 ('mostly distinct; minor overlap risk').	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: agent0ai/agent-zero
Path: plugins/_office/skills/calc-spreadsheets/SKILL.md
Commit: e3051fb

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.