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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill mocha-test-setup40
Quality
11%
Does it follow best practices?
Impact
94%
1.28xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/mocha-test-setup/SKILL.mdDiscovery
22%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 severely underdeveloped, essentially just naming the skill without explaining what it does or when to use it. It relies entirely on the skill name 'Mocha Test Setup' to convey meaning, with no concrete actions, capabilities, or explicit usage triggers. The duplicate trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Configures Mocha test runner, creates test directory structure, generates mocharc configuration files, sets up test scripts in package.json'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when setting up Mocha, configuring test runner, creating test infrastructure, or when user mentions mocha.opts, .mocharc, or JavaScript testing setup'
Remove the duplicate trigger term and expand with variations users might naturally say: 'mocha config', 'setup testing', 'configure test framework', 'node testing setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Mocha Test Setup' and 'Test Automation' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'creates', 'configures', 'generates', etc. | 1 / 3 |
Completeness | The 'what' is extremely weak (just 'Test Automation' category mention) and there's no explicit 'when' clause. The triggers listed are just the skill name repeated, not meaningful usage guidance. | 1 / 3 |
Trigger Term Quality | Contains 'mocha test setup' as a trigger term (duplicated), which is a natural phrase users might say. However, it's missing common variations like 'mocha configuration', 'test framework setup', 'mocha.opts', '.mocharc', or 'testing with mocha'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Mocha' is specific enough to distinguish from other test frameworks (Jest, Vitest, etc.), but 'Test Automation' is generic and could overlap with other testing skills. The lack of specific capabilities makes it harder to distinguish from general testing skills. | 2 / 3 |
Total | 6 / 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 content is essentially a placeholder template with no actual Mocha-specific guidance. It describes what the skill claims to do but provides zero actionable information - no installation commands, no test file structure, no configuration examples, and no concrete steps for setting up Mocha tests.
Suggestions
Add executable code showing Mocha installation (`npm install mocha --save-dev`) and a minimal test file example with describe/it blocks
Include a concrete workflow: 1) Install dependencies, 2) Create test directory structure, 3) Configure package.json scripts, 4) Write first test, 5) Run and validate
Provide a working mocha configuration example (mocharc.js or package.json config) that can be copy-pasted
Remove generic boilerplate sections ('Purpose', 'Capabilities', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Mocha. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly but never shows how to actually set up Mocha tests - no installation commands, no test file examples, no configuration snippets. | 1 / 3 |
Workflow Clarity | No steps, sequences, or workflows are defined. The content only lists vague capabilities without any process for actually accomplishing Mocha test setup. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic descriptions with no structure pointing to detailed materials, examples, or reference documentation. No links to configuration guides or example files. | 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 | |
- 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.