Name: salesflare
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

salesflare

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

Quality

61%

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

Quality

Content

61%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 delivers executable CLI guidance with a clear connection state machine, but explanatory padding and the absence of validation checkpoints around data-modifying actions limit conciseness and workflow clarity. Adding verify steps after destructive action runs would notably strengthen it.

Suggestions

Add a validation/retry step after `membrane action run` for mutating operations (e.g., re-query to confirm the change landed).

Trim conversational filler like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection".

Fix the dangling "skip to Step 2" reference, which has no corresponding labeled Step 2.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete bash commands, but includes unnecessary conversational padding such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection", fitting the score-3 anchor.	3 / 5
Actionability	It provides concrete, executable commands (membrane connection ensure, action run, request with a flag table) covering common cases, with only minor gaps like the CONNECTION_ID placeholder, matching the score-4 anchor.	4 / 5
Workflow Clarity	The connection flow (ensure -> poll state -> branch on READY/BUILDING/CLIENT_ACTION_REQUIRED) is sequenced with state checks, but destructive/batch operations (action run, proxy DELETE/POST) lack result validation or feedback loops, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files needed, though the length and inline best-practices rationale leave minor organization gaps versus a 5.	4 / 5
	Total	14 / 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 clearly names its niche and includes an explicit trigger clause, but the capability verbs are generic. Tightening 'Manage data, records, and automate workflows' into concrete actions would raise specificity.

Suggestions

Replace generic verbs with concrete Salesflare actions (e.g., 'Create and update contacts, manage opportunities, log tasks and emails, run workflows').

Add natural synonyms users might say, such as 'CRM', 'leads', 'deals', or 'contacts'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Salesflare) but the actions — "Manage data, records, and automate workflows" — are generic verbs rather than concrete capabilities, matching the score-2 anchor ('Names the domain but actions are minimal or generic').	2 / 5
Completeness	Both 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Salesflare data") are present; the 'when' is clear though the 'what' could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	"Salesflare" and "interact with Salesflare data" are relevant keywords but the phrasing lacks natural synonyms or common variations users might say, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Salesflare is a specific named CRM with a distinct trigger ("interact with Salesflare data"), giving it a clear niche with minimal conflict risk against other skills.	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/salesflare/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.