Name: elorus
Rating: 49.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

elorus

Elorus integration. Manage Organizations. Use when the user wants to interact with Elorus data.

Quality

53%

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

Quality

Content

50%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 gives executable, well-structured CLI guidance for connecting to Elorus and discovering/running actions. Its main drawbacks are a padded, partly-fabricated entity list that wastes tokens, missing validation before destructive action runs, and no progressive disclosure of the large reference material into bundle files.

Suggestions

Trim or remove the 75-item entity bullet list, keeping only entities the Elorus API actually exposes; the rest is padding that competes for context.

Add a verify-before-run checkpoint for destructive actions (e.g. 'Confirm the record ID and run membrane action get before delete-* actions').

Move the entity catalog and Popular actions table into a references/ file (e.g. ACTIONS.md) and link to it from a concise overview, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~75-item entity bullet list (lines 23-95) is a padded wall of names, many generic accounting concepts ('Trial Balance', 'Journal Entry', 'Audit Trail') rather than real Elorus resources, plus filler like 'Use action names and parameters as needed.' — a noticeably padded section that doesn't earn its tokens.	2 / 5
Actionability	Commands are concrete and copy-paste ready (npm install, membrane login, connection ensure, action list/run, request) and the Popular actions table gives real action keys, with only minor gaps such as unsubstituted CONNECTION_ID/actionId placeholders.	4 / 5
Workflow Clarity	The connection workflow is well sequenced with state-polling checkpoints and a CLIENT_ACTION_REQUIRED feedback loop, but the action-running section covers destructive operations (delete invoice/contact) with no validation or verify-before-run checkpoint, which caps this per the destructive-operations rule.	3 / 5
Progressive Disclosure	Sections are clearly headed, but the skill is a large (>50 lines) monolithic single file with no bundle references, and the entity catalog plus action table are inline reference material that would be better split into a separate file.	3 / 5
	Total	12 / 20 Passed

Description

57%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 correctly pairs a 'what' and a 'Use when' trigger and is anchored by the distinct product name 'Elorus'. Its weaknesses are minimal action specificity and thin trigger-term coverage that omits the invoicing/expense/time-tracking vocabulary users would actually invoke.

Suggestions

Replace the generic 'Manage Organizations' with 2-3 concrete capabilities, e.g. 'Create and track invoices, expenses, and billable time'.

Expand the trigger clause to include natural terms users say, e.g. 'Use when the user mentions Elorus, invoices, estimates, expenses, or time tracking'.

Note that 'Organizations' is not among the entities listed in the body — align the description's named capability with the skill's actual surface area.

Dimension	Reasoning	Score
Specificity	It names the domain ('Elorus integration') but the only named action is the generic 'Manage Organizations', which is minimal and uses a non-specific verb rather than listing concrete capabilities like invoicing, expenses, or time tracking.	2 / 5
Completeness	Both 'what' ('Elorus integration. Manage Organizations.') and 'when' ('Use when the user wants to interact with Elorus data.') are present, though the trigger clause is generic and could be more specific.	4 / 5
Trigger Term Quality	'Elorus' is a natural keyword users would say, but the description misses common variations and synonyms (invoices, expenses, time tracking, projects) that the body later reveals as core capabilities.	3 / 5
Distinctiveness Conflict Risk	The named product 'Elorus' gives it a clear, distinct niche with low conflict risk against unrelated skills, but the generic 'interact with Elorus data' phrasing leaves minor overlap risk with adjacent accounting/invoicing skills.	4 / 5
	Total	13 / 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/elorus/SKILL.md
Commit: f484c82

Reviewed: 4 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.