Name: idx-broker
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

idx-broker

IDX Broker integration. Manage Leads, Users, Roles. Use when the user wants to interact with IDX Broker data.

Quality

68%

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/idx-broker/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 skill is highly actionable with a well-instrumented connection workflow and copy-paste commands. Its main weakness is token efficiency: a large redundant endpoint catalog is inlined in SKILL.md rather than externalized into a reference file.

Suggestions

Move the endpoint catalog into a separate reference file (e.g. references/endpoints.md) and keep SKILL.md as an overview, since the same data is discoverable via `membrane action list --intent`.

Trim the redundant 'Get X — Retrieves X' endpoint list, which restates each name as its description and overlaps the Popular actions table.

Add brief guidance on interpreting and validating `membrane action run` output (e.g. checking the `output` field and handling error states) to complete the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The Membrane CLI instructions are efficient, but the ~85-line endpoint catalog restates each endpoint's name as its description ('Get Featured Properties — Retrieves a list of featured properties') and overlaps the Popular actions table, which is padded content Claude could instead discover via `membrane action list`.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases end-to-end — install, login (including headless completion), connection ensure/wait, action list, action run with JSON input, and proxy requests — each with the relevant flags.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-and-retry feedback loop; the minor gap is the absence of guidance on validating or handling `action run` results and errors.	4 / 5
Progressive Disclosure	Section headers and a Popular actions table provide some structure, but the full endpoint catalog is inlined in SKILL.md with no bundle/reference files present, so content that belongs in a separate one-level-deep reference is not split out.	3 / 5
	Total	15 / 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 cleanly states both purpose and an explicit trigger, and the named product makes it highly distinct. It is held back by a generic verb ('Manage') and a thin set of natural trigger phrases that under-represent the skill's actual surface area.

Suggestions

Replace the generic verb 'Manage' with specific operations, e.g. 'Create, update, delete, and list Leads, Users, and Roles' to surface concrete capabilities.

Expand the trigger clause with natural phrases users say, such as 'IDX Broker leads', 'property listings', or 'saved searches', instead of only 'interact with IDX Broker data'.

Mention listing/property actions (e.g. featured listings, saved links) so the 'what' reflects the full action set shown in the body.

Dimension	Reasoning	Score
Specificity	Names the domain ('IDX Broker integration') and concrete entities ('Manage Leads, Users, Roles'), but the single generic verb 'Manage' covers many operations and omits the listing/property actions the body actually exposes, so coverage is not comprehensive.	3 / 5
Completeness	Both 'what' ('Manage Leads, Users, Roles') and an explicit 'when' ('Use when the user wants to interact with IDX Broker data') are present; the 'when' is explicit but generic, matching the 'could be more specific' anchor rather than the fully concrete 5.	4 / 5
Trigger Term Quality	'IDX Broker' is a distinctive natural term a user would say, but the trigger clause 'interact with IDX Broker data' misses common variations users actually voice such as 'leads', 'property listings', or 'saved searches'.	3 / 5
Distinctiveness Conflict Risk	'IDX Broker' is a specific named product with entity-specific triggers, giving it a clear niche with minimal overlap risk against other skills.	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/idx-broker/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.