Name: pickrr
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pickrr

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

Quality

61%

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

Quality

Content

61%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 actionable and well-structured with concrete Membrane CLI commands and a clear connection workflow, but it is padded with redundant sections and lacks verification checkpoints for destructive operations like proxy DELETE.

Suggestions

Consolidate the duplicate action-list sections ("Searching for actions" and "Popular actions") into one and trim the introductory paragraph about what Pickrr is.

Add a validation/verification checkpoint after destructive calls, e.g. re-fetch the resource or run a GET via `membrane request` to confirm a DELETE/PUT took effect.

Fix the broken "skip to Step 2" reference by labeling the action-execution section as Step 2 or rewording to a relative pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but redundant action-list sections ("Searching for actions" and "Popular actions" both show `membrane action list`), an explanatory intro paragraph about what Pickrr is, and prose like "This is the fastest way to get a connection" add noticeable padding.	3 / 5
Actionability	It provides copy-paste-ready commands (`npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action run`, `membrane request`) plus a flags table, with only minor gaps (CONNECTION_ID placeholders and a trivial action-run example).	4 / 5
Workflow Clarity	The connection flow has a state-based feedback loop (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but destructive-capable operations (proxy `-X DELETE`, `action run`) lack verification checkpoints, and "skip to Step 2" references a step that is never labeled — the destructive/batch cap holds this at 3.	3 / 5
Progressive Disclosure	The body is well-organized with clear section headers and no external bundle references, with content appropriately inline; it is not a 5 because there are no one-level-deep references and the single file is somewhat long.	4 / 5
	Total	14 / 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 answers both what and when and is anchored by a distinctive brand name, but its action verbs are generic and it lacks domain synonyms (shipping, logistics, orders) that users would naturally say.

Suggestions

Replace generic verbs with concrete Pickrr actions, e.g. "Create and track shipments, manage orders and manifests, fetch courier manifests and invoices".

Add natural trigger terms users actually say: "shipping", "logistics", "courier", "fulfillment", "track shipment/order".

Tighten the "when" clause with concrete triggers, e.g. "Use when the user wants to ship orders, track shipments, or query Pickrr logistics data."

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the Pickrr domain plus a few actions, but the actions are generic rather than concrete/comprehensive, matching the anchor for naming the domain with 1-2 actions; not a 4 because the actions lack specificity.	3 / 5
Completeness	It states both a clear "what" ("Pickrr integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Pickrr data."), but the trigger is generic rather than concrete phrases, so it is not a 5.	4 / 5
Trigger Term Quality	The description surfaces the natural brand keyword "Pickrr" / "Pickrr data" but omits common domain synonyms (shipping, logistics, orders, fulfillment), so it has some relevant keywords while missing common variations.	3 / 5
Distinctiveness Conflict Risk	The "Pickrr" brand gives a clear niche with minimal conflict risk, but the surrounding wording ("manage data, records") is generic enough to allow minor overlap with related data-management skills, placing it just below a 5.	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/pickrr/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.