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

Blog Docs Log in Get started

cyberimpact

Cyberimpact integration. Manage Contacts, Campaigns, Forms. Use when the user wants to interact with Cyberimpact 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/cyberimpact/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.

The content is highly actionable with executable CLI commands and a useful actions table, and is reasonably well structured. It is held back by an unnecessary introductory concept paragraph and a lack of validation guidance around destructive/batch operations.

Suggestions

Remove or tighten the opening "Cyberimpact is an email marketing platform..." paragraph, which explains concepts Claude already knows.

Add explicit validation/verification steps for destructive and batch operations (e.g., list-after-delete confirmation, dry-run or confirmation before sending a mailing).

Fix the step numbering ("Step 2" is referenced but unlabeled, and "1b" appears without a 1a) so the connection workflow reads as a coherent sequence.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what an email marketing platform is and who uses it pads the document with concepts Claude already knows, though the CLI command sections are mostly efficient.	3 / 5
Actionability	Commands are concrete and copy-paste ready (membrane login, connection ensure with --wait polling, action run with --input JSON, request proxy), and the populated actions table covers common cases with real keys.	5 / 5
Workflow Clarity	The connection state-machine has a clear sequence and feedback loop, but destructive and batch operations in the actions table (delete-member, delete-group, create/update-mailing) lack any validation/verification steps, which caps this dimension.	3 / 5
Progressive Disclosure	No bundle files exist; the single self-contained document is organized into clear, well-labeled sections, though the large inline popular-actions table and proxy flag reference could arguably be split out.	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.

The description answers both what and when, names a specific platform and concrete action domains, and carries low conflict risk. It could be stronger with more comprehensive coverage of the platform's capabilities and more concrete, varied trigger phrases.

Suggestions

Expand the capability list to match the body (e.g., add Automations, Reports, Transactions) for more comprehensive specificity.

Replace the generic "interact with Cyberimpact data" trigger with concrete phrases users would say, such as "when the user mentions email lists, newsletters, campaigns, or contact forms".

Add common synonyms/file-type terms (email lists, mailings) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Manage Contacts, Campaigns, Forms" lists several concrete action domains, but omits automations, reports, and transactions covered in the body, leaving minor coverage gaps.	4 / 5
Completeness	Both a clear "what" (Manage Contacts, Campaigns, Forms) and an explicit "when" (Use when the user wants to interact with Cyberimpact data) are present, though the trigger clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms like Contacts, Campaigns, Forms, and "interact with Cyberimpact data", but lacks common synonyms users might say such as email lists, newsletters, or mailings.	4 / 5
Distinctiveness Conflict Risk	Naming the specific Cyberimpact platform gives it a clear niche with distinct triggers and 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/cyberimpact/SKILL.md
Commit: f484c82

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