prism-mock-testing

Test a client against a Prism mock server built from an OpenAPI spec. Use when the user wants to test against a mock API, drive a client or harness through an OpenAPI spec, verify request payloads or 422 behavior against a spec, or when a task needs a local fake of a REST API for fast, deterministic testing.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

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

The body is a tight, well-sequenced four-step workflow with explicit validation checkpoints and feedback loops, backed by a real worked-example reference and harness script. It is executable and well-structured, with only minor conciseness and placeholder gaps in the code examples.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (no basic-concept padding); the intro paragraph and the Prism validation-behavior explanation orient usefully but could be trimmed slightly, fitting the 4 anchor over a clean 5.	4 / 5
Actionability	Provides concrete commands ('prism mock <spec> --port 13000 --cors --multiprocess=false') and a mostly executable harness example with per-scheme auth guidance, but the harness snippet relies on caller-supplied placeholders (base, token, watch paths), keeping it just short of copy-paste-ready 5.	4 / 5
Workflow Clarity	Four numbered steps each carry a 'Done when:' checkpoint, with explicit feedback loops for error recovery (crash → --multiprocess=false, taken port → pick another, Prism can't signal → harness asserts wire body), matching the 5 anchor.	5 / 5
Progressive Disclosure	Clear overview body with well-signaled, one-level-deep references to a real references/coolisimplify-example.md (gated on 'when the task touches this repo's clone/API flows') and scripts/prism-harness.mjs; both files exist and content is appropriately split.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

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

The description is specific, trigger-rich, and clearly distinguishes the skill's niche. It fully answers both 'what' and 'when' with concrete, natural language. Only minor synonym coverage is missing on the trigger dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Test a client against a Prism mock server', 'drive a client or harness through an OpenAPI spec', 'verify request payloads or 422 behavior', 'local fake of a REST API' — with comprehensive coverage, matching the 5 anchor.	5 / 5
Completeness	Explicitly answers both what ('Test a client against a Prism mock server built from an OpenAPI spec') and when ('Use when the user wants to test against a mock API...') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Good natural-term coverage with synonyms ('mock server', 'mock API', 'local fake of a REST API', 'OpenAPI spec', '422 behavior'), but a few natural variants (e.g. 'stub', 'fake server', 'schema validation') are absent, so it sits at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Prism mock + OpenAPI spec testing) with distinct triggers like '422 behavior against a spec' and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Voltaire405/coolisimplify
Path: .agents/skills/prism-mock-testing/SKILL.md
Commit: 036c7de

Reviewed: ~20 hours ago

Table of Contents

Discovery Implementation Validation

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.