Name: snapdocs
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

snapdocs

Snapdocs integration. Manage Organizations, Users, Roles. Use when the user wants to interact with Snapdocs data.

Quality

67%

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

Quality

Content

72%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 executable commands and a well-sequenced connection workflow, but lacks verification feedback loops for destructive proxy operations and keeps all reference material inline rather than splitting it into separate files. It is strong on doing, weaker on progressive disclosure and validation.

Suggestions

Add an explicit validate/verify step after destructive proxy calls and a retry-on-error loop, e.g. check the response status and re-poll the connection state before proceeding.

Move the proxy flags table and the clientAction object reference into a separate REFERENCE.md (or references/) file and link to it from SKILL.md to improve progressive disclosure.

Trim incidental commentary ('This is the fastest way to get a connection', 'You should always search...') to tighten the token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a tight flag table, with only minor trimmable commentary like 'This is the fastest way to get a connection', fitting the efficient-with-minor-over-explanation anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action run with JSON input, proxy requests) plus a concrete flags table, covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequenced state machine with polling checkpoints, but action execution and the proxy (which supports POST/PUT/DELETE) provide no validation or verify-fix-retry feedback loop, so it sits at the validation-gaps anchor.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is reasonably sectioned, but reference-style content (the proxy flags table, the full clientAction object breakdown) is inlined with zero external references signaled, matching the some-structure-but-could-be-better-organized anchor.	3 / 5
	Total	15 / 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 cleanly covers what and when with a named niche product, but relies on the generic verb 'Manage' and lacks varied natural trigger phrases. It is solidly above average yet short of the comprehensive, concrete-action benchmark.

Suggestions

Replace the generic verb 'Manage' with specific actions per entity (e.g., 'Create and invite Users, assign Roles, list and update Organizations').

Broaden the trigger clause with natural user phrasing and synonyms (e.g., 'Use when the user wants to manage Snapdocs users, roles, or organization membership').

Add file extensions or entity-specific keywords (e.g., 'closings', 'orders') to widen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and three concrete targets ('Manage Organizations, Users, Roles') but the single generic verb 'Manage' gives no detail on the actions performed, so it sits at the not-comprehensive anchor rather than several-specific-actions.	3 / 5
Completeness	Both 'what' ('Manage Organizations, Users, Roles') and 'when' ('Use when the user wants to interact with Snapdocs data') are present and explicit, but the trigger clause is fairly generic so it lands just below the fully-concrete-anchor at 5.	4 / 5
Trigger Term Quality	It includes the product name 'Snapdocs' and entity terms ('Organizations, Users, Roles') plus the phrase 'interact with Snapdocs data', but misses common natural variations and synonyms a user would say, matching the some-relevant-keywords anchor.	3 / 5
Distinctiveness Conflict Risk	'Snapdocs integration' names a clear niche product with a distinct trigger, leaving only minor overlap risk with generic data-interaction skills, which matches the mostly-distinct anchor.	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/snapdocs/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.