Name: marketplacer
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

marketplacer

Marketplacer integration. Manage Marketplaces. Use when the user wants to interact with Marketplacer data.

Quality

70%

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/marketplacer/SKILL.md

Quality

Content

78%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 CLI commands and a clear, checkpointed connection workflow, and it is largely token-efficient. Its main weakness is progressive disclosure: a large entity reference list and a flags table are inlined with no external reference files to route deeper detail to.

Suggestions

Move the ~50-item entity list into a references/ file (e.g., ENTITIES.md) and link to it from the overview to improve progressive disclosure.

Resolve the dangling 'skip to Step 2' reference by labeling the next section explicitly or removing the cross-reference.

Consider extracting the proxy-request flag table into a references/ file, keeping only a one-line usage example inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven prose that assumes Claude's competence, with only minor trimmable content such as the introductory platform sentence and the long inline entity list; it does not over-explain concepts Claude already knows, fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides copy-paste-ready, executable commands for every key operation (install, login, connection ensure/get, action list/run, request) plus a concrete proxy-flag table, covering the common cases per the 'fully executable; copy-paste ready commands' anchor.	5 / 5
Workflow Clarity	The connection workflow is a clear state-driven sequence with explicit checkpoints and feedback loops (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR branches, re-poll after user action), but the 'skip to Step 2' reference is dangling with no labeled Step 2, leaving a minor gap below the fully validated anchor 5.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but no bundle/reference files exist and content that would naturally live in separate files (the ~50-item entity list and the proxy-flag reference table) is inlined, matching 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	16 / 20 Passed

Description

61%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 trigger clause, and is clearly distinct as a branded integration, but it is let down by generic capability language ('Manage Marketplaces') and thin keyword variety. Tightening the 'what' with concrete actions would lift specificity and completeness.

Suggestions

Replace the generic 'Manage Marketplaces' with 2-3 concrete actions (e.g., 'Manage listings, orders, and inquiries') to raise specificity.

Expand the trigger to mention common user phrasings and entities (e.g., 'Use when the user wants to manage Marketplacer listings, orders, returns, or disputes').

Add file/data-object keywords users naturally say (e.g., 'Marketplacer API', 'marketplace orders') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Marketplacer integration') but its only action is the generic 'Manage Marketplaces', with no concrete capabilities enumerated, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a 'what' ('Marketplacer integration. Manage Marketplaces.') and an explicit 'Use when...' trigger, satisfying both; the 'what' is somewhat generic so it does not reach the fully concrete anchor 5, landing at 'has both what and when; when could be more specific'.	4 / 5
Trigger Term Quality	The natural keyword 'Marketplacer'/'Marketplaces' is present and paired with a 'Use when the user wants to interact with Marketplacer data' trigger, but coverage is limited to the brand name with no common variations or synonyms, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Marketplacer is a specific branded platform, giving the skill a clear niche with distinct triggers and minimal risk of firing for unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 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/marketplacer/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.