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

remarkety

Remarkety integration. Manage data, records, and automate workflows. Use when the user wants to interact with Remarkety 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/remarkety/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 body is a well-structured, actionable Membrane-CLI guide with a genuinely clear connection lifecycle and state-machine checkpoints, but it carries a marketing-fluff intro and redundant action-list sections that waste tokens. Removing the intro and folding the redundant sections would improve conciseness without losing actionability.

Suggestions

Delete the marketing intro paragraph about e-commerce marketers; Claude does not need Remarkety's market positioning to use the CLI.

Merge the "Searching for actions" and "Popular actions" sections, which repeat the same `membrane action list` invocation, and add 1-2 concrete Remarkety action examples (e.g. list campaigns, fetch a contact).

Add a brief post-run validation note (e.g. check the `output` field and handle non-zero/error states) to close the workflow-verification gap on action execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete CLI commands, but the opening marketing paragraph ("Remarkety is an email marketing platform specifically designed for e-commerce businesses...") is padding Claude does not need, and the "Searching for actions" and "Popular actions" sections repeat the same action-list command, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides many copy-paste-ready executable commands (membrane login, connection ensure, action run, request) plus a proxy flag table, but the "Popular actions" section is thin (only instructs running action list with no actual Remarkety action examples), leaving minor gaps rather than full coverage.	4 / 5
Workflow Clarity	There is a clear sequence (install -> authenticate -> connect -> wait for READY -> search -> run -> proxy) with explicit state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll->act->re-poll feedback loop on the connection; minor gap is the absence of post-run verification for executed actions.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md carries everything; it is well-sectioned with clear headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices), but the redundant "Popular actions" section and all content inlined in one >50-line file leave minor organization gaps short of a clean 5.	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 with an explicit Use-when clause tied to a distinct named platform, but the capability list leans generic and the trigger term coverage is narrow (only 'Remarkety'/'Remarkety data'). Tightening the actions and adding natural synonyms would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Remarkety actions, e.g. "Create and send email campaigns, manage contacts and orders, issue coupons".

Broaden trigger terms with natural synonyms users say, e.g. "Use when the user wants to send Remarkety email campaigns, manage contacts/orders, or automate e-commerce marketing workflows."

Tie the Use-when clause to the entity types already in the body (campaigns, contacts, orders, products, coupons) so it triggers on more specific user phrasing.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Remarkety domain plus a few action phrases, but the actions (data, records) are generic rather than concrete like 'extract' or 'fill'; sits between anchor 2 (generic actions) and 3 (1-2 concrete actions).	3 / 5
Completeness	It states both a clear 'what' ("Manage data, records, and automate workflows") and an explicit 'Use when...' trigger clause; the 'when' is present and explicit but generic ('interact with Remarkety data') rather than enumerating concrete triggers, fitting anchor 4 rather than 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Remarkety data" includes "Remarkety" as a natural keyword but misses common synonyms and variations users might say (email marketing, campaigns, contacts, e-commerce), matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Remarkety is a specific named platform giving it a clear niche with minimal conflict risk, but the generic action words (manage data, automate workflows) leave minor overlap risk with other marketing/email skills when the user does not name Remarkety.	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/remarkety/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.