Name: orbisx
Rating: 55.2 (1 reviews)
Author: membranedev

orbisx

OrbisX integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with OrbisX data.

Quality

63%

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

Quality

Content

56%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 delivers highly executable CLI guidance with a well-structured connection-state workflow and feedback loops. Its biggest problems are the padded 100-item entity/verb list wasting tokens and the lack of any progressive disclosure into separate reference files.

Suggestions

Move the long entity/resource list into a separate references file (e.g. ENTITIES.md) and link to it from the overview, keeping only the most common entities inline.

Remove the generic verb list (Create, Read, Update, Delete, Search, List, Print, Share, Merge, ...) since these are universal CRUD/action terms Claude already knows.

Add a fully-worked example that substitutes real values for <actionId> and CONNECTION_ID, and add a verification step for destructive proxy calls (e.g. GET the resource after a POST/PUT/DELETE to confirm).

Dimension	Reasoning	Score
Conciseness	The instructional core (CLI install, auth, connection, actions, proxy) is reasonably efficient, but the ~100-item bullet list of entities and generic verbs (Create, Read, Update, Delete, Print, Share, Merge, ...) is a large padded section of terms Claude already knows, making it noticeably verbose.	2 / 5
Actionability	It provides copy-paste-ready commands (npm install, membrane login, connection ensure, action run, request) with a concrete flags table, but placeholders like <actionId> and CONNECTION_ID are never filled with a fully-worked example, leaving minor gaps.	4 / 5
Workflow Clarity	The connection lifecycle is a clear sequence with feedback loops (polling BUILDING, handling CLIENT_ACTION_REQUIRED, checking error on CONFIGURATION_ERROR), but "skip to Step 2" references an unlabeled step and there is no verification guidance for destructive proxy operations (DELETE/PUT).	4 / 5
Progressive Disclosure	Section headers are present and reasonable, but everything is inlined into one file with no external references, and the large entity list is content that arguably belongs in a separate reference file, so organization is only adequate.	3 / 5
	Total	13 / 20 Passed

Description

70%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, includes an explicit "Use when" clause, and anchors on a distinctive named platform. Its main weakness is the generic verb "Manage" in place of concrete actions and a trigger clause that could name specific user intents.

Suggestions

Replace the generic verb "Manage" with concrete CRUD-style actions (e.g., "Create, update, list, and search Organizations, Pipelines, Users, and Filters").

Make the trigger clause more specific by enumerating intents, e.g. "Use when the user wants to manage OrbisX organizations, pipelines, users, or filters, or query OrbisX data."

Dimension	Reasoning	Score
Specificity	It names the domain and four specific entities ("Manage Organizations, Pipelines, Users, Filters"), but the single generic verb "Manage" is not a concrete action like extract/fill/merge, so it falls below the "several specific actions" anchor at 4.	3 / 5
Completeness	Both "what" (OrbisX integration, manage the four entities) and "when" ("Use when the user wants to interact with OrbisX data") are present and explicit, but the trigger clause is somewhat generic rather than listing concrete trigger phrases, keeping it below 5.	4 / 5
Trigger Term Quality	The entity names (Organizations, Pipelines, Users, Filters) plus "OrbisX" are natural terms a user would say, giving good keyword coverage, though common synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	The named platform "OrbisX" gives it a clear niche with minimal conflict risk, but the generic entity terms (Organizations, Pipelines, Users, Filters) could overlap with other CRM-style skills, so it is not a clean 5.	4 / 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/orbisx/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.