Name: contact-enhance
Rating: 52.8 (1 reviews)
Author: membranedev

contact-enhance

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

Quality

59%

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

Quality

Content

61%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 commands and a useful state-handling loop, but suffers from inconsistent workflow numbering and some unnecessary prose. It is well-structured for a single-file skill with no external references.

Suggestions

Reconcile the step numbering: label a clear 'Step 1: Connect' and 'Step 2: Discover and run actions' so the '1b' and 'Step 2' references resolve.

Trim padding such as 'so you can focus on the integration logic rather than auth plumbing' and the marketing-style intro paragraph.

Add an explicit verification/checkpoint after running an action or proxy request (e.g. check the response `output`/error field before reporting success).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-and-table content, but includes padding such as 'so you can focus on the integration logic rather than auth plumbing' and an explanatory intro paragraph that could be tightened, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste ready commands for the common cases (login, connection ensure, action list/run, request proxy) plus a concrete flags table, with only minor gaps such as the unresolved 'QUERY' intent placeholder.	4 / 5
Workflow Clarity	A sequence with polling and a client-action feedback loop is present, but step numbering is inconsistent — a '1b' subsection and references to 'Step 2' appear without a labeled Step 1 — leaving the overall flow with implicit checkpoints and gaps.	3 / 5
Progressive Disclosure	The content is a single well-organized file with clear section headers and no nested references, giving good structure and easy navigation; it is over 50 lines so it does not qualify for the simple-skill 5, and some inline material (the proxy flags table) could arguably live elsewhere.	4 / 5
	Total	14 / 20 Passed

Description

57%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' and is anchored to a specific product, but its action verbs are generic and it lacks the natural trigger terms (contacts, enrichment, leads) a user would actually say. It is competent but not exemplary.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Enrich contact records, search for leads, and sync Contact Enhance data' instead of 'Manage data, records, and automate workflows'.

Add natural trigger terms users would say, such as 'enrich contacts', 'lead enrichment', or 'contact data'.

Tighten the 'when' clause to name concrete intents, e.g. 'Use when the user wants to enrich or look up contact and lead information in Contact Enhance'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Contact Enhance integration') but its actions — 'Manage data, records, and automate workflows' — are minimal and generic rather than concrete operations like enrich, fetch, or update, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Contact Enhance data'), but the 'when' is generic and could be more explicit, fitting the 'has both what and when; when could be more specific' anchor.	4 / 5
Trigger Term Quality	It includes the specific product name 'Contact Enhance' plus 'data' and 'records', but omits the natural phrases a user would say ('enrich contacts', 'lead enrichment', 'contacts'), so it has some relevant keywords while missing common variations.	3 / 5
Distinctiveness Conflict Risk	The named product 'Contact Enhance' gives it a clear niche with distinct triggers and minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing could overlap with sibling Membrane integration skills.	4 / 5
	Total	13 / 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/contact-enhance/SKILL.md
Commit: f484c82

Reviewed: 4 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.