mocha-test-setup
Mocha Test Setup - Auto-activating skill for Test Automation. Triggers on: mocha test setup, mocha test setup Part of the Test Automation skill category.
35
3%
Does it follow best practices?
Impact
94%
1.28xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/mocha-test-setup/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 essentially just restates the skill name without providing any useful information about what the skill actually does or when it should be selected. It reads like auto-generated boilerplate rather than a crafted description. The duplicate trigger term ('mocha test setup' listed twice) suggests a template was filled in without thought.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures Mocha test runner, creates .mocharc.yml files, sets up test directory structure, and generates boilerplate test files with describe/it blocks.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to set up Mocha, configure a test runner, create test boilerplate, initialize testing in a Node.js project, or mentions .mocharc, mocha config, or test framework setup.'
Remove the duplicate trigger term and expand with varied natural language terms users might use, such as 'mocha configuration', 'test setup', 'testing framework', 'unit tests', 'Node.js testing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Mocha Test Setup' and 'Test Automation' without describing any concrete actions. There are no specific capabilities listed like 'configure mocha config files', 'set up test runners', or 'create test boilerplate'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just the skill name repeated as a trigger. There is no explicit 'Use when...' guidance with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'mocha test setup' repeated twice. Missing natural variations users would say like 'mocha configuration', 'test framework setup', '.mocharc', 'mocha config', 'testing setup', 'unit test setup', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mocha' specifically narrows the domain to a particular test framework, which provides some distinctiveness. However, the vague 'Test Automation' category and lack of specific actions could overlap with other testing-related 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 an empty shell with no actual instructional content. It consists entirely of meta-descriptions about what the skill would do without providing any concrete guidance on Mocha test setup—no installation commands, no configuration examples, no test file templates, no assertions patterns. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples: show a minimal Mocha test setup including `npm install mocha`, a sample `.mocharc.yml` configuration, and a basic test file with `describe`/`it` blocks and assertions.
Replace the abstract 'Capabilities' and 'Example Triggers' sections with an actionable quick-start workflow: install → configure → write first test → run and validate output.
Include specific Mocha configuration patterns (e.g., TypeScript setup, async testing, reporter configuration) either inline or via clearly referenced companion files.
Add validation steps such as verifying the test runner works (`npx mocha --dry-run` or checking exit codes) to ensure the setup is correct before proceeding.
| 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 technical content. Every section describes rather than instructs, wasting tokens on information Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no configuration snippets, no specific steps for setting up Mocha tests. The content is entirely vague and abstract, describing capabilities without demonstrating any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no meaningful structure. There are no references to detailed files, no quick-start section, and no navigation to deeper content. The sections that exist are all boilerplate. | 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 | |
- Commit
3e83543
- 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.