Name: rocketreach
Rating: 55.2 (1 reviews)
Author: membranedev

rocketreach

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

Quality

62%

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/rocketreach/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 content is a well-structured, actionable CLI guide with a solid connection-state feedback loop, weakened by a background intro paragraph, inconsistent step numbering, and some redundant action sections.

Suggestions

Trim the opening RocketReach background paragraph and the auth-plumbing commentary to assume Claude's competence.

Fix the step numbering: label 'Step 1' and 'Step 2' explicitly so the 'skip to Step 2' reference resolves.

Merge the 'Searching for actions', 'Popular actions', and 'Running actions' sections to remove redundant action-list instructions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what RocketReach is and prose like 'so you can focus on the integration logic rather than auth plumbing' is over-explanation Claude does not need.	3 / 5
Actionability	It provides copy-pasteable bash commands for install, login, connection, action list/run, and proxy with a flag table; minor gaps are the placeholder values (CONNECTION_ID, actionId, QUERY) that the reader must fill in.	4 / 5
Workflow Clarity	The connection flow has a genuine validation feedback loop (poll BUILDING, handle CLIENT_ACTION_REQUIRED, check error on CONFIGURATION_ERROR), but the 'skip to Step 2' reference points to no labeled Step 2 and the '1b' numbering is inconsistent.	4 / 5
Progressive Disclosure	The single file is well-sectioned with clear headers and no nested references are needed, though the 'Searching for actions', 'Popular actions', and 'Running actions' sections overlap and could be consolidated.	4 / 5
	Total	15 / 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 correctly pairs a 'what' with an explicit 'Use when' trigger and leverages a distinctive product name, but its actions are abstract and it omits the natural vocabulary (contacts, leads, company lookups) users would actually say.

Suggestions

Replace generic verbs with concrete RocketReach capabilities, e.g. 'Look up contact info, search for professionals, and retrieve company data'.

Add natural trigger synonyms users say, such as 'contacts', 'leads', 'email or phone lookup', and 'company enrichment'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to find contact information or company data on RocketReach'.

Dimension	Reasoning	Score
Specificity	The description names the RocketReach domain but the actions ('Manage data, records, and automate workflows') are generic abstractions rather than concrete operations like looking up contacts or company profiles.	2 / 5
Completeness	Both a 'what' (RocketReach integration managing data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with RocketReach data') are present, though the 'when' could name more specific triggers.	4 / 5
Trigger Term Quality	'RocketReach' and 'data'/'records' are relevant keywords, but common user variations such as 'contacts', 'leads', 'company info', 'email lookup', or 'phone number' are missing.	3 / 5
Distinctiveness Conflict Risk	The named RocketReach product gives it a clear niche with minimal conflict risk, though the generic action phrasing leaves minor overlap with other data-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/rocketreach/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.