Name: freshsales
Rating: 52 (1 reviews)
Author: membranedev

freshsales

Freshsales integration. Manage crm and sales data, records, and workflows. Use when the user wants to interact with Freshsales data.

Quality

58%

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

Quality

Content

46%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 actionable CLI workflow half is strong and executable, but it is buried under a ~1600-line padded overview list that destroys token efficiency and structure. The skill needs the overview stripped and validation added around its destructive/batch operations.

Suggestions

Delete the ~1600-line "Freshsales Overview" bullet list — it is padded, largely non-Freshsales-specific, and adds no actionable value; keep only the genuine Freshsales entities if a short list is needed.

Add a validation/verification checkpoint before destructive and batch operations, e.g. confirm the record ID and run a get-* action to verify before delete-*, and require explicit user confirmation for Bulk Action.

If a long entity/action catalog is genuinely useful, move it to a references/ file and link to it one level deep so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The "Freshsales Overview" section is ~1600 lines of repeated, generic bullet terms (Trademark, Podcast, Scholarship, Merger, etc.) that are heavily padded and not Freshsales-specific, matching the severely-verbose/heavily-padded anchor despite the lean CLI section that follows.	1 / 5
Actionability	The working section provides fully executable, copy-paste-ready commands — `npm install -g @membranehq/cli@latest`, `membrane connection ensure ...`, `membrane action run <actionId> --input '{...}'`, `membrane request CONNECTION_ID /path` — plus a popular-actions table covering common cases.	5 / 5
Workflow Clarity	The connect/setup flow is sequenced with state-check checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED), but the skill exposes destructive actions (delete-deal/delete-account/delete-contact) and a Bulk Action with no validation/verification steps, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the giant overview list is a monolithic wall of inlined content that clearly does not belong in SKILL.md; only the latter working section has real headers, leaving structure minimal and references absent.	2 / 5
	Total	11 / 20 Passed

Description

70%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 is third-person, distinct, and supplies both a what and an explicit when clause, placing it above midpoint. Its main weakness is generic, non-concrete action language ("manage") rather than named CRM operations.

Suggestions

Replace the generic verb "Manage" with concrete operations, e.g. "Create, update, list, and delete deals, contacts, accounts, and leads in Freshsales."

Add a few natural trigger synonyms users might say, such as "CRM records", "sales pipeline", or "Freshsales CRM".

Tighten the "when" clause with concrete triggers, e.g. "Use when the user wants to create or update Freshsales deals, contacts, accounts, or leads."

Dimension	Reasoning	Score
Specificity	"Manage crm and sales data, records, and workflows" names the Freshsales domain and a couple of action targets, but the verb "manage" is generic rather than a set of concrete actions like create/update/delete deals or contacts.	3 / 5
Completeness	It answers both "what" (Freshsales integration; manage crm/sales data, records, workflows) and "when" ("Use when the user wants to interact with Freshsales data"), but the "what" is generic and the "when" is simple rather than richly specific.	4 / 5
Trigger Term Quality	Natural terms a user would say are present — "Freshsales", "crm", "sales data", "interact with Freshsales data" — giving good keyword coverage, though a few synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	The named product "Freshsales" is a distinct trigger with minimal conflict risk, but the generic CRM/sales-data language leaves minor overlap with sibling CRM skills (e.g. Salesforce, HubSpot).	4 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1759 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/freshsales/SKILL.md
Commit: f484c82

Reviewed: 5 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.