Name: jellyreach
Rating: 59.2 (1 reviews)
Author: membranedev

jellyreach

Jellyreach integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Jellyreach data.

Quality

68%

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/jellyreach/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 well-sequenced connection workflow including validation checkpoints. It loses points to a marketing-flavored intro and minor workflow numbering gaps.

Suggestions

Remove the opening marketing paragraph about what Jellyreach is; Claude only needs the integration mechanics.

Define the referenced 'Step 2' or replace it with a concrete anchor so the connection workflow is self-contained.

Tighten chatty asides like 'so you can focus on the integration logic rather than auth plumbing'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples, but the opening marketing paragraph ('Jellyreach is a sales engagement platform that helps sales teams automate...') and chatty lines like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	Provides copy-paste ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) with concrete flags and a table of named actions covering common cases.	5 / 5
Workflow Clarity	The connection workflow is well sequenced with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, but 'Step 2' is referenced but never defined and the '1b' numbering is inconsistent.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with inline tables that fit a single integration skill; no bundle files exist, and at ~180 lines some reference material could optionally be split out.	4 / 5
	Total	16 / 20 Passed

Description

62%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 states both what the skill does and when to use it, anchored to a distinct named product. It is held back by a single generic verb and limited trigger-term variation.

Suggestions

Vary the action verbs beyond 'Manage' (e.g., 'Create, update, and list Organizations, Pipelines, Users') to raise specificity.

Expand the trigger with natural phrases users say, e.g. 'Use when the user wants to manage Jellyreach contacts, campaigns, or outreach sequences.'

Dimension	Reasoning	Score
Specificity	Names the Jellyreach domain and several concrete objects ('Organizations, Pipelines, Users, Goals, Filters') but only a single generic verb ('Manage'), so the action variety is limited rather than comprehensive.	3 / 5
Completeness	Both 'what' (Jellyreach integration, manage Organizations/Pipelines/Users/Goals/Filters) and 'when' ('Use when the user wants to interact with Jellyreach data') are present, though the 'when' is somewhat generic.	4 / 5
Trigger Term Quality	The trigger relies on the product name 'Jellyreach' and the phrase 'interact with Jellyreach data', which are relevant but lack natural synonyms or variations users might say.	3 / 5
Distinctiveness Conflict Risk	The named product 'Jellyreach' gives it a clear niche with minimal conflict risk, but the generic 'interact with...data' phrasing leaves minor overlap risk with other data skills.	4 / 5
	Total	14 / 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/jellyreach/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.