CtrlK
BlogDocsLog inGet started
Tessl Logo

planyo-online-booking

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

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/planyo-online-booking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is a highly actionable, well-structured CLI integration guide with executable commands and a clear connection workflow including state checkpoints. The main gaps are a dangling "Step 2" reference and minor redundancy/content padding that could be trimmed.

DimensionReasoningScore

Conciseness

The body is largely efficient commands and a useful flags table, with only minor over-explanation such as the opening Planyo overview paragraph and "so you can focus on the integration logic rather than auth plumbing," matching anchor 4's "efficient; minor instances of over-explanation."

4 / 5

Actionability

It provides copy-paste-ready executable commands for every stage (install, login, connection ensure, action list/run, request) with concrete flags and JSON input examples covering the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a feedback loop (re-poll after the user completes the action), but the repeated "skip to Step 2" reference points to no labeled Step 2, a minor validation/navigation gap that keeps it below anchor 5.

4 / 5

Progressive Disclosure

It is a single, well-organized file with clear section headers and no nested references, appropriately structured for its scope; minor redundancy between "Searching for actions" and "Popular actions" (duplicate `action list` command) keeps it just below anchor 5.

4 / 5

Total

17

/

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 answers both what and when with an explicit trigger clause and names a distinct product niche, but its action list and trigger keywords are generic rather than booking-specific. Tightening the wording to mention reservations/appointments would lift specificity and trigger-term quality.

Suggestions

Replace generic actions ("Manage data, records, automate workflows") with booking-specific concrete operations such as creating bookings, managing reservations, and handling availability slots.

Add natural trigger terms users actually say — reservations, appointments, availability, rentals — alongside "Planyo Online Booking".

Make the "when" clause concrete rather than tautological, e.g. "Use when the user wants to create or manage Planyo bookings, reservations, or customer records."

DimensionReasoningScore

Specificity

Names the Planyo domain and lists three actions ("Manage data, records, and automate workflows"), but the actions are generic data-management terms rather than booking-specific concrete operations, so it stops at anchor 3 and does not reach the "several specific actions" bar of 4.

3 / 5

Completeness

It provides an explicit "what" (integration that manages data, records, and workflows) and an explicit "Use when the user wants to interact with Planyo Online Booking data" trigger, satisfying both halves; the "when" is present but tautological and not concrete enough for anchor 5.

4 / 5

Trigger Term Quality

The product name "Planyo Online Booking" and "interact with ... data" provide some relevant keywords, but common natural terms users would say (reservations, appointments, bookings, rentals) are missing, matching anchor 3's "some relevant keywords but missing common variations."

3 / 5

Distinctiveness Conflict Risk

Naming the specific product "Planyo Online Booking" establishes a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.