Name: sare
Rating: 67.2 (1 reviews)
Author: membranedev

sare

SARE integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with SARE data.

Quality

81%

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

Quality

Content

82%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.

A highly actionable CLI-integration skill with concrete commands and a solid connection-readiness workflow. The main improvements are tightening a few redundant/explanatory passages and fixing the dangling step numbering so the workflow is unambiguous.

Suggestions

Fix the step numbering: either number the workflow steps explicitly (1. Install, 2. Authenticate, 3. Connect...) or remove the undefined "Step 2" reference so the sequence is unambiguous.

De-duplicate the `action list --intent=QUERY` example (it appears in both "Searching for actions" and "Popular actions") and trim the SARE background paragraph to lift conciseness toward 5.

Consider moving the proxy flag table and connection-state reference into a separate reference file to strengthen progressive disclosure and keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient CLI documentation, but includes minor trimmable material: a SARE background paragraph ("SARE is a marketing automation platform...") and a duplicated `action list --intent` example in both "Searching for actions" and "Popular actions".	4 / 5
Actionability	It provides copy-paste ready bash commands with concrete flags (--json, --connectionId, --wait, --input) covering install, login, connection ensure/get, action list/run, and proxy requests, with a flag table for the proxy — fully executable and covering the common cases.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with a state-based polling feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but step numbering is broken — a "Step 2" is referenced yet never labeled, and steps are not consistently numbered.	4 / 5
Progressive Disclosure	The single-file body is well-organized into clear sections with no nested references and no bundle files to mismanage; inline reference-like material (the proxy options table, connection-state details) keeps it just below a 5 for a >50-line skill.	4 / 5
	Total	17 / 20 Passed

Description

80%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.

A strong description with an explicit what/when structure and a distinct, named-platform niche. Its main weakness is trigger-term coverage, which is limited to the product name and lacks the natural synonyms users would actually say.

Suggestions

Add natural trigger synonyms users would say, e.g. "Use when the user wants to manage SARE marketing automation data — contacts, email/SMS campaigns, deals, or leads."

Replace the generic "Manage" and vague "and more" with a tighter verb set (e.g. "Create, update, and query Persons, Organizations, Deals, Leads, Projects, and Activities") to lift specificity to a clear 5.

Dimension	Reasoning	Score
Specificity	It names the SARE domain and several concrete managed entities ("Persons, Organizations, Deals, Leads, Projects, Activities"), but the action verb is the single generic "Manage" and "and more" leaves a coverage gap, sitting just below a fully comprehensive 5.	4 / 5
Completeness	It explicitly answers both what ("Manage Persons, Organizations, Deals, Leads, Projects, Activities") and when ("Use when the user wants to interact with SARE data") with a concrete trigger phrase, matching the top anchor.	5 / 5
Trigger Term Quality	Only "SARE" and "SARE data" appear as trigger terms; common natural synonyms a user might say ("marketing automation", "contacts", "email/SMS campaigns") are missing, matching the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	SARE is a specifically named platform with a clear niche ("SARE integration", "interact with SARE data"), making it easily distinguishable from other skills with minimal conflict risk.	5 / 5
	Total	17 / 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/sare/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.