Name: vision6
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

vision6

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

Quality

61%

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

Quality

Content

61%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, command-heavy guide that is highly actionable for the Membrane CLI flow, with a genuinely useful connection state machine. Its main weaknesses are redundant/explanatory prose, an implicit end-to-end sequence, and the absence of validation before destructive email-marketing actions.

Suggestions

Add an explicit validation/confirmation step before destructive or batch actions (e.g. confirm before sending a campaign or bulk-deleting contacts), which would lift the workflow_clarity cap.

Remove the redundant `action list` command repeat under 'Popular actions' and trim the 'what is Vision6' intro and 'so you can focus' aside.

Provide one fully-substituted example of running a real Vision6 action (e.g. listing contacts) with concrete parameters instead of only placeholders.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands, but the opening 'what is Vision6' paragraph, the 'so you can focus on the integration logic' aside, and a redundant repeat of the `action list` command under 'Popular actions' are trimmable.	3 / 5
Actionability	Concrete copy-paste commands cover install, login, connection ensure, action list/run (with JSON params), and proxy requests with a full flag table; minor gaps are the unsubstituted placeholders and lack of a real Vision6 action example.	4 / 5
Workflow Clarity	The connection setup has a clear state machine with polling checkpoints, but the overall install→auth→connect→search→run sequence is implicit, and no validation guards destructive/batch email operations, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist, so all content is single-file with clear section headers (Install, Authentication, Connecting, Searching, Proxy, Best practices); organization is good, though the clientAction state detail and proxy flag table are dense inline material.	4 / 5
	Total	14 / 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 correctly uses third person and includes both a 'what' and a 'Use when' trigger, anchored on the distinctive Vision6 name. It is weakened by generic actions that never reveal the email-marketing domain, leaving trigger terms and specificity below their potential.

Suggestions

Replace generic actions with email-marketing-specific ones, e.g. 'Create and send email campaigns, manage contact lists, and automate marketing workflows.'

Add natural trigger terms users would say, such as 'email campaigns', 'marketing automation', 'contacts', or 'lists', beyond just 'Vision6 data'.

Make the 'when' clause more concrete, e.g. 'Use when the user wants to send campaigns or manage contacts in Vision6.'

Dimension	Reasoning	Score
Specificity	Names the domain (Vision6) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and do not surface the platform's email-marketing-specific capabilities like campaigns, lists, or contacts.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Vision6 data'), though the 'when' clause is somewhat generic.	4 / 5
Trigger Term Quality	'Vision6' and 'Vision6 data' are relevant triggers a user would say, but common natural variations (email campaigns, marketing automation, contacts, lists) are missing.	3 / 5
Distinctiveness Conflict Risk	The named platform 'Vision6' provides a clear niche with minimal conflict risk, but the generic surrounding actions ('manage data', 'interact with data') leave minor overlap ambiguity.	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/vision6/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.