Name: redox
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

redox

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

Quality

66%

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

Quality

Content

71%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 concrete, executable Membrane CLI commands and solid validation checkpoints around connection state polling. Its weaknesses are unnecessary introductory prose, loose step numbering, and a lack of progressive disclosure via separate reference files despite a fairly long single-file body.

Suggestions

Remove or trim the opening explanatory paragraph about what Redox is; Claude can infer the platform's purpose and the description already covers it.

Fix the step numbering so 'skip to Step 2' points to an explicitly labeled Step 2 (e.g., Searching for actions), and number the connection sub-steps consistently.

Move the Redox data model overview and/or the proxy flags reference into separate bundle files (e.g., references/data-model.md, references/proxy.md) and link them from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable code blocks and a flags table, but it includes unnecessary explanatory prose ('Redox is a platform for healthcare data exchange. It helps healthcare organizations...') that Claude does not need, matching the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests, plus a complete flags table, covering the common cases fully, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The install -> authenticate -> connect -> search -> run flow has explicit polling checkpoints and feedback loops (poll again after CLIENT_ACTION_REQUIRED, check READY/CONFIGURATION_ERROR states), but step numbering is loose ('skip to Step 2' with no matching Step 2 heading), a minor validation gap below the score-5 anchor.	4 / 5
Progressive Disclosure	The file has clear section headers but exceeds 50 lines with all content inlined and no bundle files present; content such as the 20-item data model overview and the full flags table arguably belong in separate reference files, matching the 'some structure but content that should be separate is inline' anchor.	3 / 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 clearly identifies a specific platform (Redox) and provides both a 'what' and an explicit 'Use when' trigger, which is solid. Its main weakness is generic action vocabulary and a lack of synonym/variation coverage in the trigger terms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Redox actions, e.g. 'Query patients, visits, and claims; send orders; sync clinical summaries'.

Expand the 'Use when' clause with natural trigger variations users would say, e.g. 'Use when the user wants to query Redox patient data, send orders or results, or automate Redox workflows'.

Add domain synonyms (EHR, FHIR, clinical data) to broaden trigger-term coverage and reduce overlap ambiguity.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Redox domain and a few actions, but the actions are generic rather than comprehensive or concrete, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It states a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Redox data'), though the 'when' could be more specific with concrete trigger phrases, matching the score-4 anchor.	4 / 5
Trigger Term Quality	'Redox data, records, workflows' provides some relevant natural keywords, but it lacks common variations or synonyms (e.g., EHR, FHIR, patient data, claims), matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Redox integration' and 'interact with Redox data' target a specific named platform with distinct triggers and minimal conflict risk, but the generic 'manage data, records, and automate workflows' wording creates minor overlap with other data skills, fitting just below the score-5 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/redox/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.