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 lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
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 about setting up Mocha, configuring a test runner, creating test boilerplate, .mocharc configuration, or initializing a testing framework for Node.js projects.'
Remove the duplicate trigger term ('mocha test setup' is listed twice) and expand with varied natural phrases users might say like 'configure mocha', 'set up unit tests', 'test framework setup', 'mocha config'.
| 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 runner setup', '.mocharc', 'mocha config', 'testing framework', or 'unit test setup'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mocha' specifically does narrow the domain to a particular testing 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 essentially a placeholder with no actionable content. It repeatedly describes itself in abstract terms without providing any concrete guidance on Mocha test setup—no installation commands, no configuration examples, no code snippets, no workflow steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples: show `npm install mocha chai --save-dev`, a sample `.mocharc.yml` configuration, and a minimal test file with `describe`/`it` blocks.
Provide a clear step-by-step workflow: 1) Install dependencies, 2) Create config file, 3) Write first test, 4) Run `npx mocha` and verify output.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task—these waste tokens without adding value.
If advanced topics exist (e.g., mocking with sinon, async testing, CI integration), add brief examples inline or reference separate files with clear links.
| 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 restates the same vague idea—that it helps with 'mocha test setup'—without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance: no code examples, no commands, no configuration snippets, no specific steps for setting up Mocha. The content describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow or sequence of steps is provided. The skill claims to offer 'step-by-step guidance' but contains none. There are no validation checkpoints or any process description whatsoever. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured navigation, and no separation of overview from detailed content. The 'Related Skills' section mentions a category but links to nothing. | 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
3076d78
- 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.