CtrlK
BlogDocsLog inGet started
Tessl Logo

bookboost-guest-messaging

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

58

Quality

67%

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/bookboost-guest-messaging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 concrete, copy-paste-ready Membrane commands and a well-organized section structure. Its weaknesses are a verbose marketing intro, a broken step cross-reference, and missing validation before destructive action execution.

Suggestions

Trim the marketing intro paragraph and the "burn less tokens"/agent-types filler so the file leads with actionable setup steps.

Fix the dangling "skip to Step 2" reference by labeling the downstream section as Step 2 or removing the cross-reference.

Add a validation/dry-run checkpoint before running actions that send messages or modify records (e.g. inspect outputSchema first, or run with a test input) and a re-check loop after execution.

DimensionReasoningScore

Conciseness

The body is mostly command-focused and efficient, but it opens with a marketing-style product explanation ("Bookboost Guest Messaging is a platform for hotels and vacation rentals...") and includes filler such as "This will burn less tokens" and an incomplete sentence about agent types, fitting the mostly-efficient-but-could-be-tightened anchor.

3 / 5

Actionability

It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) plus a complete proxy flag table, fully covering the common cases with executable guidance.

5 / 5

Workflow Clarity

The connection flow has good state-based feedback loops, but the "skip to Step 2" reference is dangling (no Step 2 is labeled), and running potentially destructive actions (e.g. sending guest messages) lacks any validation or dry-run step, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The skill is a single well-sectioned file with clear headers and no nested references, but at ~138 lines everything is inline with no external reference split, matching the good-structure-with-minor-organization-gaps anchor.

4 / 5

Total

15

/

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 clearly identifies a distinctive niche and includes an explicit Use-when clause, but its action list is generic and it lacks natural synonym trigger terms for the sub-features. It is solid but leaves room for more concrete, varied triggers.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Send and schedule guest messages, manage conversation templates, and trigger AI tasks" instead of "Manage data, records, and automate workflows".

Add natural trigger synonyms users would say, such as "guest messages", "conversations", "templates", and "AI tasks", to the Use-when clause.

Broaden the Use-when clause to cover multiple trigger scenarios (e.g. messaging guests, building templates, automating workflows) rather than a single "interact with data" trigger.

DimensionReasoningScore

Specificity

The description names the domain and 2-3 actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, fitting the anchor that lists domain plus a few non-comprehensive actions.

3 / 5

Completeness

Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Bookboost Guest Messaging data") are present with an explicit Use-when clause, though the trigger is single and could be more specific.

4 / 5

Trigger Term Quality

The product name "Bookboost Guest Messaging" is a strong keyword, but common synonyms users would say (messages, conversations, templates, automations) are absent, matching the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

The specific product name "Bookboost Guest Messaging" carves out a clear niche with a distinct trigger and minimal conflict risk with other skills.

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.