Name: splynx
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

splynx

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

Quality

66%

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

Quality

Content

67%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 is a well-structured, highly actionable guide to driving Splynx through the Membrane CLI, with a clear connection workflow and state-feedback loops. It is slightly held back by minor redundancy and over-explanation that could be trimmed for token efficiency.

Suggestions

Trim the introductory 'Splynx is an ISP management system...' paragraph or fold it into one line, since the description already covers it.

Consolidate the 'membrane action list' example so it appears once instead of repeated across 'Searching for actions' and 'Popular actions'.

Standardize on one invocation form ('membrane' vs 'npx @membranehq/cli@latest') to avoid confusing the agent about which to run.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and command-focused, but the introductory paragraph explaining what Splynx is and the repeated 'membrane action list' command across 'Searching for actions' and 'Popular actions' could be tightened.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection, action search/run, and proxying with a full flags table; minor gap is the inconsistent mix of 'membrane' vs 'npx @membranehq/cli@latest' invocations.	4 / 5
Workflow Clarity	Clear install→authenticate→connect→search→run sequence with explicit connection-state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/ERROR) and a poll-after-action feedback loop; minor validation gaps around action-result handling.	4 / 5
Progressive Disclosure	A single self-contained file with well-organized section headers and no need for external references; the detailed clientAction sub-states and proxy flag reference could optionally be split out, but the structure is good.	4 / 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 what the skill does and when to use it, anchored to a distinct named product. Its main weakness is generic action verbs and limited trigger-term variation, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Splynx operations such as 'Create and update customers, manage services, invoices, payments, and routers'.

Expand the trigger clause with natural variations: 'Use when the user wants to manage Splynx customers, billing, invoices, payments, routers, or services.'

Dimension	Reasoning	Score
Specificity	Names the Splynx domain and 2-3 actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; not a level-4 list of specific operations.	3 / 5
Completeness	Has a clear 'what' (Splynx integration, manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Splynx data'), though the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	'Splynx' is a natural keyword a user would say, but the only trigger phrasing is 'interact with Splynx data' — missing common variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	'Splynx' is a specific named ISP-management product, giving it a clear niche with distinct triggers and minimal conflict risk with 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/splynx/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.