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

retailed

Retailed integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Retailed 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/retailed/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 a well-structured, mostly executable guide to driving Retailed through the Membrane CLI, with a strong connection-readiness feedback loop. Its main weaknesses are a padded intro, placeholder-heavy examples, an empty "Popular actions" section, and inconsistent step labels.

Suggestions

Remove the filler intro paragraph about what Retailed is and the 'so you can focus on the integration logic' commentary; assume Claude knows the domain.

Fix the step labeling: define Step 1 and Step 2 sections explicitly, or replace 'skip to Step 2' / '#### 1b' with consistent sequential headers.

Either populate 'Popular actions' with concrete, commonly-used action examples or rename the section so it does not promise a list it does not provide.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-oriented and efficient, but opens with unnecessary background ("Retailed is a retail management platform. It helps retailers manage inventory...") and includes a few commentary asides Claude does not need, so it could be tightened.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxying with a flag table, but several examples rely on placeholders and the "Popular actions" section only re-states the discovery command instead of listing actual popular actions.	4 / 5
Workflow Clarity	The connection flow is well sequenced with a real feedback loop (poll --wait, branch on READY/BUILDING/CLIENT_ACTION_REQUIRED, re-poll after user action), but references to an undefined "Step 2" and a "1b" header with no Step 1 introduce minor sequencing gaps.	4 / 5
Progressive Disclosure	The single self-contained file is organized into clearly labeled sections with easy navigation and no nested references, but the inconsistent step numbering and a "Popular actions" section that lists no actions leave minor organization gaps.	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 answers both what and when and is anchored to a distinct named platform, but its actions are a single generic verb applied to entities and its trigger leans on the brand name without richer natural keywords.

Suggestions

Replace the repeated generic 'Manage' with differentiated verbs (e.g., 'Create and update Organizations, invite Users, set Goals, apply Filters').

Expand the 'when' clause with concrete trigger phrases users would say, e.g. 'Use when the user wants to manage Retailed organizations, users, goals, or filters.'

Add common synonyms or the product's domain terms (e.g. 'retail operations', 'Retailed orders/products') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete entities ("Manage Organizations, Users, Goals, Filters"), but the only action verb is the generic "Manage" repeated for each, so the actions themselves are not differentiated.	3 / 5
Completeness	It states both what ("Manage Organizations, Users, Goals, Filters") and when ("Use when the user wants to interact with Retailed data"), but the 'when' is generic and could name concrete triggers more specifically.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Retailed data" relies on the brand name as the sole keyword and omits natural variations or the entity terms (Organizations, Users, Goals, Filters) a user might actually say.	3 / 5
Distinctiveness Conflict Risk	Tied to a named platform ("Retailed integration"), giving it a clear niche and distinct trigger, though the entity terms (Organizations, Users) are generic enough to risk minor overlap with other management skills.	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/retailed/SKILL.md
Commit: f484c82

Reviewed: 5 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.