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

customerio

Customer.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Customer.io 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/customerio/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 guide to the Membrane CLI integration with a solid connection-validation workflow, weakened mainly by a verbose marketing-style intro and placeholder-only examples rather than a concrete end-to-end run.

Suggestions

Trim or remove the opening 'Customer.io is a marketing automation platform...' paragraph; Claude can be told the product is marketing automation without the engagement/marketing-team prose.

Add one concrete end-to-end example (e.g. listing and running a 'create or update customer' action with a realistic input JSON) so actionability reaches copy-paste completeness.

Render the search→run→proxy flow as an explicit numbered sequence so the full workflow, not just the connection step, reads as a checklist.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands, but the opening product-marketing paragraph ('Customer.io is a marketing automation platform that helps businesses send targeted emails... used by marketing and product teams to personalize customer experiences') explains what the product is, and the 'Popular actions' section repeats the action-list command, which could be trimmed.	3 / 5
Actionability	It provides many copy-paste-ready commands with real flags (install, login, connection ensure, action list/run, request) and a flag reference table, but examples use generic placeholders (CONNECTION_ID, <actionId>, '{"key": "value"}') rather than a concrete end-to-end action run, leaving minor gaps.	4 / 5
Workflow Clarity	The connection setup is a clear sequence with an explicit validation checkpoint (poll state, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action) and an error-recovery feedback loop, but the broader search→run→proxy flow is section-organized rather than an explicit numbered sequence, keeping it below the 5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained file organized into clear sections (Overview, Working with Customer.io, Popular actions, Best practices) with no nested references, giving good structure with minor organization gaps, though at ~140 lines it exceeds the simple-skill (<50 line) exception that would allow a 5.	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 clearly identifies the Customer.io niche and includes a usable 'Use when' trigger, but the capability list ('manage data, records, automate workflows') is generic and the trigger phrases lack concrete sub-feature keywords.

Suggestions

Replace generic actions with concrete Customer.io operations, e.g. 'manage customers and attributes, build segments, trigger campaigns, and send emails/SMS'.

Expand the trigger to mention concrete artifacts users name, e.g. 'Use when the user wants to manage Customer.io customers, segments, campaigns, newsletters, or data exports.'

Add natural synonyms/file-format-adjacent terms (campaigns, segments, broadcasts, event tracking) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Customer.io integration') and a few actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete API-level operations, so it sits at the '1-2 concrete actions, not comprehensive' anchor rather than the comprehensive 4/5 anchors.	3 / 5
Completeness	Both 'what' ('Customer.io integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with Customer.io data.') are present, but the trigger is somewhat generic rather than enumerating concrete trigger phrases, so it does not reach the explicit-trigger 5 anchor.	4 / 5
Trigger Term Quality	The product name 'Customer.io' is present and the phrase 'interact with Customer.io data' is a reasonable trigger, but coverage relies almost entirely on the single product name with no synonyms, sub-features (campaigns, segments, emails), or natural variations, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Customer.io integration' targets a clearly distinct third-party product with a unique name, giving it a clear niche and minimal conflict risk with other skills.	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/customerio/SKILL.md
Commit: f484c82

Reviewed: ~15 hours 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.