excel-pivot-wizard
Create advanced Excel pivot tables with calculated fields and slicers. Use when building data summaries or creating interactive dashboards. Trigger with phrases like 'excel pivot', 'create pivot table', 'data summary'.
72
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/business-tools/excel-analyst-pro/skills/excel-pivot-wizard/SKILL.mdQuality
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 well-crafted skill description that clearly defines its scope (Excel pivot tables with calculated fields and slicers), provides explicit 'Use when' guidance, and includes natural trigger phrases. It is concise, specific, and distinctive enough to avoid conflicts with broader data analysis or spreadsheet skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create advanced Excel pivot tables with calculated fields and slicers.' This names the domain (Excel), the core action (create pivot tables), and specific features (calculated fields, slicers). | 3 / 3 |
Completeness | Clearly answers both 'what' (create advanced Excel pivot tables with calculated fields and slicers) and 'when' (when building data summaries or creating interactive dashboards), with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'excel pivot', 'create pivot table', 'data summary', 'interactive dashboards'. These are terms users would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Excel pivot tables specifically, with distinct triggers like 'excel pivot' and 'create pivot table' that are unlikely to conflict with general spreadsheet or data analysis skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a high-level outline than actionable guidance. It describes what to do at a conceptual level but never shows how—no Excel formulas, no VBA/Python code, no specific UI steps, and no concrete calculated field examples. The error handling table is a nice touch, but the lack of executable content severely limits its usefulness.
Suggestions
Add concrete, executable examples: include actual calculated field formulas (e.g., `=Revenue - Cost`), specific VBA or openpyxl code for creating pivot tables programmatically, or step-by-step Excel UI instructions.
Include at least one complete worked example with real sample data, showing the exact fields, formulas, and slicer configuration rather than just describing the desired outcome.
Add validation checkpoints to the workflow, such as 'Verify pivot table displays expected aggregations before adding calculated fields' and 'Test slicer filtering updates all connected pivot tables'.
Either provide the referenced `pivot-formulas.md` bundle file or remove the reference; currently it points to a non-existent resource.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'Prerequisites' (Claude knows what tabular data is) and the 'Overview' restates the description. The error handling table and output section add moderate value but could be tighter. | 2 / 3 |
Actionability | The instructions are entirely abstract ('Create pivot table from data range', 'Add calculated fields') with no concrete code, formulas, VBA/Python snippets, or specific Excel steps. The examples describe outcomes but provide no executable guidance on how to achieve them. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence, but there are no validation checkpoints (e.g., verifying the pivot table renders correctly before adding slicers), no feedback loops for error recovery, and the steps are too high-level to guide a multi-step process reliably. | 2 / 3 |
Progressive Disclosure | There is a reference to a bundle file (`pivot-formulas.md`) and an external resource, which is good structure. However, the bundle file doesn't actually exist, and the main content could benefit from splitting detailed calculated field syntax and slicer configuration into separate referenced files rather than leaving the body both shallow and monolithic. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.