Name: booqable
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

booqable

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

Quality

64%

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/booqable/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 with concrete executable commands and a clear connection workflow, and it is mostly concise. Its main gaps are the lack of validation steps around destructive order operations and reference-grade tables that could move to a separate file.

Suggestions

Add a verification checkpoint before/after destructive actions (archive-order, cancel-order), e.g. confirm the order state or run a get-order to verify the result.

Move the large popular-actions table and proxy flag reference into a separate reference file and link to it from the body.

Fix the broken step cross-references ('skip to Step 2' with no Step 2; '1b' with no '1a') so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste commands and tables, with only minor over-explanation (the app intro line and a few redundant reminders) that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands across install, auth, connection, action search/run, and proxy, with flag tables and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state checks, but destructive operations (archive-order, cancel-order) lack verification checkpoints, capping workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Well-organized sections and clear headers give good navigation, but reference-grade material (the 20-row actions table, proxy flag table) is inlined rather than split into a one-level-deep reference file.	4 / 5
	Total	16 / 20 Passed

Description

52%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 the target app and includes an explicit usage trigger, making it distinct, but the capability list is generic ('manage data, records, automate workflows') rather than concrete. Tightening the 'what' with specific Booqable operations would lift specificity and completeness.

Suggestions

Replace generic actions with concrete Booqable operations, e.g. 'Create and manage orders, reservations, products, and customers'.

Expand the trigger with natural variations users might say, e.g. 'Use when the user wants to manage Booqable rentals, orders, or inventory'.

Keep the explicit 'Use when...' clause and pair it with a sharper 'what' so both halves are concrete.

Dimension	Reasoning	Score
Specificity	Names the domain (Booqable) but the stated actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete operations.	2 / 5
Completeness	Both a 'what' and an explicit 'Use when...' trigger are present, but the 'what' is vague and the 'when' is generic, leaving it short of the concrete both-answers level.	3 / 5
Trigger Term Quality	Includes the genuine natural keyword 'Booqable' a user would say, but offers few variations or synonyms beyond the product name and generic 'data'.	3 / 5
Distinctiveness Conflict Risk	The named product 'Booqable' gives a clear niche with a distinct trigger and minimal risk of firing for unrelated skills.	5 / 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/booqable/SKILL.md
Commit: f484c82

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