Name: robly
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

robly

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/robly/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 a well-structured, executable guide to driving Robly through the Membrane CLI, weakened mainly by marketing-fluff padding and a broken step reference with no error-recovery guidance.

Suggestions

Delete the opening marketing paragraph about SMBs and ROI; lead directly with what the skill does and the CLI prerequisite.

Fix the "skip to Step 2" reference by labeling the post-connection steps (e.g. "Step 2: Search for actions", "Step 3: Run actions") so the sequence is unambiguous.

Add a short error-recovery note for `membrane action run` failures (check `error` field, retry or fall back to `membrane request` proxy) to give the workflow a validation feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening marketing paragraph ("designed to help small to medium-sized businesses automate and optimize their email campaigns...overall marketing ROI") and phrases like "so you can focus on the integration logic rather than auth plumbing" are padding Claude does not need, fitting the 3 anchor.	3 / 5
Actionability	It provides copy-paste-ready membrane commands (login, connection ensure, action list/run, request) plus a flags table, but the "Popular actions" heading only rediscovers actions rather than listing any, leaving a minor gap that keeps it at 4 rather than 5.	4 / 5
Workflow Clarity	A rough sequence exists (install → auth → connect → poll for READY → search → run) with state checkpoints, but the text references a "Step 2" that is never labeled and offers no error-recovery feedback loop for failed action runs, matching the 3 anchor.	3 / 5
Progressive Disclosure	The content is well-organized into clearly headed sections with no nested references and no bundle files to mislink; the only gap is that the detailed connection-state handling and flags table are inlined rather than split out, sitting at 4 rather than 5.	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 answers both what and when and is anchored to a specific named app, but its action vocabulary is generic and its trigger terms miss the email-marketing concepts users would naturally mention.

Suggestions

Replace the generic verb "Manage" with concrete operations, e.g. "Create and manage Organizations and Users, search and run Robly API actions."

Add natural trigger terms users would say — e.g. "Use when the user wants to manage Robly email campaigns, lists, subscribers, or contacts."

Tighten the "when" clause to reference concrete Robly objects (campaigns, lists, subscribers) instead of the generic "interact with Robly data".

Dimension	Reasoning	Score
Specificity	It names the domain ("Robly integration") and two concrete entities ("Organizations, Users"), but the verb "Manage" is generic and coverage is not comprehensive — matching the 3 anchor "Names domain and 1-2 concrete actions, but not comprehensive."	3 / 5
Completeness	Both "what" ("Robly integration. Manage Organizations, Users.") and "when" ("Use when the user wants to interact with Robly data.") are present, but the "when" clause is generic rather than concrete triggers, fitting the 4 anchor over the 5.	4 / 5
Trigger Term Quality	"Robly", "Organizations", and "Users" are relevant terms, but the description omits the natural vocabulary users actually use for this app (campaigns, lists, subscribers, email marketing) that appears in the body, matching the 3 anchor for some keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The proper noun "Robly" gives it a clear niche with minimal conflict risk, but the generic "Manage Organizations, Users" phrasing could overlap with CRM-style skills, so it sits at 4 rather than 5.	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/robly/SKILL.md
Commit: f484c82

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