Name: microcks
Rating: 56.8 (1 reviews)
Author: membranedev

microcks

Microcks integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microcks data.

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/microcks/SKILL.md

Quality

Content

67%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 content is highly actionable with executable commands and a clear state-driven connection workflow, supported by good section organization. Its main weakness is conciseness: a marketing-style intro and redundant command repetition add padding without aiding execution.

Suggestions

Trim the marketing-style opening paragraph ('This allows teams to build and test applications without relying on complete, production-ready APIs') — Claude does not need Microcks' value proposition.

Remove the duplicated `membrane action list` command in 'Popular actions' (already shown in 'Searching for actions') and either list actual popular actions or delete the section.

Fix the dangling 'Step 2' reference and the orphan '1b' subsection heading so the connection workflow reads as a clean numbered sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the marketing-style opening ('This allows teams to build and test applications without relying on complete, production-ready APIs') and a duplicated `membrane action list` command add unnecessary tokens, fitting anchor 3 rather than 4.	3 / 5
Actionability	It provides many copy-paste-ready bash commands with real flags (login, connection ensure, action list/run, request proxy) covering common cases, but the hollow 'Popular actions' section merely redisplays the list command rather than listing concrete actions, keeping it at anchor 4.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with a state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED) and re-poll feedback loop, but a dangling 'Step 2' reference and an orphan '1b' heading leave minor gaps, matching anchor 4; this is not a destructive/batch skill so the validation cap does not apply.	4 / 5
Progressive Disclosure	No bundle files exist; the single-file body is well-organized into clearly headed sections with no nested references, appropriate for a ~130-line CLI guide, fitting anchor 4 though some detail (state machine, proxy flag table) could optionally be split out.	4 / 5
	Total	15 / 20 Passed

Description

62%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 third-person, includes an explicit 'Use when' trigger, and names a distinct product niche, but its action list is generic and lacks concrete Microcks-specific capabilities or trigger synonyms. It is solid but not comprehensive.

Suggestions

Replace generic verbs like 'Manage data, records' with concrete Microcks-specific actions (e.g., 'mock APIs, run contract tests, manage test artifacts and messages').

Add natural trigger synonyms users might say — such as 'API mocking', 'contract testing', or 'service simulation' — beyond just 'Microcks data'.

Tighten the 'what' clause so the listed capabilities are specific enough to distinguish this skill from generic data-management tools.

Dimension	Reasoning	Score
Specificity	Names the Microcks domain and lists action verbs ('Manage data, records, and automate workflows') but the actions are generic rather than concrete Microcks-specific capabilities, matching anchor 3 and falling short of the multi-specific anchor 4.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Microcks data') are present, but the 'what' is generic rather than concrete trigger phrases, so it sits at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Relevant keywords ('Microcks', 'data', 'records') appear with an explicit 'Use when' trigger, but common variations or synonyms users might say (e.g., 'mocking', 'contract testing', 'API simulation') are missing, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	Microcks is a named product giving it a clear niche with minimal conflict risk, but the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with other data-tool skills, matching anchor 4.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/microcks/SKILL.md
Commit: f484c82

Reviewed: 6 days 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.