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

amadeus

Amadeus integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amadeus 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/amadeus/SKILL.md

Quality

Content

67%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 well-structured, actionable guide with concrete Membrane CLI commands and a properly sequenced connection workflow, held back by minor redundancy and a slightly verbose overview section.

Suggestions

Remove the duplicated `membrane action list` command in 'Popular actions' or merge that section into 'Searching for actions'.

Trim or cut the opening paragraph defining what Amadeus is, since Claude already knows this.

Label the 'Searching for actions' section as 'Step 2' (or reword the 'skip to Step 2' references) so the cross-references resolve.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes redundancy (the `membrane action list` command appears in both 'Searching for actions' and 'Popular actions') and an unnecessary introductory paragraph explaining what Amadeus is.	3 / 5
Actionability	Provides concrete, executable bash commands for install, login, connection, action search/run, and proxying, with only minor placeholder gaps (CONNECTION_ID, /path/to/endpoint).	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based validation checkpoints and a poll-again feedback loop, though 'skip to Step 2' references a step that is not explicitly labeled.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no nested references, though the long Amadeus action list is inlined and the file exceeds 50 lines with no external reference split.	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 correctly includes both a 'what' and a 'Use when...' trigger clause and leverages a distinctive brand name, but its action language is generic and it omits the concrete travel-domain triggers (flights, hotels, bookings) that users would naturally say.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Amadeus capabilities such as 'Search and book flights, hotels, transfers, and car rentals'.

Expand the trigger clause with natural user phrases, e.g. 'Use when the user wants to search flights, book hotels, or query Amadeus travel data'.

Add file-extension or product-style synonyms (flight offers, hotel offers, bookings) to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Amadeus) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and high-level rather than concrete capabilities like flight search or hotel booking.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Amadeus data') are present, but the 'when' clause is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes the natural keyword 'Amadeus' and 'Amadeus data', but misses the common variations and synonyms a user would actually say (flights, hotels, bookings, travel, transfers).	3 / 5
Distinctiveness Conflict Risk	The 'Amadeus' name carves a clear, distinctive niche with minimal conflict risk, though the surrounding action language ('manage data, records') is generic enough to leave minor overlap risk.	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/amadeus/SKILL.md
Commit: f484c82

Reviewed: 3 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.