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

icypeas

Icypeas integration. Manage Organizations, Pipelines, Users, Goals, Filters, Projects. Use when the user wants to interact with Icypeas 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/icypeas/SKILL.md

Quality

Content

76%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 is highly actionable with concrete, executable commands and a solid connection-state workflow, but it lacks validation/verification guidance for destructive proxy and action operations, and a few sections (the Overview, step cross-references) are loosely structured. Adding verify-before-destructive-action checkpoints and tightening the Overview would lift the weakest dimensions.

Suggestions

Add an explicit validation/verification step before destructive operations, e.g. a "Confirm before DELETE/PUT/PATCH" note in the proxy section and a dry-run/confirm pattern for `membrane action run` on write actions.

Clean up the "Icypeas Overview" section by either filling in the empty "Properties" bullets or removing them, and replace "Use action names and parameters as needed" with concrete guidance.

Make the multi-step workflow numbering explicit and consistent (numbered steps 1-N) so cross-references like "skip to Step 2" resolve to actual headers.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-focused with lean tables and code blocks, though the intro paragraph ("Product managers and customer success teams are typical users") and filler like "Use action names and parameters as needed" could be trimmed, matching the efficient-with-minor-over-explanation anchor 4.	4 / 5
Actionability	It provides copy-paste-ready, executable commands for every common case (install, login, connection ensure/get, action list/run, request proxy) plus a concrete popular-actions table and a flags table, fully covering the common cases as in anchor 5.	5 / 5
Workflow Clarity	A clear connect-search-run sequence exists with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling, but the skill enables destructive operations (proxy DELETE/PUT/PATCH, action runs against a contacts database) with no verify-before-act guidance, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The content is well-organized into clear topical sections with no nested references (no bundle files exist), but the "Icypeas Overview" section lists entities with empty "Properties" bullets and loose "Step 2" cross-references, leaving minor organization gaps at anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

71%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 cleanly covers what and when for a clearly distinct, product-specific integration, but its trigger phrasing is generic and misses the natural task keywords users would actually say. Tightening the "when" clause with concrete use-case triggers would raise completeness and trigger-term quality.

Suggestions

Expand the "Use when..." clause with concrete task triggers users would naturally say, e.g. "Use when finding people, verifying emails, scraping LinkedIn profiles, or searching domains via Icypeas."

Vary the action verbs beyond the single generic "Manage" to convey distinct capabilities (e.g., "Search leads, verify emails, scrape LinkedIn profiles, manage organizations and pipelines").

Add common synonyms or file/term variations so the trigger matches a wider range of natural user phrasings.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists several concrete managed entities ("Manage Organizations, Pipelines, Users, Goals, Filters, Projects"), giving several specific actions, though the single generic verb "Manage" limits action diversity compared to the comprehensive multi-verb anchor 5.	4 / 5
Completeness	Both "what" (manage Organizations, Pipelines, Users, etc.) and "when" ("Use when the user wants to interact with Icypeas data") are present and explicit, but the "when" clause is generic rather than listing concrete trigger phrases, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	It relies on the brand keyword "Icypeas" and the phrase "interact with Icypeas data", but lacks the natural task phrases users would actually say (e.g., "find people", "verify email", "scrape LinkedIn"), missing common variations and synonyms.	3 / 5
Distinctiveness Conflict Risk	The product-specific trigger "Icypeas" carves out a clear niche with distinct triggers and minimal conflict risk against other skills, matching the anchor 5 example of a clearly distinct product-scoped skill.	5 / 5
	Total	16 / 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/icypeas/SKILL.md
Commit: f484c82

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