project-conventions
Core conventions and patterns for ExcelMcp
36
32%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.squad/skills/project-conventions/SKILL.mdQuality
Discovery
0%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 description is critically underspecified. It provides no concrete actions, no natural trigger terms, no 'when to use' guidance, and nothing to distinguish it from other skills. It reads more like an internal label than a functional description that Claude could use for skill selection.
Suggestions
Replace the vague phrase 'Core conventions and patterns' with specific actions like 'Read, write, and analyze Excel spreadsheets, create pivot tables, generate charts, and format cells'.
Add a 'Use when...' clause with natural trigger terms such as 'Use when working with Excel files, spreadsheets, .xlsx files, tabular data, or when the user asks to create or modify workbooks'.
Include natural keywords users would say (e.g., 'Excel', 'spreadsheet', '.xlsx', 'workbook', 'cells', 'formulas') to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions no concrete actions whatsoever. 'Core conventions and patterns' is abstract language that does not describe what the skill actually does. 'ExcelMcp' names a tool but no capabilities are listed. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of capabilities. | 1 / 3 |
Trigger Term Quality | 'ExcelMcp' is a technical/internal tool name that users would not naturally say. There are no natural keywords like 'spreadsheet', 'Excel', '.xlsx', 'pivot table', or 'chart' that a user might use. | 1 / 3 |
Distinctiveness Conflict Risk | 'Core conventions and patterns' is extremely generic and could apply to virtually any skill. Without specific triggers or domain details, it would be impossible to distinguish this from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid conventions/patterns skill with strong actionability—concrete code examples, specific commands, and precise anti-patterns make it immediately useful. The main weaknesses are moderate verbosity (some sections repeat similar themes across testing, triage, and bug report sections) and the lack of progressive disclosure for what is a fairly long document that could benefit from splitting detailed testing and error handling guidance into separate referenced files.
Suggestions
Consider extracting the detailed Testing and Bug Report Triage sections into a separate TESTING.md file, keeping only a brief summary and reference in the main SKILL.md to improve progressive disclosure and conciseness.
Consolidate overlapping guidance between 'Bug Report Triage For Tests' and the 'Triage Pattern' section—they cover similar ground and could be merged into a single, tighter triage workflow with explicit decision checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and avoids explaining basic concepts, but some sections are verbose—particularly the testing and bug triage sections which repeat similar guidance in slightly different ways. The error handling section lists multiple bullet points that could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable code examples (correct vs incorrect exception propagation pattern), specific commands (dotnet test with filter syntax), exact file paths, and precise naming conventions. The guidance is specific enough to act on immediately. | 3 / 3 |
Workflow Clarity | The TDD workflow (test FIRST → RED → implement → GREEN) and triage pattern (check 3 things in order) are clearly sequenced, but the bug report triage and testing sections lack explicit validation checkpoints or feedback loops for error recovery. The triage pattern is good but could benefit from explicit decision gates. | 2 / 3 |
Progressive Disclosure | The file structure section provides good navigation to the codebase, and content is organized into logical sections (Patterns, Anti-Patterns, Triage). However, for a skill this long (~120 lines of dense content), some sections like Testing and Error Handling could be split into referenced files. No bundle files are provided to offload detail. | 2 / 3 |
Total | 9 / 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.
- Repository
- sbroenne/mcp-server-excel
- Commit
e8764a6
- 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.