Name: snapshot
Rating: 52 (1 reviews)
Author: membranedev

snapshot

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

Quality

58%

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/snapshot/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 a well-structured, actionable CLI integration guide with concrete commands and a clear connection workflow including validation checkpoints. Its main weakness is conciseness, due to an unnecessary marketing-style introduction and some explanatory padding.

Suggestions

Trim the introductory paragraph to a one-line tool summary; drop the audience/marketing language ("used by software developers, QA testers... streamline communication").

Fix the dangling "skip to Step 2" reference and label steps consistently (e.g., add a "Step 1a" heading before "#### 1b. Wait for the connection to be ready").

Add one short end-to-end worked example (connect -> search -> run) with concrete values to lift actionability from concrete-but-fragmented to copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary prose such as the marketing-style intro ("used by software developers, QA testers, and customer support teams... streamline communication") and explanatory asides about Membrane, matching the score-3 anchor; it does not reach score 4 because the intro padding could be trimmed without losing actionability.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with clearly marked placeholders, matching the score-4 anchor; it stops short of score 5 because no single end-to-end worked example ties the pieces together with concrete IDs.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-then-repoll feedback loop, matching the score-4 anchor; it is below score 5 because of minor gaps such as the dangling "skip to Step 2" reference and an unlabeled step before "#### 1b".	4 / 5
Progressive Disclosure	The content is well-organized into clearly headed sections (install, auth, connect, search, run, proxy, best practices) with no bundle files needed and content appropriately placed inline, matching the score-4 anchor; it does not reach score 5 due to minor organization gaps like the inconsistent step labeling.	4 / 5
	Total	15 / 20 Passed

Description

48%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 includes an explicit trigger clause and a distinct app name, but its capability statement is generic fluff ("manage data, records, and automate workflows") that does not describe what SnapShot concretely does. Specificity and completeness are the weakest dimensions.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete SnapShot actions, e.g. "Capture screenshots, annotate screen recordings, and retrieve albums and photos."

Expand the trigger phrase to natural terms users would say, e.g. "Use when the user wants to capture screenshots, record their screen, or retrieve SnapShot photos and albums."

Make the "what" explicitly reflect SnapShot's capabilities rather than generic data-management language so it answers both what and when concretely.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the SnapShot domain but the actions are minimal and generic, matching the score-2 anchor ("Names the domain but actions are minimal or generic"); it does not reach score 3 because no concrete SnapShot-specific actions (capture, annotate, retrieve photos) are listed.	2 / 5
Completeness	It has a clear "when" ("Use when the user wants to interact with SnapShot data") but the "what" is vague ("Manage data, records, and automate workflows"), falling between the score-3 and score-4 anchors; the vague "what" keeps it from score 4 even though the "when" clause is explicit.	3 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with SnapShot data" includes the recognizable keyword "SnapShot" plus "data", but coverage is thin and misses common variations (screenshots, recordings, albums, photos), matching the score-3 anchor; it is above score 2 because a natural trigger phrase is present rather than only generic jargon.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a named app ("SnapShot integration", "interact with SnapShot data") gives it a distinct niche with only minor overlap risk against other integration skills, matching the score-4 anchor; it is below score 5 because the generic "manage data, records, workflows" phrasing could still overlap with broad data-management skills.	4 / 5
	Total	12 / 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/snapshot/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.