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

Blog Docs Log in Get started

vryno

Vryno integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vryno 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/vryno/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 delivers concrete, executable Membrane CLI guidance with a clear connection workflow and validation checkpoints, but is held back by a stray filler line, a redundant section, and minor numbering/organization inconsistencies. Cleaning these up would push it into the top tier.

Suggestions

Remove the leftover placeholder line ("I don't have enough information about that app…") — it is not skill content.

Merge or differentiate the "Searching for actions" and "Popular actions" sections, which repeat the same `action list` command.

Fix step numbering (the text references "Step 2" while the preceding subsection is labeled "1b") so the connection workflow reads as a coherent sequence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI documentation, but contains a leftover filler line ("I don't have enough information about that app…") and a redundant "Popular actions" section that repeats the action-list command. Not 4 because the filler and redundancy are unnecessary padding; not 2 because the bulk is reasonably tight rather than extensively verbose.	3 / 5
Actionability	Provides concrete, executable `membrane` commands with flags and a proxy-options table covering common cases. Not 5 because some placeholders (CONNECTION_ID, QUERY) and the vague line "Use action names and parameters as needed" leave minor gaps; not 3 because the guidance is mostly copy-paste ready rather than pseudocode.	4 / 5
Workflow Clarity	The connection flow has explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a feedback loop (poll again after the user completes the action). Not 5 because the step numbering is inconsistent ("Step 2" referenced but the prior section is labeled "1b") and error recovery is implicit; not 3 because checkpoints and a retry loop are clearly present.	4 / 5
Progressive Disclosure	Single file with well-organized section headers and no nested references; no bundle files are present to mis-link. Not 5 because the thin "Vryno Overview" section and the redundant "Popular actions" section are minor organization gaps; not 3 because structure is clear and content is appropriately placed.	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 names a distinct app and includes both a capability summary and an explicit "Use when" trigger, but the listed actions are generic and the trigger phrase lacks concrete variations. It is solid but could be sharpened with more specific verbs and trigger terms.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Vryno actions (e.g., "create and update contacts, log meeting notes, search records").

Expand the "Use when" clause with concrete trigger phrases users would say (e.g., "when the user mentions Vryno contacts, meetings, or meeting notes").

Add synonyms or file/entity terms to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Vryno) and lists three actions ("Manage data, records, and automate workflows"), but the actions are generic ("manage") rather than concrete. Not 4 because the actions lack the specificity of anchors like "extracts text, fills forms, converts pages"; not 2 because multiple actions are named beyond the minimal level.	3 / 5
Completeness	Provides both a "what" ("Vryno integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Vryno data."). Not 5 because the "when" clause is generic rather than concrete trigger phrases; not 3 because both what and when are clearly present.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Vryno", "data", "records", "workflows", "interact with Vryno data") but misses natural variations and synonyms a user might say. Not 4 because coverage is not comprehensive enough for the higher anchor; not 2 because more than one or two generic keywords are present.	3 / 5
Distinctiveness Conflict Risk	"Vryno" is a distinct named application, giving it a clear niche with minimal conflict risk against other skills. Not 4 because a unique named app has even lower overlap risk than the "mostly distinct" anchor implies.	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/vryno/SKILL.md
Commit: f484c82

Reviewed: 3 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.