Name: syncro
Rating: 62.4 (1 reviews)
Author: membranedev

syncro

Syncro integration. Manage Organizations, Tickets, Leads, Emails, Users, Roles. Use when the user wants to interact with Syncro data.

Quality

74%

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/syncro/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 comprehensive executable commands and a well-structured connection state machine. It loses points mainly on a padded entity enumeration and minor structural inconsistencies in step labeling.

Suggestions

Trim or move the 45-item "Syncro Overview" entity list into a concise note or a separate reference file, since the flat noun list adds tokens without actionable guidance.

Fix the broken step navigation: label the section referenced as "Step 2" and rename "1b" to a consistent step number so the flow is unambiguous.

Add a brief verification step after running actions or proxy requests (e.g., check the `output` field / HTTP status) to strengthen the workflow's validation loop.

Dimension	Reasoning	Score
Conciseness	The command and workflow sections are efficient and token-conscious, but the ~45-item flat "Syncro Overview" entity list and the introductory platform-description paragraph add padding that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready commands across install, login (including headless), connection ensure/poll, action list/run with JSON params, and proxy requests with a full flag table — covering the common cases.	5 / 5
Workflow Clarity	The connection flow is a clear state machine with checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/ERROR) and a re-poll feedback loop, but "skip to Step 2" references an unlabeled step and there is no verification after running actions.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections with no nested references and no bundle files, but the large inline entity list and the inconsistent step numbering ("1b", "Step 2") are minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

73%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 clearly identifies a distinct niche (Syncro) and answers both what it does and when to use it, with good trigger keyword coverage. It is held back from the top band only by the generic single verb "Manage" and a narrow, generic "when" clause.

Suggestions

Replace the single verb "Manage" with distinct concrete actions (e.g., "Create, update, and query Organizations, Tickets, Leads, Emails, Users, Roles") to raise specificity.

Expand the trigger clause with concrete phrases, e.g. "Use when the user wants to manage Syncro tickets, leads, customers, or MSP operations."

Dimension	Reasoning	Score
Specificity	Names the Syncro domain and several concrete entities ("Manage Organizations, Tickets, Leads, Emails, Users, Roles"), but the single generic verb "Manage" does not enumerate distinct concrete actions, so it sits between the 1-2-action and several-action anchors.	3 / 5
Completeness	Both "what" ("Manage Organizations, Tickets, Leads, Emails, Users, Roles") and "when" ("Use when the user wants to interact with Syncro data") are explicit, but the trigger clause is singular and somewhat generic rather than a set of concrete varied triggers.	4 / 5
Trigger Term Quality	"Syncro" and the listed entity names (Tickets, Leads, Emails, Users, Roles) give good natural keyword coverage a user would actually say, though a few common variations are missing.	4 / 5
Distinctiveness Conflict Risk	"Syncro integration" targets a specific MSP platform with distinct triggers tied to the Syncro product name, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 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/syncro/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.