Name: soveren
Rating: 52.8 (1 reviews)
Author: membranedev

soveren

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

Quality

59%

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/soveren/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 CLI usage guidance is concrete and well-sequenced with good state-handling checkpoints, making it genuinely actionable. The skill is dragged down by a massive inlined list of generic entity/buzzword terms that violate conciseness and would be better moved to a reference file.

Suggestions

Remove or relocate the ~200-item entity list (Company, User, ... Metaverse); most are generic terms Claude already knows and are not actionable Soveren-specific guidance.

Define the referenced "Step 2" explicitly (e.g. label the Searching/Running actions section) so the cross-references resolve.

Add an explicit verification step after running actions or proxy requests (e.g. check the `output`/error field and retry on non-2xx) to close the workflow validation gap.

Dimension	Reasoning	Score
Conciseness	The body opens with a ~200-item bullet list of mostly generic terms ("Metaverse", "Cryptocurrency", "BIOS", "Driver", "Firmware") that are not Soveren-specific and assume Claude lacks basic vocabulary, which is noticeable padding despite the reasonably lean CLI sections.	2 / 5
Actionability	It provides concrete, executable commands (npm install, membrane login, membrane connection ensure, membrane action run, membrane request) plus a flags table, giving mostly copy-paste-ready guidance with only minor gaps such as unresolved CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and polling, though it references an undefined "Step 2" and lacks explicit verification for action execution.	4 / 5
Progressive Disclosure	Sections are headed and organized, but the skill is ~360 lines with no bundle files or external references, and the large inlined entity list is content that would be better split into a separate reference file, fitting the anchor for some structure with inline content that should be separate.	3 / 5
	Total	13 / 20 Passed

Description

62%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 functional: it names the product, lists a few actions, and includes an explicit Use-when trigger. Its main weakness is generic action language ("manage data, records") rather than concrete capabilities, leaving the trigger and specificity moderately strong but not comprehensive.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Soveren-specific capabilities, e.g. "Search and update Soveren records, trigger automations, and pull reports".

Expand the trigger clause with natural user phrases and synonyms, e.g. "Use when the user wants to query, create, or update Soveren records or run Soveren automations".

Add file-format or entity hints (e.g. contacts, cases, deals) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain (Soveren) and lists a few actions — "Manage data, records, and automate workflows" — but those actions are generic rather than concrete, matching the anchor that names the domain with 1-2 actions that are not comprehensive.	3 / 5
Completeness	It answers both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Soveren data") with an explicit Use-when clause, though the when could be more specific — matching the anchor for both present with the when only moderately explicit.	4 / 5
Trigger Term Quality	It includes relevant keywords ("Soveren", "data", "records", "workflows") and an explicit trigger phrase, but lacks common variations or synonyms a user would naturally say, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Soveren gives it a clear niche with minimal conflict risk, but the accompanying actions are generic enough to allow minor overlap with other data-management skills, fitting the mostly-distinct anchor.	4 / 5
	Total	14 / 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/soveren/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.