excel-pivot-wizard
Generate pivot tables and charts from raw data using natural language - analyze sales by region, summarize data by category, and create visualizations effortlessly Activates when you request "excel pivot wizard" functionality.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill excel-pivot-wizard60
Quality
47%
Does it follow best practices?
Impact
78%
1.39xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skill-structure-cleanup-20251108-073936/plugins/business-tools/excel-analyst-pro/skills/excel-pivot-wizard/SKILL.mdDiscovery
60%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 excels at listing specific capabilities with concrete examples like pivot tables, charts, and data summarization. However, it relies on an artificial activation phrase ('excel pivot wizard') that users wouldn't naturally say, undermining its effectiveness for skill selection. The description also uses second person ('when you request') which violates the third-person voice guideline.
Suggestions
Replace the artificial trigger phrase with natural user language: 'Use when the user asks to create pivot tables, analyze data by categories, summarize spreadsheet data, or generate charts from tabular data.'
Add common file type triggers: '.xlsx', 'Excel files', 'spreadsheets', 'CSV data'
Convert to third person voice: 'Activates when users request...' or better, use 'Use when...' format
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate pivot tables and charts', 'analyze sales by region', 'summarize data by category', and 'create visualizations'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific capabilities, but the 'when' clause requires users to say the exact phrase 'excel pivot wizard' rather than describing natural trigger scenarios. This artificial trigger doesn't help Claude select the skill based on user intent. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'pivot tables', 'charts', 'sales', 'data', but the activation trigger 'excel pivot wizard' is an artificial phrase users wouldn't naturally say. Missing common variations like 'spreadsheet', 'Excel', '.xlsx', 'data analysis'. | 2 / 3 |
Distinctiveness Conflict Risk | The pivot table and chart focus provides some distinction, but 'analyze data', 'summarize by category', and 'create visualizations' could overlap with general data analysis or charting skills. The artificial trigger phrase doesn't help real-world disambiguation. | 2 / 3 |
Total | 9 / 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 is excessively verbose, treating Claude like it needs extensive hand-holding with sample outputs and insights. It lacks actual executable code for interacting with the Excel MCP server, instead providing conceptual descriptions. The content would benefit from being 80% shorter with actual API calls replacing the verbose example interactions.
Suggestions
Replace the verbose 'Example Interactions' section with actual MCP server API calls showing how to create pivot tables programmatically
Move the extensive sample outputs and 'Common Analysis Patterns' to a separate EXAMPLES.md file, keeping only one brief example in the main skill
Add concrete validation steps: how to verify a pivot table was created successfully, error handling for invalid data or missing columns
Remove explanatory text about what pivot tables are and what insights mean - Claude already knows this; focus only on the specific MCP server interface
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines with extensive example outputs that Claude doesn't need. The skill explains basic concepts like what pivot tables do, includes lengthy sample data tables, and provides verbose 'insights' that pad the content unnecessarily. | 1 / 3 |
Actionability | Provides conceptual guidance and example outputs but lacks actual executable code. The 'Build the Pivot Table' section says 'Use Excel MCP server to:' but provides no actual API calls or code snippets showing how to interact with the MCP server. | 2 / 3 |
Workflow Clarity | Has a 5-step workflow but lacks validation checkpoints. No error handling, no verification that the pivot table was created correctly, and no feedback loops for when operations fail. Steps are conceptual rather than concrete. | 2 / 3 |
Progressive Disclosure | References external files (REFERENCE.md, examples/) but the main content is a monolithic wall of text with extensive inline examples that should be in separate files. The 'Example Interactions' section alone could be its own reference document. | 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 | |
- 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.