Name: reverse-contact
Rating: 64 (1 reviews)
Author: membranedev

reverse-contact

Reverse Contact integration. Manage Persons, Organizations, Users, Goals, Filters. Use when the user wants to interact with Reverse Contact data.

Quality

76%

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

Quality

Content

75%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 executable commands and a clear connection/workflow sequence, and it is well-structured into navigable sections. Its main weaknesses are trimmable marketing-style prose and a missing error-recovery feedback loop for action execution.

Suggestions

Cut the descriptive opener ("Reverse Contact helps sales teams identify decision-makers...") and the "so you can focus on..." / "burn less tokens" asides to tighten token efficiency.

Add an explicit validate/retry feedback loop after `membrane action run` (check the `output` field for errors, re-fetch connection state, retry on transient failure).

Merge the near-duplicate "Searching for actions" and "Popular actions" command examples to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The bulk is lean command reference, but prose padding (the sales-team opener, "so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens and make communication more secure") goes beyond minor trimmable instances.	3 / 5
Actionability	Copy-paste-ready commands are given throughout (npm install, membrane login, connection ensure, action list/run, request) with a complete proxy-flag table and clear placeholders, covering the common cases.	5 / 5
Workflow Clarity	The install → auth → connect → poll → search → run sequence is clear with explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling, though the action-run and proxy steps lack explicit result/error feedback loops.	4 / 5
Progressive Disclosure	Well-organized into clear section headers with no external references needed and no nesting, but it is a single ~140-line file (above the 50-line simple-skill carve-out) with minor redundancy between the "Searching for actions" and "Popular actions" sections.	4 / 5
	Total	16 / 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 clearly names the product and its domain objects and includes a Use-when trigger, making it distinct and reasonably complete. It is held back from top marks by the generic repeated verb "Manage" and a slightly circular when-clause.

Suggestions

Replace the generic "Manage" with concrete verbs (e.g. "Search, enrich, and update Persons, Organizations, Users, Goals, and Filters") to lift specificity.

Sharpen the trigger to a concrete user phrasing (e.g. "Use when the user wants to look up a contact's employer, enrich a lead, or find decision-makers in a target account").

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Users, Goals, Filters" lists several concrete domain objects to act on, but the single generic verb "Manage" keeps it short of the comprehensive, multi-verb anchor 5 example.	4 / 5
Completeness	It states the what ("Manage Persons, Organizations, Users, Goals, Filters") and an explicit when clause ("Use when the user wants to interact with Reverse Contact data"), but the when is somewhat circular rather than offering concrete trigger phrases.	4 / 5
Trigger Term Quality	"Reverse Contact", the entity names, and "interact with Reverse Contact data" are natural phrases a user would say, though synonyms/variations are limited since it is a named product with no file extensions.	4 / 5
Distinctiveness Conflict Risk	"Reverse Contact" is a specific named product with entity-specific triggers, giving it a clear niche and minimal risk of triggering for unrelated 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/reverse-contact/SKILL.md
Commit: f484c82

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