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

Blog Docs Log in Get started

rex

Rex integration. Manage data, records, and automate workflows. Use when the user wants to interact with Rex 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/rex/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, actionable Membrane CLI integration guide with strong command coverage and a solid connection workflow. Its weaknesses are mild padding in the intro, placeholder-heavy examples, and missing validation guidance for destructive proxy/action operations.

Suggestions

Trim the introductory Rex description and the 'auth plumbing' commentary so the body assumes Claude's competence and leads with action.

Add an explicit validation/verification checkpoint after destructive proxy requests (e.g., re-fetch the resource or check the response status) and after batch action runs, so the workflow includes a validate-fix-retry loop.

Provide at least one fully-resolved example command (real connectionId and a concrete intent) so the guidance is copy-paste ready without substitution.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening Rex description and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation that could be trimmed, fitting anchor 3.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands (install, login, connection ensure, action list/run, request) plus a flags table, but placeholders like CONNECTION_ID, <agentType>, and QUERY require substitution, leaving minor gaps at anchor 4.	4 / 5
Workflow Clarity	Connection setup is well sequenced with state polling and a poll-again feedback loop, but destructive operations (proxy DELETE/PUT and action run) lack validation/verification checkpoints, so workflow clarity is capped at 3 per the batch/destructive rule.	3 / 5
Progressive Disclosure	With no bundle files present, the content is well organized into clear inline sections (Install, Authentication, Connecting, Searching, Proxy) appropriately scoped for an integration guide, matching anchor 4 with only minor organization gaps.	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 clearly identifies the Rex niche and includes both a 'what' and an explicit 'Use when' trigger clause. Its main weakness is generic action verbs and limited keyword/synonym coverage.

Suggestions

Replace generic verbs with concrete Rex actions (e.g., 'create and track jobs, manage job outputs, review account usage and billing') to lift specificity.

Expand the 'Use when' clause with more natural trigger phrases and synonyms a user would actually say (e.g., 'Use when the user mentions Rex records, job outputs, or wants to automate Rex workflows').

Add the file/extension or entity terms users associate with Rex to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (Rex data, records) and lists a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete, so it sits at the anchor-3 level rather than higher.	3 / 5
Completeness	It gives a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Rex data'), but the trigger phrasing is narrow and could be more specific, fitting anchor 4 rather than 5.	4 / 5
Trigger Term Quality	'Rex data', 'records', and 'workflows' are relevant keywords, but common variations or synonyms are missing, matching the 'some relevant keywords' anchor rather than the comprehensive one.	3 / 5
Distinctiveness Conflict Risk	'Rex integration' targets a specific app niche with a distinct trigger, but the generic 'manage data, records, workflows' language carries minor overlap risk, placing it just below the minimal-conflict anchor.	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/rex/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.