Name: pci-booking
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

pci-booking

PCI Booking integration. Manage data, records, and automate workflows. Use when the user wants to interact with PCI Booking data.

Quality

66%

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

Quality

Content

76%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 and reasonably concise, dominated by executable CLI examples and a clear connection-state workflow. Its main gaps are missing verification checkpoints around destructive action/proxy operations and inconsistent step numbering.

Suggestions

Add a verification checkpoint after running actions or proxy requests (e.g. inspect the `output` field, check the HTTP status, or confirm the resource state) so destructive operations have a feedback loop.

Fix the step numbering — the text references "Step 2" but no Step 1/Step 2 are labeled; either number the workflow explicitly or drop the cross-reference.

Trim mild fluff ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") to tighten conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-and-flag examples with brief explanations; only minor padding ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") could be trimmed, fitting the efficient score-4 anchor better than the tighter score-5 or the padded score-3.	4 / 5
Actionability	It provides copy-paste-ready executable commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a concrete flags table — fully executable guidance covering the common cases per the score-5 anchor.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with state-handling feedback, but action execution and proxy requests (which include destructive PUT/PATCH/DELETE) lack any validation or verification checkpoint, and "skip to Step 2" references a step that is never labeled — capping at 3 per the destructive-operation guidance.	3 / 5
Progressive Disclosure	Content is well-organized into clear headed sections with one external doc link and no nested/broken references, but at ~140 lines with no bundle files, some inline material (the proxy flags table, detailed clientAction sub-bullets) could be split out, keeping it below 5.	4 / 5
	Total	16 / 20 Passed

Description

57%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 pairs a what-and-when structure and names a distinct product, but its capability verbs are generic and its trigger vocabulary is limited to the product name. Tightening the action list to concrete PCI Booking operations would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete PCI Booking capabilities, e.g. "store and tokenize credit cards, manage reservations, process payments, and generate PCI compliance reports".

Broaden trigger terms to natural user phrasing such as "credit card vault", "PCI DSS compliance", "payment tokenization", or "hospitality payments".

Make the "when" clause enumerate concrete scenarios (e.g. "Use when storing card data, tokenizing payments, or handling PCI DSS compliance for hospitality bookings").

Dimension	Reasoning	Score
Specificity	It names the domain ("PCI Booking") but the actions — "Manage data, records, and automate workflows" — are generic verbs rather than concrete capabilities, matching the score-2 anchor better than the concrete-action score-3 anchor.	2 / 5
Completeness	It has both a "what" ("PCI Booking integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with PCI Booking data."), but the "what" is generic and the trigger phrase set is thin, so it falls short of the score-5 anchor.	4 / 5
Trigger Term Quality	The only natural keyword is the product name "PCI Booking", repeated in "interact with PCI Booking data"; relevant but missing natural variations a user might say (credit card, payment, PCI compliance, hospitality).	3 / 5
Distinctiveness Conflict Risk	"PCI Booking" is a specific named niche product with distinct triggers and minimal conflict risk, but the generic verbs "Manage data, records, and automate workflows" could overlap with CRM/database skills, keeping it below 5.	4 / 5
	Total	13 / 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/pci-booking/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.