Name: sharpspring
Rating: 64 (1 reviews)
Author: membranedev

sharpspring

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

Quality

76%

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/sharpspring/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 executable commands and a solid connection workflow including validation feedback loops. Its main weakness is a padded intro paragraph and a slightly broken step reference.

Suggestions

Remove or trim the opening marketing paragraph ("SharpSpring is a marketing automation and CRM platform...") — Claude already knows what SharpSpring is.

Fix the "skip to Step 2" cross-reference by explicitly labeling the searching-actions section as Step 2.

Add a brief validation note for destructive actions (delete-lead, delete-account) in the running-actions section.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("SharpSpring is a marketing automation and CRM platform designed to help businesses generate leads...") explains the platform with marketing fluff Claude already knows, and a few "focus on the integration logic" asides add padding.	3 / 5
Actionability	Copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a popular-actions table cover the common cases fully and are executable as written.	5 / 5
Workflow Clarity	The connection setup has explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-handle-repoll feedback loop, but the "skip to Step 2" reference points to an unlabeled section and delete operations lack explicit validation guidance.	4 / 5
Progressive Disclosure	Sections are well organized with no bundle files needed, but the long popular-actions table is inlined and could be better split or referenced.	4 / 5
	Total	16 / 20 Passed

Description

78%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 scopes the skill to SharpSpring with concrete entity types and an explicit use-when clause. It is distinct and well-triggered, with only minor specificity gaps in the trigger phrasing.

Dimension	Reasoning	Score
Specificity	"Manage Leads, Persons, Organizations, Deals, Projects, Activities and more" lists several concrete entity types, though the single verb "Manage" is generic and "and more" leaves minor gaps.	4 / 5
Completeness	Both a clear "what" (manage SharpSpring entities) and an explicit "Use when the user wants to interact with SharpSpring data" are present, but the trigger phrase could be more specific.	4 / 5
Trigger Term Quality	Natural terms like "SharpSpring", "Leads", "Deals", "Organizations" appear, giving good keyword coverage, but a few common phrasings users might say are absent.	4 / 5
Distinctiveness Conflict Risk	Tied to a named platform (SharpSpring) with entity-specific triggers, giving it a clear niche 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/sharpspring/SKILL.md
Commit: f484c82

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