Name: hello-retail
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

hello-retail

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

Quality

61%

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

Quality

Content

61%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 actionable and reasonably well-structured with concrete Membrane CLI commands and a clear connection state machine, but it leans slightly verbose and lacks validation feedback loops for destructive action/proxy operations.

Suggestions

Trim the marketing-style opening paragraph about Hello Retail and informal phrasing like 'burn less tokens' to tighten token efficiency.

Add an explicit validate/verify checkpoint after running actions or proxy mutations (e.g., re-fetch the record to confirm the change) to support destructive/batch operations.

Consider moving the proxy flags table and popular-actions catalog into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the marketing-style intro ('AI-powered personalization platform... helps retailers deliver personalized shopping experiences') and colloquial filler ('This will burn less tokens') could be trimmed; not a 4 due to these padded passages.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure/get, action list/run, request) with a flags table; minor gaps (e.g. placeholder CONNECTION_ID not fully wired) keep it from a 5.	4 / 5
Workflow Clarity	The connection setup is clearly sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the skill manages records and runs proxy requests that can be destructive/batch with no validation or verify-then-proceed feedback loop, capping it at 3.	3 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no bundle files needed; not a 5 because the proxy flags table and popular-actions block could live in a separate reference for a >50-line skill.	4 / 5
	Total	14 / 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 hits both 'what' and 'when' with an explicit trigger clause and a clear niche, but its action language is generic and its trigger vocabulary lacks synonyms or file/format cues.

Suggestions

Replace generic verbs ('Manage data, records') with specific Hello Retail actions (e.g., 'search products, manage orders and promotions, sync customer records').

Add concrete trigger phrases and synonyms a user would naturally say (e.g., 'Hello Retail data, product recommendations, orders, promotions').

Tighten the trigger clause to enumerate the entity types listed in the body (Customer, Order, Product, Promotion).

Dimension	Reasoning	Score
Specificity	Names the domain ('Hello Retail integration') and a couple actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete — not a 2 because it does list multiple actions, not a 4 because none are specific.	3 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Hello Retail data'); the 'when' is present but could be more specific with concrete trigger phrases, so not a 5.	4 / 5
Trigger Term Quality	Contains a natural trigger phrase ('Use when the user wants to interact with Hello Retail data'), but coverage is limited to 'Hello Retail'/'Hello Retail data' with no synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	The 'Hello Retail' niche is clearly distinct with its own trigger, minimal overlap risk; not a 5 because the action verbs ('manage data, records') are broad enough to overlap slightly with other CRM/data 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/hello-retail/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.