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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill mocha-test-setupActivation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger guidance. It lacks concrete actions, natural user keywords, and explicit usage scenarios. The duplicate trigger term suggests minimal effort in crafting the description.
Suggestions
Add specific actions the skill performs, e.g., 'Configures Mocha test framework, creates test file structure, sets up describe/it blocks, configures reporters and assertions'
Add a 'Use when...' clause with natural trigger terms like 'Use when setting up Mocha tests, configuring test suites, creating unit tests with Mocha, or when the user mentions mocha.opts, test runners, or BDD-style testing'
Include file extensions and related terms users might mention: '.spec.js', '.test.js', 'chai assertions', 'before/after hooks', 'test coverage'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Mocha Test Setup' and 'Test Automation' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'creates test files', 'configures mocha', or 'generates test suites'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a duplicate trigger phrase. There's no explicit 'Use when...' clause explaining scenarios where this skill should be selected. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('mocha test setup' listed twice) and very narrow. Missing natural variations users might say like 'unit tests', 'testing framework', 'test configuration', 'describe/it blocks', or 'test runner setup'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mocha' specifically does provide some distinctiveness from generic testing skills, but 'Test Automation' is broad and could overlap with Jest, Jasmine, or other testing framework skills. The lack of specific Mocha-related triggers weakens differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is essentially a placeholder with no substantive content. It describes what a Mocha test setup skill should do without actually providing any guidance on how to set up Mocha tests. The entire content could be replaced with a single code block showing Mocha installation and a basic test file, which would be far more useful.
Suggestions
Add executable code showing Mocha installation (`npm install --save-dev mocha`) and basic configuration (package.json test script, mocha.opts or .mocharc.js)
Include a minimal working test file example with describe/it blocks and assertions
Remove the meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual setup instructions
Add common patterns like async test handling, hooks (before/after), and assertion library integration (chai)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains obvious concepts Claude already knows. Phrases like 'provides automated assistance' and 'follows industry best practices' add no value and waste tokens. | 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 configuration examples, no test file templates. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There's no sequence for setting up Mocha, no validation checkpoints, nothing actionable. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with clear headers, but there are no references to detailed materials, no links to examples or advanced configurations. The structure exists but leads nowhere useful. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.