Name: worksnaps
Rating: 56.8 (1 reviews)
Author: membranedev

worksnaps

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/worksnaps/SKILL.md

Quality

Content

68%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 content is highly actionable with copy-paste CLI commands and a clear connection state machine, but it is capped on workflow clarity because the action/proxy operations that can perform destructive writes lack validation or verification steps. Minor verbosity and a couple of redundant sections keep conciseness and progressive disclosure just below the top band.

Suggestions

Add a verification/validation step after running actions or proxy requests (e.g., re-query to confirm the change took effect, or a dry-run/check call before destructive POST/PUT/DELETE), which would lift the workflow_clarity cap.

Trim promotional and explanatory padding such as 'so you can focus on the integration logic rather than auth plumbing' and fix the 'burn less tokens' wording to concise best-practice guidance.

Fix inconsistent step numbering (resolve '1b' with no '1a' and the dangling 'Step 2' reference) and consolidate the overlapping 'Searching for actions' and 'Popular actions' sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and flag tables, but includes unnecessary explanation and mild padding such as 'so you can focus on the integration logic rather than auth plumbing' and the promotional 'This will burn less tokens and make communication more secure', matching score-3 'Mostly efficient but includes some unnecessary explanation'; not a 4 because several sentences could be trimmed without losing clarity.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases throughout (e.g. 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.worksnaps.com/www/index.shtml" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input ...'), matching score-5 'Fully executable; copy-paste ready code or commands'; not a 4 because the examples are complete and concrete rather than having minor gaps.	5 / 5
Workflow Clarity	The connection sequence is well-structured with state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but running actions and proxy requests support destructive HTTP methods (POST/PUT/PATCH/DELETE) with no validation/verification step, triggering the rubric cap that workflow_clarity cannot exceed 3; not a 4 because the destructive/batch cap applies and the step numbering is inconsistent ('1b' with no '1a', references to 'Step 2').	3 / 5
Progressive Disclosure	The skill is a single self-contained file (no references/scripts/assets bundles exist) organized into clearly labeled sections (Overview, Install, Authentication, Connecting, Searching for actions, Popular actions, Best practices) with a useful flags table, matching score-4 'Good structure; most content appropriately placed; minor organization gaps'; not a 5 because 'Popular actions' overlaps with 'Searching for actions' and numbering gaps exist, and not a 3 because organization is genuinely clear rather than merely present.	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 is well-formed with both a 'what' and an explicit 'Use when' trigger, and its targeting of a single named app makes it highly distinct. Its main weakness is generic capability verbs ('Manage data, records') rather than concrete Worksnaps-specific actions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Worksnaps-specific actions such as 'track time entries, manage projects and users, pull time reports'.

Broaden the trigger phrase beyond 'interact with Worksnaps data' to include natural terms like time tracking, timesheets, or work hours.

Tighten the 'when' clause to cite specific trigger scenarios (e.g., 'when the user wants to pull time-tracking reports or manage Worksnaps projects').

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Worksnaps domain but the actions are minimal and generic ('manage data', 'records'), matching the score-2 anchor 'Names the domain but actions are minimal or generic'; not a 3 because no action is concrete enough to resemble 'extracts content'.	2 / 5
Completeness	Both 'what' ('Worksnaps integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Worksnaps data') are present, matching score-4 'Has both what and when; when could be more explicit or specific'; not a 5 because the trigger phrase lacks concrete variations, and not a 3 because an explicit 'Use when' clause is present.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Worksnaps data' supplies the natural keyword 'Worksnaps' but offers no synonyms or variations, fitting the score-3 anchor 'Some relevant keywords but missing common variations or synonyms'; not a 4 because coverage is limited to the single app name with no broader natural terms.	3 / 5
Distinctiveness Conflict Risk	'Worksnaps integration' targets a single named application, giving it a clear niche with distinct triggers and minimal conflict risk, matching the score-5 anchor; not a 4 because no other common skill would naturally trigger on the Worksnaps name.	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/worksnaps/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.