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

travelport

Travelport integration. Manage data, records, and automate workflows. Use when the user wants to interact with Travelport 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/travelport/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 body is highly actionable with copy-paste-ready CLI commands and a well-structured connection workflow including retry logic, but it carries some avoidable background explanation and inconsistent step numbering. Splitting detailed reference material into separate files and fixing the step labels would further improve it.

Suggestions

Tighten or remove the opening overview paragraph and redundant auth-mode prose that restates concepts Claude already knows.

Fix the workflow step numbering: define 'Step 1/1a' before '1b' and either define or remove the dangling 'Step 2' reference.

Consider moving the clientAction schema details and the proxy flags table into a separate reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening background paragraph ('Travelport is a global distribution system...') and some redundant auth-mode explanation restate concepts Claude largely already knows and could be tightened.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request proxy) plus a concrete flags table, covering the common cases.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with state branching and a poll-retry feedback loop, but the step numbering is inconsistent (a '1b' with no '1a', a referenced 'Step 2' that is never defined), leaving minor gaps.	4 / 5
Progressive Disclosure	Content is well organized into clear sections with no nested references and no bundle files, but material like the detailed clientAction schema and the proxy flags table could plausibly live in a separate reference file for a cleaner overview.	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 correctly names a distinct system and includes an explicit 'Use when' clause, satisfying both 'what' and 'when', but its capability verbs are generic and it lacks natural travel-domain trigger terms. Strengthening it with concrete actions and richer trigger language would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Travelport actions such as 'Search flights, book and cancel reservations, manage passengers and payments'.

Add natural trigger terms users would actually say, e.g. 'Use when the user wants to search flights, make or change travel bookings, or query Travelport/GDS data'.

Optionally note scope limits to further reduce any ambiguity about when the skill applies.

Dimension	Reasoning	Score
Specificity	The description names the Travelport domain but the stated actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete, matching the score-2 anchor.	2 / 5
Completeness	It answers both 'what' (Travelport integration, manage data/records/workflows) and 'when' (explicit 'Use when...' clause), though the 'when' is generic rather than tied to specific trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the relevant term 'Travelport' and an explicit trigger ('Use when the user wants to interact with Travelport data') but misses common natural variations like 'travel booking', 'flights', or 'GDS' that users would say.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Travelport system gives it a clear niche with a distinct trigger ('interact with Travelport data') and minimal overlap risk with other skills.	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/travelport/SKILL.md
Commit: f484c82

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