Name: neonomics
Rating: 53.6 (1 reviews)
Author: membranedev

neonomics

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

Quality

60%

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

Quality

Content

82%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 a strong, executable reference for the Membrane CLI integration, with copy-paste commands, a flag table, and a clear connection-state workflow. Its main weaknesses are mild verbosity in a few explanatory passages and the absence of explicit verification steps for action execution and proxy requests.

Suggestions

Trim the opening product-description paragraph and rationale-style prose to lean on Claude's existing knowledge of what an API integration is.

Add an explicit verification step after 'action run' and proxy requests (e.g. inspect the 'output' field / status code and handle errors before proceeding) to strengthen workflow checkpoints.

Consider moving the full CLI flag reference table into a short separate reference file if the skill grows, keeping SKILL.md as an overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient, leading with executable commands and tables of flags, but includes a couple of mild over-explanations (e.g. the opening product description paragraph and the 'Discover before you build' rationale) that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready CLI commands with concrete flags for install, login, connection ensure/get, action list/run, and proxy requests, plus a complete flag-options table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based decision branches (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling loop, but operations like 'action run' and proxy requests lack explicit validation or verification checkpoints, which is a minor gap rather than a destructive-operation cap.	4 / 5
Progressive Disclosure	The SKILL.md is well-organized into overview, install, auth, connection, actions, proxy, and best-practices sections, but it inlines the full CLI flag reference and all guidance with no separate reference files or one-level-deep pointers, which is appropriate for this size yet leaves minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

37%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 includes a 'Use when' trigger and names the target product, but its capabilities are generic ('manage data, records, and automate workflows') rather than reflecting Neonomics' open-banking domain (payments, accounts, transactions). Tightening the action list and adding natural banking/payment trigger terms would materially improve it.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Neonomics-specific actions such as 'Access bank account data, initiate payments, and retrieve transaction history'.

Add natural user-facing trigger terms like 'banking', 'payments', 'accounts', or 'open banking' so the skill matches how users actually phrase the need.

Keep the 'Use when' clause but tie it to specific scenarios, e.g. 'Use when the user needs to connect to bank accounts, initiate payments, or fetch financial data via Neonomics.'

Dimension	Reasoning	Score
Specificity	The description names the domain but actions are generic ('Manage data, records, and automate workflows') with no concrete Neonomics-specific capabilities like payments, account access, or transaction retrieval.	2 / 5
Completeness	A 'what' is present ('Manage data, records, and automate workflows') and a 'when' clause exists ('Use when the user wants to interact with Neonomics data'), but the 'what' is generic and the 'when' is weakly tied to a single vague trigger, so it falls below a clear both-what-and-when anchor.	3 / 5
Trigger Term Quality	The only natural trigger phrase is 'interact with Neonomics data', which restates the product name; it lacks common-sense variations or synonyms a user would actually say, such as 'banking', 'payments', or 'accounts'.	2 / 5
Distinctiveness Conflict Risk	The brand name 'Neonomics' provides a niche anchor, but 'manage data, records, and automate workflows' is broad and could overlap with generic data-management or automation skills.	3 / 5
	Total	10 / 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/neonomics/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.