Name: nexudus
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

nexudus

Nexudus integration. Manage Spaces, Members, Products. Use when the user wants to interact with Nexudus data.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nexudus/SKILL.md

Quality

Content

76%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 a clear connection workflow, organized into clean sections. Its main weaknesses are the absence of validation/verification steps before destructive or batch action/proxy operations and minor verbosity in a few prose passages.

Suggestions

Add an explicit validation/verification checkpoint before running mutating or destructive actions and proxy calls (e.g., confirm the target resource id and review the operation before POST/PUT/DELETE), and a verify step afterward.

Trim soft prose such as "so you can focus on the integration logic rather than auth plumbing" and "This will burn less tokens and make communication more secure" to tighten token efficiency.

Consider moving the detailed clientAction state-machine and the proxy flag table into a short reference file so SKILL.md stays a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands and avoids explaining generic concepts Claude already knows; the Nexudus/Membrane specifics are legitimately useful, though a few phrases ("so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens") could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection setup, action search/run, and proxying, with flag tables covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with a polling state machine and error-recovery branches, but running actions and proxying (which can issue destructive POST/PUT/DELETE calls) lack any validation or verification checkpoint before execution, which caps this dimension at 3 per the destructive/batch-operation guideline.	3 / 5
Progressive Disclosure	The single self-contained SKILL.md is well organized into clear sections (Overview, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with easy navigation and no bundle files needed; at ~145 lines some detailed content (the clientAction state machine, the proxy flag table) could be split into references, leaving minor organization gaps rather than a fully split structure.	4 / 5
	Total	16 / 20 Passed

Description

78%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 specific, third-person, and clearly names both capabilities and a use-trigger, with a strong distinct niche around Nexudus. It could be improved by diversifying the verbs beyond "Manage" and making the trigger clause more concrete.

Suggestions

Replace the repeated generic verb "Manage" with distinct concrete actions (e.g., "Create and update Spaces, manage Members and Contracts, list Products") to broaden coverage.

Make the trigger clause more concrete by listing situations users describe (e.g., "Use when the user wants to manage bookings, members, or invoices in Nexudus").

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates several concrete management targets ("Manage Spaces, Members, Products") rather than vague language, though the single verb "Manage" covers only part of the domain (Session, Task, Booking, Contract, Invoice from the body are omitted), leaving minor coverage gaps.	4 / 5
Completeness	It states both what ("Manage Spaces, Members, Products") and when ("Use when the user wants to interact with Nexudus data"), but the "when" clause is generic rather than listing concrete trigger phrases, so it falls just short of a 5.	4 / 5
Trigger Term Quality	The product name "Nexudus" and "Nexudus data" are natural terms a user would say, with "Spaces, Members, Products" adding relevant keywords, but common variations like bookings, contracts, or invoices are missing.	4 / 5
Distinctiveness Conflict Risk	Tied to a named platform ("Nexudus integration", "interact with Nexudus data"), giving it a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	17 / 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/nexudus/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.