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

retriever

Retriever integration. Manage Organizations, Leads, Projects, Pipelines, Users, Filters. Use when the user wants to interact with Retriever 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/retriever/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 concrete, executable integration guide with a well-sequenced connection workflow and state-based checkpoints. Its main weakness is token efficiency: generic overview prose, a vacant "When to use which actions" line, and a duplicated action-list command inflate the body without adding guidance.

Suggestions

Delete the generic overview paragraph ("Retriever is a search and discovery platform...") and the empty "When to use which actions" line; Claude can infer what Retriever is.

Merge the duplicated action-discovery command from "Searching for actions" and "Popular actions" into a single section to remove redundancy.

Define or remove the undefined "Step 2" reference and renumber the "1b. Wait for the connection to be ready" subsection so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but it carries removable filler — the generic overview paragraph ("Retriever is a search and discovery platform..."), the empty "When to use which actions: Use action names and parameters as needed" line, and a duplicated action-list command across "Searching for actions" and "Popular actions."	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list, action run, and proxy requests, plus a flags table; minor gaps remain where placeholders (CONNECTION_ID, QUERY intent, actionId) are left abstract.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but "Step 2" is referenced and never defined and the "1b" numbering is awkward.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections with no nested external references and no bundle files to misplace; the proxy flags table is reasonably inline, though the skill is longer than a minimal single-purpose skill.	4 / 5
	Total	15 / 20 Passed

Description

70%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 is clear and trigger-aware, naming a specific platform and concrete resources with an explicit "Use when" clause. Its main weakness is the single generic verb "Manage," which blurs the specific actions available per resource.

Suggestions

Replace the single verb "Manage" with specific verbs per resource (e.g., "Create and list Organizations, enrich Leads, trigger Pipelines") so the concrete actions are visible.

Expand the "Use when" clause with a few concrete trigger phrases users would actually say (e.g., "when the user wants to search Retriever, enrich leads, or manage pipeline stages").

Dimension	Reasoning	Score
Specificity	Names the Retriever domain and lists concrete resources ("Organizations, Leads, Projects, Pipelines, Users, Filters"), but the single generic verb "Manage" covers all of them, so the specific actions per resource are not enumerated.	3 / 5
Completeness	It answers "what" (Retriever integration; manage the listed resources) and "when" with an explicit "Use when..." clause, but the trigger is one general scenario rather than multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Retriever data" plus the entity names (Organizations, Leads, Projects, Pipelines, Users, Filters) give good natural-term coverage; a few synonymous phrasings users might say are missing.	4 / 5
Distinctiveness Conflict Risk	"Retriever integration" names a specific platform with a clear niche, and the resource list is tied to it; minor overlap risk remains with generic CRM/sales skills that also manage Leads, Projects, and Pipelines.	4 / 5
	Total	15 / 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/retriever/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.