Name: sugarsync
Rating: 59.2 (1 reviews)
Author: membranedev

sugarsync

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

Quality

68%

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

Quality

Content

75%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-ready Membrane commands and a clear connection workflow backed by a state machine. The main weaknesses are an unnecessary introductory explanation of what SugarSync is and some fluff in the Best practices section.

Suggestions

Cut the opening paragraph explaining what SugarSync is ("a cloud storage and file synchronization service, similar to Dropbox or Google Drive") — Claude already knows this.

Tighten the Best practices section by removing rhetorical padding like "This will burn less tokens and make communication more secure".

Label the section referenced as "Step 2" (or remove the dangling "Skip to Step 2" references) so the workflow steps resolve cleanly.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the opening paragraph explains what SugarSync is ("a cloud storage and file synchronization service, similar to Dropbox...") and the "Best practices" section contains fluff ("This will burn less tokens and make communication more secure"), fitting "mostly efficient but includes some unnecessary explanation".	3 / 5
Actionability	It provides copy-paste-ready commands for the common cases — install (npm install -g @membranehq/cli), login, connection ensure, action list/run with --input JSON, and membrane request with a concrete flags table — fully executable and covering the typical workflow.	5 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear and includes a connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a polling feedback loop, but "Step 2" is referenced without a matching labeled section, a minor checkpoint/labeling gap.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Overview, Working with SugarSync, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references and no bundle files, but some dense inline material (the clientAction sub-bullets, the proxy flags table) could arguably live in a separate reference.	4 / 5
	Total	16 / 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 correctly includes both a capability statement and an explicit "Use when" trigger, and the brand name keeps it distinctive. Its main weakness is generic, non-concrete action language and a lack of natural user trigger terms like files, sync, backup, or share.

Suggestions

Replace generic actions with concrete SugarSync capabilities, e.g. "Back up and sync files, manage folders, and share links via SugarSync".

Add natural trigger terms users actually say, such as "Use when the user wants to sync, back up, share, or access SugarSync files and folders".

Avoid the templated "Manage data, records, and automate workflows" phrasing that could match many integration skills and dilute distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the SugarSync domain and lists a few actions ("Manage data, records, and automate workflows"), but those actions are generic abstractions rather than concrete file/sync/backup operations, fitting the "names domain and 1-2 concrete actions but not comprehensive" anchor.	3 / 5
Completeness	Both the "what" ("SugarSync integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with SugarSync data") are present, but the trigger phrase is generic rather than concrete, so it sits at "has both what and when; when could be more explicit" rather than a 5.	4 / 5
Trigger Term Quality	"SugarSync" is a strong brand trigger and "interact with SugarSync data" gives one relevant phrase, but common natural terms users would actually say (files, sync, backup, share, cloud storage) are missing, matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The SugarSync brand name gives it a clear niche with minimal conflict risk, but the templated "Manage data, records, and automate workflows" phrasing could overlap with sibling Membrane integration skills, placing it at "mostly distinct; minor overlap risk" rather than a 5.	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/sugarsync/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.