project-conventions
Core conventions and patterns for ExcelMcp
46
32%
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 ./.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 no distinguishing details. It reads more like an internal label than a functional skill description that Claude could use for skill selection.
Suggestions
Replace the vague phrase 'Core conventions and patterns' with specific actions like 'Analyze Excel spreadsheets, create pivot tables, format cells, generate charts using ExcelMcp'.
Add an explicit '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 read, write, or manipulate Excel workbooks'.
Include the natural keywords users would say (e.g., 'Excel', 'spreadsheet', '.xlsx', 'workbook', 'cells', 'rows', 'columns') 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 would 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, this would either never be selected or conflict with 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 for a specific codebase with strong actionability through concrete code examples and specific anti-patterns. Its main weaknesses are some redundancy between sections (triage pattern appears twice, exception propagation is emphasized in multiple places) and the lack of explicit validation checkpoints in multi-step workflows. The content would benefit from consolidating overlapping sections and splitting detailed testing/triage guidance into referenced files.
Suggestions
Consolidate the 'Bug Report Triage For Tests' and 'Triage Pattern' sections into a single section to eliminate redundancy and save tokens.
Add explicit validation checkpoints to multi-step workflows like the TDD cycle (e.g., 'verify test fails with expected assertion message before implementing') and bug triage (e.g., 'document findings at each step before proceeding').
Consider splitting the detailed testing patterns and error handling sections into separate referenced files (e.g., TESTING.md, ERROR_HANDLING.md) to keep the main skill lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and project-specific, but some sections are somewhat verbose with repeated emphasis on the same points (e.g., exception propagation patterns reiterated across multiple sections, triage pattern repeated in both 'Bug Report Triage' and 'Triage Pattern'). Some bullet points could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable code examples (correct vs incorrect exception handling), specific commands (dotnet test with filters), exact file paths, and clear do/don't patterns. The guidance is specific enough to be directly applied. | 3 / 3 |
Workflow Clarity | The TDD workflow (test FIRST → RED → implement → GREEN) and triage pattern provide sequencing, but there are no explicit validation checkpoints or feedback loops for multi-step processes like bug triage or implementing new features. The triage steps are listed but lack explicit 'if X then Y' recovery paths. | 2 / 3 |
Progressive Disclosure | The file structure section provides good navigation to the codebase, and content is organized into clear sections. However, the skill is quite long and some sections (testing, error handling, bug triage) could benefit from being split into referenced files. No external references are provided for deeper dives. | 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
468809e
- 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.