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

Blog Docs Log in Get started

markettime

MarketTime integration. Manage Organizations. Use when the user wants to interact with MarketTime 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

75%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 highly actionable with concrete, executable Membrane CLI commands and a clear connection-state workflow including feedback loops, though it carries some marketing-style padding and a couple of minor structural inconsistencies.

Suggestions

Trim the introductory prose ("B2B platform connecting manufacturers... streamline the wholesale buying process") and the "auth plumbing" commentary to assume Claude's competence and reclaim tokens.

Resolve the dangling "Step 2" reference by labeling the subsequent section explicitly (e.g., "## Step 2: Discover and run actions").

Add a brief validation/check step for `membrane request` and `membrane action run` outputs (e.g., inspect the `output`/`error` field before proceeding) to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ("streamline the wholesale buying process") and lines like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding, fitting the mostly-efficient-with-some-over-explanation anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands with real flags (install, login, connection ensure/get, action list/run, request) covering the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	There is a clear install→auth→connect→search→run sequence with an explicit connection-state feedback loop (BUILDING poll, CLIENT_ACTION_REQUIRED re-poll, CONFIGURATION_ERROR error check), but a dangling "Step 2" reference and no validation on proxy/action results leave minor gaps below the 5 anchor.	4 / 5
Progressive Disclosure	The content is well-organized into clearly labeled self-contained sections with no bundle files to navigate, fitting the good-structure anchor; minor redundancy between "Searching for actions" and "Popular actions" keeps it just below 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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 cleanly states what the skill does and when to use it with an explicit trigger clause and a highly distinctive brand name, but it lists only one concrete action and offers a narrow set of trigger terms.

Suggestions

Expand the capability list beyond "Manage Organizations" to the other core entities (e.g., Orders, Products, Customers, Sales Reps) so specificity reaches comprehensive coverage.

Broaden the "Use when" clause with concrete trigger phrases users would actually say, such as "when the user wants to manage MarketTime orders, products, or sales rep accounts".

Consider naming the integration medium (Membrane) in the description so it is distinguishable from any other MarketTime-related skill.

Dimension	Reasoning	Score
Specificity	Names the MarketTime domain plus one concrete action ("Manage Organizations"), matching the anchor for 1-2 concrete actions that are not comprehensive; it is not a 2 because "Manage Organizations" is more concrete than the generic "Processes PDF files" anchor.	3 / 5
Completeness	Both "what" ("MarketTime integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with MarketTime data.") are present, but the single trigger phrase could be more specific, so it stops short of the multi-trigger anchor at 5.	4 / 5
Trigger Term Quality	"MarketTime" and "MarketTime data" are relevant natural keywords, but common variations a user might say (orders, products, catalogs, sales reps) are missing, fitting the anchor for some relevant keywords lacking synonyms.	3 / 5
Distinctiveness Conflict Risk	"MarketTime" is a distinct proper-noun niche with a brand-specific trigger ("interact with MarketTime data"), giving minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/markettime/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.