Name: microsoft-excel
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

microsoft-excel

Microsoft Excel integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microsoft Excel data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/microsoft-excel/SKILL.md

Quality

Content

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

The content is a well-structured, highly actionable CLI integration guide with a genuinely sequenced, checkpointed connection workflow. Its weak spots are an over-explanatory intro paragraph and a dangling 'Step 2' cross-reference.

Suggestions

Delete the opening paragraph defining what Excel is and the filler line 'Use action names and parameters as needed'; Claude already knows this and they consume context.

Fix the dangling 'Step 2' reference — either add a '## Step 2' header or reword to point directly at the 'Searching for actions' section.

Add a one-line validation/confirm step before destructive commands (delete-table, delete-worksheet) in the Running actions or Best practices section.

Dimension	Reasoning	Score
Conciseness	It is mostly command-dense and efficient, but the opening paragraph ('Microsoft Excel is a spreadsheet software used for organizing...') explains what Excel is — exactly the kind of concept Claude already knows that the rubric penalizes — and 'Use action names and parameters as needed' is filler.	3 / 5
Actionability	It provides concrete, copy-paste CLI commands for every stage (install, login, connection ensure/get, action list, action run with --input, request proxy) plus a Popular actions table, but examples lean on placeholders (<actionId>, CONNECTION_ID) rather than one full real invocation with sample output.	4 / 5
Workflow Clarity	The connection setup is clearly sequenced with state-based checkpoints and a feedback loop (poll until READY, branch on CLIENT_ACTION_REQUIRED, re-poll after action), though the referenced 'Step 2' has no corresponding header and destructive actions (delete-table, delete-worksheet) get no explicit pre-validation.	4 / 5
Progressive Disclosure	The body is well-organized under clear headers (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with an external 'Official docs' link, but everything is inlined in one file and the dangling 'Step 2' reference is a minor navigation gap.	4 / 5
	Total	15 / 20 Passed

Description

62%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 covers both what the skill does and when to use it with a product-specific trigger, which is solid. Its main weakness is generic action verbs and thin keyword coverage — it omits natural synonyms like spreadsheets, workbooks, worksheets, and .xlsx.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete operations, e.g. 'Create and update worksheets, tables, and ranges; read and write cells and formulas.'

Broaden trigger terms to include natural synonyms users say: 'Use when working with Excel spreadsheets, workbooks, worksheets, .xlsx files, cells, or formulas.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Microsoft Excel integration') and a couple of actions ('Manage data, records, and automate workflows'), but those actions are abstract verbs rather than concrete operations like creating tables or formulas, so it stops at '1-2 concrete actions, not comprehensive' rather than reaching 'several specific actions.'	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Microsoft Excel data') are present, but the trigger is generic and lacks the concrete multi-phrase trigger list of a 5.	4 / 5
Trigger Term Quality	It repeats 'Microsoft Excel' and 'data' but omits the natural synonyms users actually say — spreadsheets, workbooks, worksheets, .xlsx, cells, formulas — placing it at 'some relevant keywords but missing common variations.'	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named product 'Microsoft Excel' gives it a clear niche with minimal conflict risk, but the narrow/generic 'interact with data' phrasing keeps it just short of comprehensive distinct triggers.	4 / 5
	Total	14 / 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: membranedev/application-skills
Path: skills/microsoft-excel/SKILL.md
Commit: f484c82

Reviewed: 6 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.