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

getresponse

GetResponse integration. Manage data, records, and automate workflows. Use when the user wants to interact with GetResponse data.

Quality

68%

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

Quality

Content

75%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 delivers a clear, mostly executable workflow for using the Membrane CLI with GetResponse, with strong command examples and state-handling checkpoints. Its main weaknesses are minor redundancy and a couple of placeholder-heavy or loosely labeled steps rather than substantive gaps.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, tables, and state-handling bullets with only minor over-explanation (the introductory 'so you can focus on the integration logic rather than auth plumbing' and the platform-description paragraph), fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Concrete, copy-paste-ready commands are provided throughout (npm install, membrane login, connection ensure, action list/run, request) with a clear proxy-flags table, but placeholders like CONNECTION_ID and the vague 'QUERY' intent leave minor gaps versus fully worked examples.	4 / 5
Workflow Clarity	There is a clear install -> authenticate -> connect -> poll-for-ready -> search -> run sequence with explicit state-based checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a polling feedback loop; a dangling 'Step 2' reference and unlabeled step numbering are minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in a single well-organized SKILL.md with clear section headers and an external 'Official docs' link; structure is good, though the 'Popular actions' section partially duplicates 'Searching for actions'.	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 is third-person, identifies the GetResponse domain, and includes an explicit 'Use when' trigger, but its action language is generic and it lacks the natural synonyms (email marketing, campaigns, newsletters) that would aid discovery. It is solid but not comprehensive.

Suggestions

Replace generic verbs with concrete GetResponse actions, e.g. 'send newsletters, build email lists, automate marketing campaigns, create landing pages'.

Add natural synonyms and trigger phrases users say, such as 'email marketing', 'campaigns', or 'autoresponders'.

Sharpen the 'when' clause to name concrete scenarios, e.g. 'Use when the user wants to send campaigns or manage GetResponse contacts'.

Dimension	Reasoning	Score
Specificity	Names the domain ('GetResponse integration') and multiple action phrases ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete GetResponse-specific capabilities such as sending newsletters or building lists.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with GetResponse data') are present, but the trigger is generic rather than concrete, fitting the 'both present, when could be more specific' anchor.	4 / 5
Trigger Term Quality	The natural keyword 'GetResponse' is present and repeated, but no synonyms or common variations ('email marketing', 'newsletters', 'campaigns') are included, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The GetResponse brand name gives it a clear niche with minimal conflict risk, but the generic action phrasing ('manage data, records') could overlap with other integration skills, keeping it just below the fully distinct anchor.	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/getresponse/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.