CtrlK
BlogDocsLog inGet started
Tessl Logo

sendloop

Sendloop integration. Manage Subscribers, Lists, Segments, Campaigns, Forms. Use when the user wants to interact with Sendloop data.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sendloop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable CLI guidance with strong executable examples, but it is weakened by a padded intro/redundant section and the absence of validation checkpoints for destructive-capable operations like running actions and proxy requests.

Suggestions

Trim the marketing-style opening paragraph and the redundant 'Popular actions' section that restates the action-list command.

Add explicit validation/verification checkpoints after running actions or proxy requests (e.g. confirm subscriber count before a campaign send, check the response status and error fields before proceeding).

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but the marketing-style intro ('Sendloop is an email marketing automation platform designed for businesses of all sizes...') and the 'Popular actions' section restating the already-shown action-list command are unnecessary padding.

3 / 5

Actionability

Provides copy-paste-ready, fully executable CLI commands for setup, connecting, listing, searching, running actions with JSON params, and proxy requests, with a clear flags table covering common cases.

5 / 5

Workflow Clarity

The connect-then-run sequence is present, but running actions and proxy requests can be destructive or batch (sending campaigns, deleting subscribers) and there are no validation or verification checkpoints, capping this dimension at 3.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references; all content is inline in a single file with good structure, though some sections (e.g. the proxy flags table) could justify separation if the skill grows.

4 / 5

Total

15

/

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.

A solid description that names the product, lists concrete capabilities, and includes an explicit use-when trigger. The main weakness is the generic 'Manage' verb and a when-clause that could enumerate concrete user phrasings.

Suggestions

Replace the single 'Manage' verb with varied concrete actions (e.g. 'Create and segment subscriber lists, build and send campaigns, design forms').

Expand the 'Use when' clause with concrete user phrasings (e.g. 'Use when the user mentions email campaigns, newsletters, subscriber lists, or Sendloop').

DimensionReasoningScore

Specificity

Names several concrete capabilities ('Manage Subscribers, Lists, Segments, Campaigns, Forms') but uses a single generic verb 'Manage' across all of them, leaving minor gaps versus comprehensive coverage.

4 / 5

Completeness

Provides a clear 'what' ('Manage Subscribers, Lists, Segments, Campaigns, Forms') and a 'when' ('Use when the user wants to interact with Sendloop data'), though the when-clause is generic rather than listing concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes natural domain terms (Subscribers, Lists, Segments, Campaigns, Forms) plus the product name Sendloop, but misses common synonyms a user might say like 'email marketing' or 'newsletter'.

4 / 5

Distinctiveness Conflict Risk

Anchored to a specific named product (Sendloop) with a clear niche, so it is unlikely to trigger for unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.