Name: aweber
Rating: 62.4 (1 reviews)
Author: membranedev

aweber

AWeber integration. Manage Subscribers, Lists, Broadcasts, Automations, Tags. Use when the user wants to interact with AWeber data.

Quality

73%

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

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.

A highly actionable skill with copy-paste commands and a well-structured connection workflow featuring explicit state feedback loops. It is held back by mild intro padding and the absence of verification steps around destructive delete operations.

Suggestions

Remove the marketing-style opening paragraph and the filler "When to use which actions" line to tighten conciseness.

Add a validation/confirmation step before destructive actions (e.g., "Confirm the subscriber ID before running delete-subscriber; verify the deletion with get-subscriber"), which would lift workflow clarity above the destructive-ops cap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the opening marketing paragraph ("It's used by small businesses, entrepreneurs, and marketers to build email lists...") and filler like "When to use which actions: Use action names and parameters as needed." add unnecessary explanation Claude does not need.	3 / 5
Actionability	Copy-paste-ready commands are given throughout (npm install, membrane login, connection ensure, action run, request) with concrete flags and a parameterized JSON-input example, fully covering common cases.	5 / 5
Workflow Clarity	The connect→poll→search→run sequence is clear with explicit state handling and feedback loops for the connection flow, but destructive operations (Delete Subscriber, Delete Broadcast) are presented with no validation or verification checkpoint, capping the score per the destructive-operations rule.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with the action table reasonably inlined; no external reference files are signaled, but none are strictly needed at this length.	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 focused, third-person description that clearly names the AWeber domain and its entities and includes an explicit use-when clause. It is strong on distinctiveness but could enumerate concrete verbs and richer trigger phrases.

Suggestions

Replace the generic "Manage" with concrete verbs (e.g., add/update/delete subscribers, create/schedule broadcasts) to lift specificity.

Expand the "Use when" clause with natural triggering phrases (e.g., "email lists", "newsletter subscribers", "email campaigns") for better trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Subscribers, Lists, Broadcasts, Automations, Tags" names several concrete resource types with a clear action verb, though the actions are generic per entity rather than enumerated (e.g., add/update/delete).	4 / 5
Completeness	It states both what ("AWeber integration. Manage Subscribers, Lists, Broadcasts, Automations, Tags") and when ("Use when the user wants to interact with AWeber data"), but the trigger clause is somewhat generic rather than listing concrete triggering phrases.	4 / 5
Trigger Term Quality	"AWeber" plus the entity terms (Subscribers, Lists, Broadcasts, Automations, Tags) give good keyword coverage a user would naturally say, but synonyms and file/extension variants are absent.	4 / 5
Distinctiveness Conflict Risk	AWeber is a distinct named product with a clear niche, and the trigger is tied specifically to AWeber data, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/aweber/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.