Name: very-good-security
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

very-good-security

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

Quality

64%

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/very-good-security/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 highly actionable with a clear state-machine workflow for connection setup, but it carries some unnecessary background explanation and minor redundancy that slightly blunt conciseness.

Suggestions

Trim the opening "Very Good Security helps companies..." paragraph and the bare entity list, or move them to a referenced overview, since Claude already knows this context.

Collapse the "Popular actions" section into the "Searching for actions" section to remove the repeated command and reduce redundancy.

Add a short filled example of `membrane action run` with a realistic action ID and a sample output so the run workflow is end-to-end concrete.

Dimension	Reasoning	Score
Conciseness	The bulk is tight CLI commands, but the opening business-purpose paragraph and flat entity list explain background Claude already knows, and the "Popular actions" section repeats the earlier search command.	3 / 5
Actionability	Provides concrete copy-paste commands for install, auth, connection, action search/run, and proxying with a flags table; minor gaps include no filled action-run example with a real action ID and output.	4 / 5
Workflow Clarity	Clear install→login→ensure→poll sequence with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, though it lacks an explicit verify step after running actions.	4 / 5
Progressive Disclosure	Single well-organized file with clear section headers and a signaled external docs link; no bundle references exist, and the "Popular actions" section is slightly redundant.	4 / 5
	Total	15 / 20 Passed

Description

61%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 answers both what and when and is clearly tied to a distinct product, but its action verbs are generic and it misses the "VGS" abbreviation and domain synonyms that users would naturally say.

Suggestions

Replace generic verbs with concrete VGS actions, e.g. "Tokenize and vault sensitive data, manage records, and automate workflows."

Add the "VGS" abbreviation and synonyms (tokenization, vault) so the trigger matches how users actually refer to the product.

Make the "Use when" clause more concrete, e.g. "Use when the user wants to tokenize data, manage VGS vault records, or automate VGS workflows."

Dimension	Reasoning	Score
Specificity	Names the VGS domain but the actions ("Manage data, records, and automate workflows") are generic verbs rather than concrete VGS operations like tokenizing or vaulting records.	2 / 5
Completeness	Both "what" (manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Very Good Security data") are present, though the trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	Uses the full brand name "Very Good Security" but omits the common abbreviation "VGS" and natural synonyms such as tokenization or vault.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named product with a brand-based trigger, giving a clear niche with minimal overlap risk against other skills.	5 / 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/very-good-security/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.