Name: flexport
Rating: 58.4 (1 reviews)
Author: membranedev

flexport

Flexport integration. Manage data, records, and automate workflows. Use when the user wants to interact with Flexport 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/flexport/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 content is highly actionable with copy-paste Membrane CLI commands and a solid connection-readiness workflow including error feedback. Its main weaknesses are padding (Flexport background, marketing phrases) and a loose 'Step 2' reference that breaks the otherwise clear sequence.

Suggestions

Trim the Flexport company background paragraph and marketing phrasing ('burn less tokens', 'focus on the integration logic') to assume Claude's competence.

Replace the dangling 'skip to Step 2' reference with explicit numbered steps (Step 1 connect, Step 2 search/run) or rename the '1b' header to 'Step 1b'.

Add a brief validation/check before running actions or proxy requests (e.g., confirm connection state is READY and actionId resolved) to close the workflow validation gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-focused, but includes unnecessary Flexport background ('Flexport is a platform for global trade...') and marketing phrasing ('burn less tokens', 'focus on the integration logic rather than auth plumbing') that could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end (install, login, connection ensure, action list/run, request) alongside a concrete proxy flags table, matching 'fully executable; copy-paste ready'.	5 / 5
Workflow Clarity	A clear connect->search->run sequence exists with state-polling validation and a CLIENT_ACTION_REQUIRED feedback loop, but 'skip to Step 2' references a non-existent numbered step and there is no validation checkpoint before running actions.	4 / 5
Progressive Disclosure	The single file is well-sectioned with clear headers and easy navigation, and no bundle files exist to split into; it is over 50 lines so the simple-skill 5-anchor does not apply, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

61%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 establishes a distinct Flexport niche with an explicit use-when trigger, but its capability list relies on generic verbs (manage, automate) rather than concrete Flexport operations. Tightening the 'what' with specific actions and broadening the trigger phrases would raise it.

Suggestions

Replace generic verbs with concrete Flexport operations (e.g., 'Search shipments, list tasks, retrieve shipment updates, and look up users').

Broaden the 'Use when' clause to cover records and workflows, not only 'interact with Flexport data'.

Add natural trigger variations users might say (e.g., 'shipments', 'tracking', 'Flexport API').

Dimension	Reasoning	Score
Specificity	Names the Flexport domain but the listed actions ('Manage data, records, and automate workflows') are generic abstractions rather than concrete operations, fitting the 'names domain but actions minimal/generic' anchor.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Flexport data') are present, though the 'what' is vague and the 'when' is narrow rather than comprehensive.	4 / 5
Trigger Term Quality	The key brand term 'Flexport' plus 'data, records, workflows' are present and natural, but there are no synonyms or common variations, matching 'some relevant keywords but missing variations'.	3 / 5
Distinctiveness Conflict Risk	'Flexport integration' names a distinct, brand-specific niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 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/flexport/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.