Name: sendspark
Rating: 56.8 (1 reviews)
Author: membranedev

sendspark

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

Quality

65%

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

Quality

Content

67%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 strong, concrete Membrane CLI commands and a well-sequenced connection workflow with feedback loops. Its main weaknesses are minor padding, an empty "Popular actions" section, and a dangling "Step 2" reference.

Suggestions

Trim marketing/explanatory filler such as the customer-engagement sentence and "rather than auth plumbing" to improve conciseness.

Populate the "Popular actions" section with a few concrete Sendspark action examples (e.g., list/create/send video) instead of only redirecting to discovery.

Resolve the dangling "Step 2" reference by labeling the actual next section (e.g., searching/running actions) and add an explicit verify-the-output step after running an action.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes padding such as "This helps to build relationships and improve customer engagement" and "so you can focus on the integration logic rather than auth plumbing", matching the mostly-efficient-but-could-be-tightened anchor and falling short of the minor-over-explanation anchor at 4.	3 / 5
Actionability	Concrete copy-paste commands (login, connection ensure, action list/run, request) plus a flag table provide mostly executable guidance, but the "Popular actions" section is empty and action/connection IDs remain undiscovered placeholders, leaving minor gaps versus the fully-copy-paste-ready anchor at 5.	4 / 5
Workflow Clarity	The connection state machine is clearly sequenced with polling and feedback loops (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but a dangling "Step 2" reference and the absence of a final result-verification step leave minor validation gaps versus the explicit-checklist anchor at 5.	4 / 5
Progressive Disclosure	Content is organized into clear sections with no nested references, but the skill is over 50 lines with all content inlined and an effectively empty "Popular actions" section, so it stops short of the well-signaled one-level-deep-references anchor at 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 explicitly states both capability and an explicit "Use when" trigger, and benefits from a distinctive brand name. It is weakened by generic action verbs and a narrow trigger clause that misses common user phrasings.

Suggestions

Replace generic verbs with concrete Sendspark-specific actions (e.g., "create and send video messages, manage campaigns and video responses") to lift specificity and distinctiveness.

Broaden the trigger clause to mirror how users actually phrase the need (e.g., "Use when the user wants to create, send, or manage Sendspark videos, campaigns, or video responses").

Add natural synonyms and product-specific terms (videos, video responses, campaigns) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Sendspark domain plus a few actions, but the verbs (manage, automate) on vague objects (data, records) are generic rather than concrete, matching the 1-2 concrete-actions anchor and falling short of the several-specific-actions anchor at 4.	3 / 5
Completeness	It answers both what ("Sendspark integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Sendspark data."), but the "when" clause is narrow and lacks the concrete, varied trigger phrases of a 5.	4 / 5
Trigger Term Quality	The terms "Sendspark", "data", "records", and "workflows" are relevant, but the trigger "Use when the user wants to interact with Sendspark data" is narrow and misses common variations or synonyms users would say, matching the some-relevant-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	The named brand "Sendspark" provides a distinct niche with minimal conflict risk, but the generic action verbs (manage data, automate workflows) could overlap with other integration skills, keeping it just below the clear-niche anchor at 5.	4 / 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/sendspark/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.