Name: bookingmood
Rating: 62.4 (1 reviews)
Author: membranedev

bookingmood

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

Quality

74%

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

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 body is highly actionable with executable commands and a useful action catalog, and the connection workflow has good state-handling feedback loops. Main gaps are a broken 'Step 2' navigation label, missing validation guidance for destructive actions, and a large inline reference table that could live in a separate file.

Suggestions

Fix the 'skip to Step 2' reference by explicitly labeling the Searching/Running actions section as Step 2, or remove the dangling reference.

Add a validation checkpoint for destructive operations (e.g. confirm IDs and show the resource before running delete-booking, update-booking, or update-attribute).

Move the full Popular actions table into a reference file (e.g. ACTIONS.md) and keep only the most common examples inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused with tables and code blocks, but contains minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.	4 / 5
Actionability	It provides copy-paste ready, fully-flagged commands for every stage (login, connection ensure, action list, action run, request proxy) plus a concrete action catalog table, covering the common cases executably.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→search→run sequence with explicit state-polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the 'skip to Step 2' reference points to an unlabeled section and destructive actions like delete-booking lack explicit validation checkpoints.	4 / 5
Progressive Disclosure	The single file is well-organized into clear sections with no nested references and an external docs link, but the large Popular actions table is inlined rather than split out, leaving minor organization gaps for a 174-line skill.	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 is well-formed with a proper 'Use when' trigger and a distinct named-product niche, but its capability list is generic ('Manage data, records, automate workflows') rather than concrete. Tightening the action verbs and adding domain synonyms would raise specificity and trigger quality.

Suggestions

Replace generic actions ('Manage data, records, automate workflows') with concrete Bookingmood operations such as 'list and update bookings, manage availability calendars, and create booking details'.

Add natural user synonyms to the trigger clause, e.g. 'Use when the user wants to manage Bookingmood bookings, calendars, availability, or rental products.'

Mention the calendar/availability focus explicitly since that is Bookingmood's distinctive capability.

Dimension	Reasoning	Score
Specificity	The description names the domain (Bookingmood) and a couple of action phrases ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor for naming the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Bookingmood data'), but the what is generic and the when trigger is not highly specific, so it sits above the missing-when anchor but below the fully concrete anchor.	4 / 5
Trigger Term Quality	The primary natural term 'Bookingmood' and 'interact with Bookingmood data' appear, but common variations a user might say (bookings, calendars, rentals, availability) are missing, fitting the anchor for some relevant keywords without common synonyms.	3 / 5
Distinctiveness Conflict Risk	Bookingmood is a named, specific SaaS product with a distinct trigger phrase, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/bookingmood/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.