Name: snyk
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

snyk

Snyk integration. Manage Projects, Organizations. Use when the user wants to interact with Snyk data.

Quality

71%

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

Quality

Content

76%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 copy-paste CLI commands and a clear connection-state feedback loop. Its weaknesses are the undefined "Step 2" cross-reference and the absence of validation guidance for destructive proxy requests.

Suggestions

Define the referenced "Step 2" (or reword the "skip to Step 2" links) so the connection-to-action handoff is unambiguous.

Add a validation checkpoint before destructive proxy requests (e.g. confirm method/path, dry-run GET first, or check the response status before proceeding).

Trim the marketing framing ("rather than auth plumbing", "burn less tokens") to keep the body lean.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and a reference table with little padding; minor over-explanation ("Snyk is a developer security platform..." intro and "rather than auth plumbing" framing) could be trimmed, matching the efficient-with-minor-over-explanation anchor.	4 / 5
Actionability	Copy-paste-ready commands (npm install, membrane login, connection ensure, action run, request) with explicit flags and a proxy-options table cover the common cases fully, matching the fully-executable anchor.	5 / 5
Workflow Clarity	A sequence with state-polling feedback (READY/BUILDING/CLIENT_ACTION_REQUIRED) exists, but proxy requests support destructive verbs (POST/PUT/DELETE) with no validation guidance, and "skip to Step 2" references an undefined Step 2, so the destructive-operation cap and implicit-checkpoint gaps hold this at 3.	3 / 5
Progressive Disclosure	No bundle files exist and content is organized into clear headed sections with no nested references; at 155 lines some proxy/action detail could arguably live in a separate file, but the single-file structure is well-signaled and navigable, fitting the good-structure anchor.	4 / 5
	Total	16 / 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 cleanly answers both what it does and when to use it, anchored to a distinct brand. Its main weakness is generic verb choice ("Manage") and missing common Snyk trigger terms like vulnerabilities or scanning.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List and inspect Snyk Projects, Organizations, vulnerabilities, and reports."

Add natural trigger terms users actually say, such as "Snyk vulnerabilities", "Snyk scan results", or "security findings".

Expand the "Use when" clause to enumerate concrete triggers like reviewing dependencies or checking vulnerability reports.

Dimension	Reasoning	Score
Specificity	Quotes "Manage Projects, Organizations" name the Snyk domain and two concrete entities, but the single verb "Manage" is generic rather than enumerating concrete actions, matching the anchor that lists domain plus 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Both "what" ("Manage Projects, Organizations") and "when" ("Use when the user wants to interact with Snyk data") are present and explicit, but the "what" is somewhat generic so it stops short of the concrete-trigger-phrase completeness of a 5.	4 / 5
Trigger Term Quality	Terms "Snyk", "Projects", "Organizations", and the trigger clause "interact with Snyk data" are relevant, but common natural variations users say (vulnerabilities, scan, security findings) are absent, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Snyk integration" tied to a distinct brand with a Snyk-specific "Use when" trigger carves a clear niche with minimal overlap risk against other skills.	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/snyk/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.