Name: easypost
Rating: 62.4 (1 reviews)
Author: membranedev

easypost

EasyPost integration. Manage Shipments, Addresses, CarrierAccounts, Batchs, Reports, Refunds and more. Use when the user wants to interact with EasyPost data.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/easypost/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.

A well-structured, actionable CLI-wrapper skill with concrete commands and a state-driven connection workflow including feedback loops. The main gaps are minor: a dangling Step 2 reference, no worked action-run example, and inlined reference material with no deeper file references.

Suggestions

Fix the dangling "skip to Step 2" navigation by labeling the next section explicitly as Step 2 (Searching for actions) or rewording to "skip to Searching for actions."

Add one fully-worked `membrane action run` example with realistic input (e.g., buying a shipment with a selected rate) so the run path is copy-paste ready end-to-end.

Consider moving the popular-actions catalog and proxy flag reference into a separate reference file and linking it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and little explanation of concepts Claude already knows, but has minor trimmable padding such as "so you can focus on the integration logic rather than auth plumbing" and "This will burn less tokens."	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests plus a flags table and action catalog, with the minor gap that no fully-worked `membrane action run` example shows real input values end-to-end.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with a state-based polling feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-poll after user action), but the dangling "skip to Step 2" reference (no labeled Step 2) and the absence of action-result verification are minor validation gaps.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections and avoids nested references, but there are no external reference files at all and reference-style content (the popular actions table, proxy flags) is inlined rather than split out, which is a minor organization gap for a ~165-line skill.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

A solid, third-person description that names EasyPost and many of its resources with an explicit Use-when clause. Its main weakness is the single generic action verb and a vague trigger that could be more concrete.

Suggestions

Replace the single generic verb "Manage" with several distinct concrete actions (e.g., "Create and buy shipments, verify addresses, track packages, request refunds").

Expand the Use-when clause with concrete trigger phrases users would actually say, such as "Use when the user wants to create shipments, buy labels, track packages, or verify addresses via EasyPost."

Add commonly used natural terms missing from the description (shipping labels, tracking, parcels, carriers) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists many concrete resources ("Shipments, Addresses, CarrierAccounts, Batchs, Reports, Refunds") but only one generic action verb ("Manage ... and more"), so it names the domain and entities comprehensively without distinct concrete actions.	3 / 5
Completeness	It has both a "what" ("EasyPost integration. Manage ...") and an explicit "Use when the user wants to interact with EasyPost data" clause, but the when-trigger is generic rather than concrete phrases like create shipments or buy labels.	4 / 5
Trigger Term Quality	"EasyPost" plus the named entity types give good keyword coverage a user would naturally say, but common natural terms like shipping labels, tracking, and parcels (present in the body) are missing from the description.	4 / 5
Distinctiveness Conflict Risk	"EasyPost" is a specific named service with a clear niche and distinct trigger ("interact with EasyPost data"), giving minimal overlap risk with other skills.	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/easypost/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.