Name: flodesk
Rating: 59.2 (1 reviews)
Author: membranedev

flodesk

Flodesk integration. Manage Users, Subscribers, Emails, Workflows. Use when the user wants to interact with Flodesk data.

Quality

69%

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

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 body is highly actionable with copy-paste commands and a well-sequenced connection workflow, but it lacks verification guidance for destructive subscriber operations and keeps some reference-style tables inline.

Suggestions

Add an explicit verification/confirmation step before running destructive actions (e.g. 'Before remove-subscriber or unsubscribe, confirm the target subscriber ID with the user').

Trim the opening descriptive paragraph about what Flodesk is, since Claude does not need that background to operate the CLI.

Consider moving the Popular actions catalog into a references file and keeping only a few key examples inline, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is command-focused and lean with executable snippets, but the opening marketing paragraph ('Flodesk is an email marketing platform designed for small businesses...') and a few padded phrasings could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run with JSON input, proxy flags) plus a concrete actions table, fully covering the common cases.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with state-checking feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the skill exposes destructive actions (remove/unsubscribe subscribers) with no verification step before execution, capping clarity per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references, though the 13-row Popular actions table and proxy-flag table are reference-style content kept inline rather than split into separate files.	4 / 5
	Total	16 / 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 cleanly answers both 'what' and 'when' and targets a distinct named platform, but relies on a single generic verb ('Manage') and only the brand name as a trigger term.

Suggestions

Replace the generic 'Manage' with more concrete verbs (e.g. 'Create, list, update, and remove subscribers, segments, and workflows') to raise specificity.

Expand the 'Use when' clause with natural trigger phrases users would say, such as 'Use when the user wants to manage Flodesk subscribers, segments, workflows, or email campaigns.'

Add common synonyms or related terms (e.g. 'email lists', 'email marketing') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Flodesk domain and lists four concrete resources (Users, Subscribers, Emails, Workflows), but the only action verb is the generic 'Manage', so actions are minimal rather than comprehensive.	3 / 5
Completeness	It states what the skill does ('Manage Users, Subscribers, Emails, Workflows') and gives an explicit 'when' ('Use when the user wants to interact with Flodesk data'), but the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural keyword 'Flodesk' appears and 'interact with Flodesk data' is a reasonable phrase, but no synonyms or common variations are given, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Flodesk' is a specific named platform giving it a clear niche with minimal conflict risk, though it could overlap with other email-marketing integration skills.	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/flodesk/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.