Name: simvoly
Rating: 68.8 (1 reviews)
Author: membranedev

simvoly

Simvoly integration. Manage Websites, Funnels, Stores, Memberships, Bookings, Forms and more. Use when the user wants to interact with Simvoly data.

Quality

83%

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

Quality

Content

88%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 tight, executable integration guide with concrete commands, a well-sequenced connection workflow, and explicit state-based validation and feedback loops. The only real slack is a little introductory background padding and minor redundancy in the actions section.

Suggestions

Trim the opening background paragraph ("Simvoly is a website builder platform...") and the auth-plumbing aside; Claude does not need the platform explained.

De-duplicate the "Popular actions" section, which restates the `action list --intent=QUERY` command already shown under "Searching for actions".

Add a one-line verification hint after `action run` (e.g., check the `output` field for errors / expected fields) to strengthen the run step's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable commands, but the opening "Simvoly is a website builder platform..." paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" are minor over-explanation Claude does not need; efficient overall with a little trimmable padding, matching the 4 anchor.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end (npm install, membrane login, connection ensure, action list/run with --input, request proxy with a full flag table), matching the fully-executable anchor; placeholders like CONNECTION_ID and QUERY are explicitly parameterized rather than pseudocode.	5 / 5
Workflow Clarity	The connect flow has an explicit sequence with validation checkpoints (poll --wait until state leaves BUILDING) and feedback loops (re-poll after the user completes a client action), plus error-state handling (CONFIGURATION_ERROR / SETUP_FAILED -> check the error field), matching the explicit-validation anchor.	5 / 5
Progressive Disclosure	The single SKILL.md is well-organized with a clear section hierarchy and no monolithic wall of reference material, matching the good-structure anchor; not a 5 because there are no one-level-deep references to split out (fine for scope) and the "Popular actions" section repeats the earlier search command, a minor redundancy.	4 / 5
	Total	18 / 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 cleanly states what the skill does and when to use it, with good natural trigger terms tied to a distinct platform niche. Its main weakness is the generic verb "Manage" and the broad "interact with Simvoly data" trigger, which keep specificity and completeness just below the top anchor.

Suggestions

Replace the single verb "Manage" with a few concrete verbs (e.g., "Create, edit, and query Websites, Funnels, Stores...") to lift specificity toward comprehensive coverage.

Make the "when" trigger more concrete with the phrases users actually say, e.g. "Use when the user wants to build or edit a Simvoly website, funnel, store, or membership."

Add common synonyms or surface terms users might say (e.g. "Simvoly pages, popups, A/B tests, form submissions") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Websites, Funnels, Stores, Memberships, Bookings, Forms and more" names several concrete entity types, matching the anchor that lists several specific actions with minor gaps; not a 5 because the single verb "Manage" plus "and more" leaves the action coverage non-comprehensive.	4 / 5
Completeness	Both "what" ("Manage Websites, Funnels...") and "when" ("Use when the user wants to interact with Simvoly data") are present, matching the anchor with both parts where the trigger could be more explicit; not a 5 because the "when" clause is broad rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural domain terms (Websites, Funnels, Stores, Memberships, Bookings, Forms) give good keyword coverage, matching the "good coverage, a few natural terms missing" anchor; not a 5 because synonyms and file extensions are absent and "interact with Simvoly data" is generic.	4 / 5
Distinctiveness Conflict Risk	"Simvoly integration" scoped to a specific named platform with platform-specific entity triggers gives a clear niche with minimal conflict risk, matching the clear-niche anchor; not a 4 because the brand name makes overlap with other skills unlikely.	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/simvoly/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.