CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/mountebank-imposters

Authors Mountebank imposters (multi-protocol mock servers - HTTP, HTTPS, TCP, SMTP, LDAP, gRPC, WebSockets, GraphQL, and more) by POSTing JSON definitions to the Mountebank control API on port 2525, configures stubs with predicates and responses, and uses record-playback proxy mode to capture upstream traffic. Use when the project needs a multi-protocol mock server beyond HTTP-only tools like WireMock or MSW.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with executable examples, a validation-gated workflow, and clean one-level-deep progressive disclosure. The only weakness is mild repetition of the record-playback and multi-protocol themes across sections that slightly inflates the token budget.

Suggestions

Collapse the repeated record-playback explanation between 'When to use', 'Authoring imposters > Proxying', and the worked example into a single forward reference to keep the body leaner.

Trim the Overview, which restates the frontmatter description almost verbatim, to a one- or two-line framing that points straight at 'When to use' and 'How to use'.

Condense the 'Docs-domain note' block to a single line in the Limitations section rather than a multi-line callout in the Overview.

DimensionReasoningScore

Conciseness

Mostly efficient with executable, tight examples and no beginner-concept padding, but the Overview re-states the description and several themes (record-playback, multi-protocol) recur across 'When to use', 'Authoring', and the worked example, so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready curl POST, JSON stub blocks, JS integration code, a CI workflow, and a worked proxy example — fully executable guidance rather than abstract direction.

3 / 3

Workflow Clarity

'How to use' is a clear numbered sequence with an explicit validation checkpoint (step 4: GET /imposters, assert 200, diagnose a missing stub → fix JSON, re-POST) and teardown (DELETE) with a feedback loop for error recovery.

3 / 3

Progressive Disclosure

SKILL.md is a well-signaled overview that delegates the full operator/mode tables to one real, one-level-deep file (references/predicates-and-proxying.md), verified to exist, with easy navigation and no deep nesting.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that pairs concrete capabilities with an explicit 'Use when' trigger and a distinctiveness contrast against WireMock/MSW. It hits all four dimensions at the top anchor without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'POSTing JSON definitions to the Mountebank control API on port 2525', 'configures stubs with predicates and responses', 'uses record-playback proxy mode to capture upstream traffic' — each tied to a specific mechanism, not vague.

3 / 3

Completeness

Explicitly answers both what (the POSTing/configuring/proxying actions) and when via the 'Use when the project needs a multi-protocol mock server beyond HTTP-only tools like WireMock or MSW' trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say ('mock server', 'multi-protocol', 'record-playback', protocol names) and names comparable tools ('WireMock or MSW'); jargon like 'imposters' is balanced by accessible framing.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (multi-protocol mocking) and explicitly contrasts against HTTP-only tools, making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents