Name: getswift
Rating: 56.8 (1 reviews)
Author: membranedev

getswift

Getswift integration. Manage Organizations, Projects, Users, Goals, Filters. Use when the user wants to interact with Getswift data.

Quality

65%

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/getswift/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 a lean, actionable CLI integration guide with concrete commands and sensible sectioning. Its main weakness is workflow clarity: external/destructive operations (running actions, proxy POST/DELETE) proceed without explicit validation checkpoints, so errors would not be caught early.

Suggestions

Add an explicit validation checkpoint after connecting (e.g., run `membrane connection list --json` and confirm the new connectionId appears) and before running actions, with a fix-and-retry loop on failure.

Show one complete real invocation of a popular action (e.g., `create-task` with actual pickup/dropoff parameters) instead of only a generic --input placeholder.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — tables and copy-paste command blocks carry the weight — with only minor over-explanation such as the opening product backstory and the 'so you can focus on the integration logic rather than auth plumbing' flourish that could be trimmed.	4 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connect, action list/run, request) plus flag and popular-action tables, but it stops short of a complete real-parameter invocation of a named popular action — the --input example uses generic {"key":"value"} — leaving a minor gap versus fully copy-paste-ready coverage.	4 / 5
Workflow Clarity	The install → login → connect → discover → run/proxy sequence is clearly laid out, but validation is only implicit (e.g., 'note its connectionId', 'return action objects with id and inputSchema') with no explicit verify checkpoint before running actions or proxy requests that perform external/destructive operations, capping it at 3 per the destructive-operations guidance.	3 / 5
Progressive Disclosure	As a self-contained single-file guide with no bundle files, it is well organized into clear sections (Overview, Working with Getswift, Popular actions, Best practices) with easy navigation; not a 5 only because the popular-actions and proxy-flag references are inlined where a separate reference file could further sharpen the overview.	4 / 5
	Total	15 / 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 cleanly states what the integration manages and gives an explicit trigger, but it relies on one generic verb ("Manage") and a single generic "interact with Getswift data" trigger rather than varied, natural trigger phrases. It is solid and distinct but not comprehensive.

Suggestions

Replace the single generic verb 'Manage' with a few concrete actions per entity (e.g., 'Create and list Organizations, invite Users, set Goals, apply Filters') to lift specificity.

Expand the 'Use when' clause with concrete, natural trigger phrases users would actually say (e.g., 'Use when the user wants to book Getswift deliveries, list drivers, or track tasks').

Dimension	Reasoning	Score
Specificity	The description names the domain and five concrete entities ("Organizations, Projects, Users, Goals, Filters") but applies only a single generic verb ("Manage"), so it lists several objects without several specific actions — matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor above.	3 / 5
Completeness	It explicitly answers both what ("Getswift integration. Manage Organizations, Projects, Users, Goals, Filters.") and when ("Use when the user wants to interact with Getswift data"), but the 'when' offers a single generic trigger rather than the multiple concrete trigger phrases that define a 5.	4 / 5
Trigger Term Quality	It includes relevant domain terms ("Getswift", "Organizations", "Projects", "Users", "Goals", "Filters") but the trigger phrase "interact with Getswift data" is generic and lacks the natural variations or synonyms that would push it to 4.	3 / 5
Distinctiveness Conflict Risk	Binding the skill to the unique product name "Getswift" makes it mostly distinct with only minor overlap risk against sibling Membrane logistics integrations that share the templated "interact with X data" trigger; not a 5 because that shared template weakens distinctiveness.	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/getswift/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.