Name: getprospect
Rating: 61.6 (1 reviews)
Author: membranedev

getprospect

GetProspect integration. Manage Persons, Organizations, Leads, Users, Roles, Filters. Use when the user wants to interact with GetProspect 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/getprospect/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 copy-paste CLI commands and a well-structured connect-to-run workflow including state-validation feedback loops. It is held back by minor verbosity and a broken cross-reference ('Step 2'), plus no use of separate reference files for bulk action data.

Suggestions

Trim the marketing intro and filler phrases ('so you can focus on the integration logic', 'This is the fastest way') to tighten conciseness.

Fix the dangling 'skip to Step 2' reference and label steps consistently (e.g. add a 'Step 1' / '1a' or renumber) so the connection workflow is unambiguous.

Consider moving the 20-row Popular actions table and detailed connection-state reference into a references/ file, linked once from the body, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the marketing intro ('helps sales and marketing teams find verified email addresses'), 'so you can focus on the integration logic rather than auth plumbing', and 'This is the fastest way to get a connection' that could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) with a concrete flags table and a 20-row actions reference covering the common cases.	5 / 5
Workflow Clarity	The connect -> poll-state -> search -> run sequence is clear with explicit validation checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states and re-poll feedback loop), but the dangling 'skip to Step 2' reference with no labeled Step 2 (and a '1b' with no '1a') is a minor sequencing gap.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested/deep references, but no bundle files exist and bulk reference material (the 20-row actions table, detailed connection-state handling) is inlined rather than split into separate reference files.	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 states what the skill manages and includes an explicit 'Use when' trigger, anchored to a distinct named product. Its main weakness is a generic trigger phrase that omits the natural task terms users would actually say.

Suggestions

Replace the generic 'interact with GetProspect data' trigger with concrete task phrases users say, e.g. 'Use when the user wants to find verified emails, search B2B leads, or manage GetProspect contacts and companies.'

Swap the single verb 'Manage' for a few concrete actions (e.g. 'search, create, update, and delete') to lift specificity toward 5.

Add common synonyms/file or object terms (leads, prospects, verified emails, companies) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (GetProspect) and lists six concrete resource types ('Persons, Organizations, Leads, Users, Roles, Filters'), giving several specific capabilities, though the single generic verb 'Manage' leaves minor coverage gaps versus a 5.	4 / 5
Completeness	Both a clear 'what' ('Manage Persons, Organizations, Leads, Users, Roles, Filters') and an explicit 'when' ('Use when the user wants to interact with GetProspect data') are present, but the 'when' is generic rather than concrete trigger phrases, so it stops short of 5.	4 / 5
Trigger Term Quality	The keyword 'GetProspect' appears and repeats as 'GetProspect data', but the trigger phrase 'interact with GetProspect data' is generic and misses natural task-level terms users would say (e.g. 'find emails', 'search leads', 'B2B prospecting').	3 / 5
Distinctiveness Conflict Risk	The named product 'GetProspect' in both the what and the trigger gives it a clear niche with product-specific triggers, making conflict with other skills minimal.	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/getprospect/SKILL.md
Commit: f484c82

Reviewed: 1 day 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.