Name: woosender
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

woosender

Woosender integration. Manage Organizations. Use when the user wants to interact with Woosender data.

Quality

66%

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/woosender/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 content is a well-structured, actionable integration guide with strong feedback loops in the connection workflow. It is held back mainly by a marketing-style intro and the absence of validation guidance around data-modifying actions.

Suggestions

Trim the marketing intro and explanatory prose (e.g., the WooCommerce audience description, 'so you can focus on the integration logic') to assume Claude's competence.

Add a brief validation/verification step after running data-modifying actions (e.g., re-fetch or check the response error field) to support destructive operations.

Consider moving the popular-actions table and proxy flag reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The bulk is lean commands and tables, but the marketing-style intro ('email marketing automation platform built for WooCommerce store owners...') and prose like 'so you can focus on the integration logic rather than auth plumbing' add unnecessary explanation Claude does not need, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Commands are concrete and copy-paste ready (login, connection ensure, action run, request) and a popular-actions table gives real keys, but examples rely on placeholders (CONNECTION_ID, actionId) and the actions table lists keys without usage, leaving minor gaps below the fully copy-paste-ready bar.	4 / 5
Workflow Clarity	The connection setup is well sequenced with explicit state checks and feedback loops (poll BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll, handle CONFIGURATION_ERROR), but the action-running section lacks explicit verification of outcomes, a minor validation gap that keeps it just below 5.	4 / 5
Progressive Disclosure	The body is organized into clearly headed sections with no nested references, and with no bundle files present the inline tables are acceptable; the large popular-actions table and proxy-options table could arguably live in separate reference files, a minor organization gap that fits 'good structure, most content appropriately placed'.	4 / 5
	Total	15 / 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 correctly answers both what and when and is highly distinct thanks to the named product, but its action list is thin and the trigger phrasing is generic. Tightening with a couple more concrete actions and richer trigger terms would raise it.

Suggestions

List 2-3 concrete actions beyond 'Manage Organizations' (e.g., campaigns, contacts, lists, templates) to improve specificity and alignment with the body's entity list.

Expand the 'Use when' clause with concrete trigger phrases users would actually say (e.g., 'Use when managing Woosender campaigns, contacts, lists, or scheduled emails').

Verify 'Organizations' matches a real Woosender entity, since the body's overview lists Campaign/List/Template/etc. but not Organizations.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Woosender integration') and one concrete action ('Manage Organizations'), matching the '1-2 concrete actions but not comprehensive' anchor; it is not score 2 because a specific object type is named, and not score 4 because only a single, somewhat generic action is listed.	3 / 5
Completeness	Both 'what' ('Woosender integration. Manage Organizations.') and 'when' ('Use when the user wants to interact with Woosender data.') are present, but the 'when' clause is generic rather than packed with concrete trigger phrases, so it stops at 'both present but when could be more specific' rather than reaching 5.	4 / 5
Trigger Term Quality	It includes the natural keyword 'Woosender' and a trigger phrase ('Use when the user wants to interact with Woosender data'), but offers no synonyms, file extensions, or common variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Woosender' gives it a clear niche with a distinct trigger and minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/woosender/SKILL.md
Commit: f484c82

Reviewed: 3 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.