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

expedy

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

Quality

67%

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

Quality

Content

68%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 copy-paste Membrane CLI commands and a strong connection state-machine workflow, but it is let down by unnecessary introductory prose and missing validation around destructive device/proxy operations. Tightening the intro and adding confirmation checkpoints would lift the weaker dimensions.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g., "Before running shutdown-device or reboot-device, confirm the target device id with the user").

Trim the Expedy intro paragraph and the "so you can focus on the integration logic rather than auth plumbing" aside; assume Claude understands SaaS and auth plumbing.

Fix the dangling "skip to Step 2" / "1b" references by labeling the workflow steps explicitly (Step 1: ensure connection, Step 2: search and run actions).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but the opening paragraph explaining what Expedy is and prose like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be tightened, matching score 3.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across install, login, connection ensure, action list/run, and proxy, plus a flags table and a popular-actions table covering the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	The connection state-machine has clear polling and a feedback loop, but destructive operations (shutdown/reboot device, proxy DELETE/PUT) lack validation checkpoints, triggering the destructive-ops cap at 3; a dangling "Step 2" reference also leaves the sequence implicit.	3 / 5
Progressive Disclosure	No bundle files exist, but the body is well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with appropriately sized inline tables; minor organization gaps (the dangling Step 2 reference) keep it at 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly identifies a distinct product niche and includes an explicit Use-when trigger, but its action verb is generic and its trigger phrase coverage is thin. Strengthening it would mean specifying concrete verbs per resource and adding more natural trigger terms.

Suggestions

Replace the generic verb "Manage" with specific actions per resource (e.g., "Create and update Organizations, build Pipelines, invite Users, configure Filters").

Expand the trigger clause with natural phrases a user would say, e.g. "Use when the user wants to manage Expedy organizations, pipelines, users, or expense filters."

Add a concrete trigger tied to the product's purpose, such as "or when working with Expedy expense/travel data."

Dimension	Reasoning	Score
Specificity	Names the Expedy domain and four concrete resources ("Manage Organizations, Pipelines, Users, Filters"), but the single generic verb "Manage" keeps it from listing multiple distinct concrete actions, matching the score-3 anchor.	3 / 5
Completeness	Both the "what" (Expedy integration, manage those resources) and an explicit "Use when the user wants to interact with Expedy data" trigger are present; the when clause is explicit but somewhat generic rather than packing concrete trigger phrases, fitting score 4 over 5.	4 / 5
Trigger Term Quality	"Expedy" and the resource names are relevant keywords, but the only natural user phrase is "interact with Expedy data"; common variations or synonyms are missing, aligning with the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	"Expedy" is a unique named SaaS product giving it a clear niche with distinct triggers and minimal conflict risk, matching the score-5 anchor.	5 / 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/expedy/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.