Name: icontact
Rating: 58.4 (1 reviews)
Author: membranedev

icontact

IContact integration. Manage Persons, Organizations, Deals, Activities, Pipelines, Leads and more. Use when the user wants to interact with IContact data.

Quality

67%

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/icontact/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 body is strongly actionable with a real end-to-end Membrane CLI workflow and explicit connection-state handling. It loses points mainly on conciseness (concept-explainer padding and a vague overview) and a stray incorrect documentation link.

Suggestions

Remove the introductory "IContact is an email marketing platform..." paragraph and the empty "IContact Overview" bullet list; assume Claude knows the domain and lead with the workflow.

Fix the "Official docs" link: https://developer.apple.com/documentation/contacts is Apple's Contacts framework, not IContact — point to the real IContact developer docs or remove the line.

Resolve the broken step anchors ("skip to Step 2", "1b" without a "1a") by explicitly labeling Step 1a/1b and Step 2 so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean CLI commands, but the opening "IContact is an email marketing platform..." paragraph and the skeletal "IContact Overview" ("Use action names and parameters as needed") are unnecessary padding that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-pasteable commands across the full workflow (install, login, connection ensure, action list/run, request) plus an actions table, with only minor gaps such as the vague overview and an incorrect docs URL.	4 / 5
Workflow Clarity	The connection flow has explicit state-based feedback loops (READY / CLIENT_ACTION_REQUIRED / error handling and re-polling), but it references an unlabeled "Step 2" and a "1b" without a "1a", and lacks verification steps after running actions.	4 / 5
Progressive Disclosure	Content is organized into clearly headed sections, but with no bundle files everything is inlined (~175 lines) and bulk such as the actions table and clientAction detail could be split into referenced files.	4 / 5
	Total	15 / 20 Passed

Description

67%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 covers a clear product niche with an explicit "Use when" clause, but its trigger vocabulary is thin and the "when" guidance is generic. Specificity is good on entities but light on distinct action verbs.

Suggestions

Expand the trigger clause with concrete natural phrases, e.g. "Use when the user wants to manage IContact email campaigns, subscription lists, contacts, or sends."

Replace the single verb "Manage" with specific actions (create, list, update, delete) so capabilities read as concrete verbs rather than one generic one.

Drop the "and more" hedge or replace it with the remaining concrete entities to avoid vague over-claiming.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Activities, Pipelines, Leads and more" names many concrete entities, but relies on a single generic action verb ("Manage") rather than multiple distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	It states both what ("IContact integration. Manage ...") and when ("Use when the user wants to interact with IContact data"), but the "when" clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The only trigger keywords are the product name "IContact" and "IContact data"; natural synonyms a user would say (email marketing, campaigns, contacts, lists) are missing, so common variations are absent.	3 / 5
Distinctiveness Conflict Risk	Binding triggers to the named product "IContact" makes it mostly distinct, though the name overlaps generic contact-management skills (the body even cites Apple's Contacts docs), creating minor conflict risk.	4 / 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/icontact/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.