Name: crobox
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

crobox

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

Quality

72%

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

Quality

Content

78%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 highly actionable with executable Membrane CLI commands and a clear connection-state workflow including a retry loop. Its main weaknesses are an unresolved 'Step 2' reference and the absence of any progressive disclosure to separate reference files for the detailed state/flag material.

Suggestions

Resolve the dangling 'Step 2' reference: either label the 'Searching for actions' section as Step 2 or remove the cross-reference, and renumber '1b' into a coherent 1/2 sequence.

Move the detailed clientAction state semantics and the proxy flags table into a separate reference file (e.g. references/connections.md and references/proxy.md) and link to them from the body to improve progressive disclosure.

Trim the marketing-style opening paragraph about what Crobox is down to a single sentence, since the rest of the skill already implies the integration purpose.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands with a useful proxy flag table, but the opening marketing-style paragraph ('It uses AI to personalize... increase conversion rates and average order value') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are minor over-explanation that could be trimmed.	4 / 5
Actionability	Provides copy-paste ready commands for the common cases (install, login, connection ensure, action list/run, proxy) with documented placeholders and a flags table, matching the 'fully executable, copy-paste ready, covers common cases' anchor.	5 / 5
Workflow Clarity	The connection setup has a clear state-based sequence with a retry feedback loop (poll after CLIENT_ACTION_REQUIRED until READY), but 'skip to Step 2' references a Step 2 that is never labeled, and the '1b' numbering has no '1a'/'Step 1', leaving a navigation gap that keeps it below 5.	4 / 5
Progressive Disclosure	The body is well-sectioned with headers but all content is inlined in a single ~150-line file with no external references, and since it exceeds 50 lines the simple-skill exception does not apply, matching the 'some structure but content that should be separate is inline, no references' anchor.	3 / 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 is third-person, names the product, and includes both a 'what' and a 'when' clause, but the listed capabilities are generic and the trigger phrasing lacks concrete variations. Distinctiveness is strong thanks to the unique Crobox name.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with concrete Crobox capabilities (e.g., 'run experiments, manage segments, fetch personalized recommendations') to lift specificity.

Expand the 'Use when' clause with concrete trigger phrases users would naturally say, such as 'when the user mentions Crobox experiments, variants, segments, or integrations'.

Add common synonyms or object names (experiments, variants, segments) so the trigger terms cover how users actually refer to Crobox features.

Dimension	Reasoning	Score
Specificity	Names the Crobox domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, so it sits at the 'names domain and 1-2 actions, not comprehensive' anchor rather than the more specific 4.	3 / 5
Completeness	Both 'what' ('Crobox integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Crobox data') are present, but the 'when' could be more explicit with concrete trigger phrases, so it is below the 5 anchor.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Crobox', 'interact with Crobox data') but offers few natural variations or synonyms a user might say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The unique product name 'Crobox' anchors a clear niche with distinct triggers and minimal conflict risk with other skills, matching the top anchor.	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/crobox/SKILL.md
Commit: f484c82

Reviewed: ~14 hours 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.