Excel Macro Creator - Auto-activating skill for Business Automation. Triggers on: excel macro creator, excel macro creator Part of the Business Automation skill category.
35
3%
Does it follow best practices?
Impact
94%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/excel-macro-creator/SKILL.mdQuality
Discovery
7%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 extremely minimal and template-like, providing almost no actionable information for skill selection. It lacks concrete actions, meaningful trigger terms, and any 'Use when...' guidance. The duplicate trigger term and reliance on category labels rather than substantive description make it one of the weakest possible skill descriptions.
Suggestions
Add specific concrete actions such as 'Creates VBA macros for Excel spreadsheets, automates repetitive tasks, generates macro-enabled workbooks, and writes custom Excel functions'.
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks to create Excel macros, write VBA code, automate spreadsheet tasks, or build macro-enabled .xlsm files'.
Remove the duplicate trigger term and expand with natural variations users would say: 'VBA', 'macro', 'automate Excel', 'Excel script', 'spreadsheet automation', '.xlsm'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Excel Macro Creator') but does not describe any concrete actions. There are no specific capabilities listed like 'creates VBA macros', 'automates spreadsheet tasks', or 'generates macro code for data manipulation'. | 1 / 3 |
Completeness | The description barely addresses 'what' (only the name 'Excel Macro Creator') and completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill, and the category label 'Business Automation' is too vague to serve as trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'excel macro creator' repeated twice. This misses natural user phrases like 'VBA', 'macro', 'automate Excel', 'spreadsheet automation', 'Excel script', or '.xlsm'. The repetition adds no value. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Excel Macro' does narrow the domain somewhat, distinguishing it from general document or code skills. However, the lack of specificity about what it does could cause overlap with other Excel-related or automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an empty shell—a meta-description that describes what it would do without providing any actual content. It contains no VBA code, no macro creation steps, no concrete examples, and no actionable guidance whatsoever. It fails on every dimension because it is a placeholder rather than a functional skill.
Suggestions
Add concrete VBA code examples for common Excel macro tasks (e.g., auto-formatting, data processing, report generation) that are copy-paste ready.
Define a clear workflow for creating macros: e.g., 1) Open VBA editor, 2) Create module, 3) Write macro code, 4) Test with sample data, 5) Validate output.
Replace the meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) with actual instructional content—specific patterns, code templates, and best practices for Excel macro creation.
Add a quick-start section with a minimal working macro example and link to separate files for advanced topics like error handling, UserForms, or connecting to external data sources.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every line describes rather than instructs, wasting tokens on things like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Actionability | There is zero actionable content—no VBA code examples, no concrete steps for creating Excel macros, no commands, no specific patterns. The entire skill is a meta-description of what it claims to do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it 'provides step-by-step guidance' without including any actual steps. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to detailed files, and no navigation structure. The sections that exist (Capabilities, Example Triggers, Related Skills) are boilerplate metadata rather than progressive disclosure of useful information. | 1 / 3 |
Total | 4 / 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 | |
4dee593
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.