Name: mockaroo
Rating: 53.6 (1 reviews)
Author: membranedev

mockaroo

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

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

57%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 concrete Membrane CLI commands and a clear connection workflow, but it is held back by padding, a broken "Step 2" reference, and missing validation guidance before destructive proxy requests. Organization is decent but has redundant sections and a useless overview block.

Suggestions

Remove the cryptic "Mockaroo Overview" bullet list and de-duplicate the `action list` command that appears in both "Searching for actions" and "Popular actions".

Fix the dangling "skip to Step 2" reference by labeling the action-search/run section as Step 2, or reword to "skip to Running actions".

Add a validation checkpoint before destructive proxy requests (e.g. confirm the HTTP method and target before running POST/PUT/DELETE, and inspect the response status).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational guidance, but it includes padding: a cryptic "Mockaroo Overview" bullet list (Schema/Field/API Call) that adds nothing, a redundant restatement of the `action list` command across "Searching for actions" and "Popular actions", and an intro paragraph restating what Mockaroo is, matching the score-3 anchor of mostly efficient with some unnecessary content.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests with a concrete flag table, but uses placeholders (CONNECTION_ID, actionId) and lacks a worked Mockaroo-specific example such as generating a schema or records, fitting score 4 with minor gaps.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state-check checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll feedback loop, but the action-running and proxy workflows lack validation before destructive operations (POST/PUT/DELETE via proxy), and the "skip to Step 2" reference points to a non-existent Step 2, so the destructive-operation cap holds it at 3.	3 / 5
Progressive Disclosure	At ~150 lines with no bundle files, all content is inline under reasonable section headers, but the cryptic overview section, the duplicated action-listing sections, and the inline proxy/clientAction reference blocks that could live in separate files match the score-3 anchor of some structure that could be better organized.	3 / 5
	Total	13 / 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 correctly includes an explicit "Use when" trigger and names the target app, giving it solid completeness and distinctiveness. It is held back by generic action verbs and a thin set of natural trigger terms that miss common synonyms like "test data" or "generate".

Suggestions

Replace generic verbs with concrete Mockaroo actions, e.g. "generate realistic test data, define schemas, and download records in CSV/JSON".

Expand the trigger clause to list natural phrases users say, e.g. "Use when the user wants to generate test data, sample data, or fake records with Mockaroo".

Dimension	Reasoning	Score
Specificity	Names the Mockaroo domain and a few action areas ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete actions like "generate test data" or "populate databases", matching the score-3 anchor of domain plus 1-2 actions that are not comprehensive.	3 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Mockaroo data"), but the when clause offers only one trigger phrase rather than several concrete triggers, matching score 4 rather than 5.	4 / 5
Trigger Term Quality	It includes the named tool "Mockaroo" plus "data", "records", and "workflows", but misses common natural variations users would say such as "test data", "sample data", "fake data", or "generate", fitting the score-3 anchor of relevant keywords with missing synonyms.	3 / 5
Distinctiveness Conflict Risk	The specific named app "Mockaroo" gives it a clear niche with minimal conflict risk, but the generic "Manage data, records, and automate workflows" phrasing could overlap with other data-handling skills, placing it at 4 rather than 5.	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/mockaroo/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.