Excel CLI automation skill for Windows workbooks. Use when a coding agent needs token-efficient, scriptable, or unattended Excel automation via excelcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk workbook edits. Supports Power Query, DAX, PivotTables, Tables, Ranges, Charts, VBA, Data Models, screenshots, and formatting. Triggers: excelcli, Excel CLI, command line, batch, script, automation, CI/CD, scheduled, PowerShell, unattended, coding agent, workbook processing.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its niche (CLI-based Excel automation on Windows), lists comprehensive capabilities, provides explicit trigger guidance with a 'Use when' clause and enumerated trigger terms, and distinguishes itself well from general Excel manipulation skills. The description is information-dense without being padded, and uses appropriate third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: Power Query, DAX, PivotTables, Tables, Ranges, Charts, VBA, Data Models, screenshots, formatting, batch processing, bulk workbook edits. Also specifies the tool (excelcli) and platform (Windows). | 3 / 3 |
Completeness | Clearly answers both 'what' (Excel CLI automation for Windows workbooks with specific capabilities listed) and 'when' (explicit 'Use when' clause plus 'Best for' scenarios plus explicit 'Triggers' list). All three components are well-defined. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'excelcli', 'Excel CLI', 'command line', 'batch', 'script', 'automation', 'CI/CD', 'scheduled', 'PowerShell', 'unattended', 'coding agent', 'workbook processing'. These are terms users would naturally use when needing CLI-based Excel automation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — clearly differentiates itself from general Excel skills by focusing specifically on CLI/command-line automation, unattended processing, and scripting contexts. The emphasis on 'excelcli commands', 'token-efficient', 'CI/CD', and 'coding agent' creates a clear niche that wouldn't overlap with interactive Excel editing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides highly actionable guidance with executable PowerShell examples throughout. The workflow is clearly sequenced with validation steps and error handling. The main weakness is moderate redundancy in session ID handling patterns repeated across multiple rules, which could be consolidated to save tokens.
Suggestions
Consolidate the session ID capture pattern (shown in Rules 3, 5, and 7) into a single reusable example referenced by the other rules, reducing repetition by ~20 lines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts, but there's some redundancy — e.g., session ID capture is demonstrated multiple times across Rules 3, 5, and 7 with similar patterns. The 'CRITICAL' callouts and repeated emphasis on session IDs add bulk. Some tightening is possible. | 2 / 3 |
Actionability | Excellent actionability throughout — every rule includes concrete, executable PowerShell commands with realistic arguments. The batch mode JSON format, Power Query lifecycle, and calculation mode examples are all copy-paste ready with specific flags and syntax. | 3 / 3 |
Workflow Clarity | The workflow checklist table at the top provides a clear sequence. Individual rules like Power Query (Rule 5) and bulk writes (Rule 7) have explicit numbered steps with validation checkpoints (e.g., 'Test M code before creating permanent queries', 'Recalculate once at end'). Rule 6 provides an explicit error-handling stop condition. Batch mode includes --stop-on-error for error recovery. | 3 / 3 |
Progressive Disclosure | The skill provides a well-structured overview with clear sections, then references a single external file (./references/cli-commands.md) for the full command reference and common pitfalls. Navigation is one level deep and clearly signaled with links. The inline content is appropriately scoped to critical rules and workflows. | 3 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
468809e
Table of Contents
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.