CtrlK
BlogDocsLog inGet started
Tessl Logo

doppler-marketing-automation

Doppler Marketing Automation integration. Manage Accounts. Use when the user wants to interact with Doppler Marketing Automation data.

61

Quality

71%

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/doppler-marketing-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 content is highly actionable with copy-paste-ready Membrane CLI commands and good structural organization. Its main weakness is workflow clarity: the multi-step processes lack explicit validation/verification checkpoints, which is especially relevant for an integration that can perform batch or destructive marketing operations.

Suggestions

Add explicit validation checkpoints, e.g. after `connect`, verify the connection appears in `connection list` before running actions; after `action run`, inspect the output/error fields to confirm success.

Trim the promotional intro paragraph to a single line of product context, removing the marketing language ('nurture leads, promote products, improve customer engagement') that Claude does not need.

Add a brief error-recovery/feedback loop for action runs (what to do on auth expiry or failed runs), since actions can be batch or destructive.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete CLI commands and a tight overview tree, but the promotional intro ('nurture leads, promote products, improve customer engagement through targeted email communication') is minor over-explanation that could be trimmed; it is not 5 because of that padded prose and not 3 because the bulk is lean and actionable.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for every common case (login, search, connect, connection list, action list, action run, request) with a clear flag table and JSON input examples, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The steps are clearly sequenced (setup -> connect -> list -> search -> run -> proxy), but explicit validation/verification checkpoints are absent (e.g. no 'confirm the connection exists before running actions'); per the destructive/batch cap guidance for a skill that can send campaigns and modify contacts, workflow clarity cannot exceed 3, and it is not 2 because the sequence is coherent and ordered.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections (Overview, setup, connecting, searching, popular actions, best practices) with content appropriately kept in one file given its size and no bundle files present, matching 'Good structure; most content is appropriately placed; minor organization gaps'; it is not 5 because there are no well-signaled one-level-deep references and the 'Popular actions' section is thin.

4 / 5

Total

16

/

20

Passed

Description

66%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 well-formed with an explicit 'Use when' clause and a distinctive brand trigger, but it under-specifies the skill's actual capabilities and lacks concrete natural-language trigger phrases. Specificity and trigger-term quality are the main weaknesses.

Suggestions

Replace the single generic 'Manage Accounts' with the specific capabilities the skill supports (Campaigns, Emails, Forms, Lists/Contacts, Workflows, Reports) so the description reflects true coverage.

Add natural trigger phrases users would actually say, e.g. 'send or schedule email campaigns', 'manage subscriber lists and contacts', 'build signup forms', or 'view campaign and workflow reports'.

Tighten the 'Use when...' clause from the generic 'interact with ... data' to concrete triggers tied to those capabilities.

DimensionReasoningScore

Specificity

The description names the domain ("Doppler Marketing Automation integration") and one action area ("Manage Accounts"), matching the anchor for 'Names domain and 1-2 concrete actions, but not comprehensive'; it does not reach 4 because only a single, somewhat generic action is stated rather than several specific ones.

3 / 5

Completeness

Both 'what' ("Doppler Marketing Automation integration. Manage Accounts.") and 'when' ("Use when the user wants to interact with Doppler Marketing Automation data.") are explicitly present, matching 'Has both what and when; when could be more explicit or specific'; it is not 5 because the trigger is generic ('interact with ... data') rather than concrete capability phrases.

4 / 5

Trigger Term Quality

It contains the core brand keyword ("Doppler Marketing Automation") and a "Use when" trigger, but misses the natural capability phrases users would say (campaigns, emails, lists, forms), fitting 'Some relevant keywords but missing common variations or synonyms'; it is not a 4 because keyword coverage is thin beyond the brand name.

3 / 5

Distinctiveness Conflict Risk

The skill is branded to a specific product ("Doppler Marketing Automation") with a brand-named trigger, giving it a clear niche with minimal conflict risk against other skills; it does not drop to 4 because the brand name itself is highly distinctive.

5 / 5

Total

15

/

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.