CtrlK
BlogDocsLog inGet started
Tessl Logo

wubook-ratechecker

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/wubook-ratechecker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 CLI commands and a solid connection-readiness workflow including error recovery, but it carries moderate padding and inconsistent step numbering, and keeps reference-grade detail inline. Trimming fluff and labeling steps would improve it.

Suggestions

Remove filler sentences such as 'so you can focus on the integration logic rather than auth plumbing' and the 'burn less tokens' justification in Best practices to tighten token use.

Replace the loose 'Step 2' / '1b' references with explicit numbered steps (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run) so the sequence is unambiguous.

Consider moving the connection state-machine breakdown and the request flags table into a separate reference file referenced from the body, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but includes padded phrasing like 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens and make communication more secure' that could be trimmed without losing clarity.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands (install, login, connection ensure, action list/run, request proxy) plus a complete flags table and JSON-input examples covering the common cases.

5 / 5

Workflow Clarity

The connect-to-poll-to-run sequence is clear and includes a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, retry), but step numbering is inconsistent ('skip to Step 2', '1b' without a labeled Step 1/2), a minor gap.

4 / 5

Progressive Disclosure

The content is well-organized into clearly labeled sections (Overview, Working with, Install, Auth, Connecting, Searching, Proxy, Best practices) with no nesting, though the connection state-machine detail and flags table are inlined rather than split into reference files.

4 / 5

Total

16

/

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-targeted to a distinct named product and includes both a 'what' and a 'when' clause, but its action language is generic and the trigger phrases lack variation. Strengthening the specificity of capabilities and adding concrete trigger synonyms would raise the score.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete RateChecker operations such as 'compare competitor rates, monitor rate plans across date ranges, and review saved rate checks'.

Broaden the 'Use when' trigger with natural phrasings users would say, e.g. 'Use when the user wants to compare hotel rates, check competitor pricing, or review saved rate checks in WuBook RateChecker.'

DimensionReasoningScore

Specificity

It names the domain (WuBook RateChecker) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete API operations, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with WuBook RateChecker data'), but the trigger could be more specific with multiple concrete phrases.

4 / 5

Trigger Term Quality

The natural keyword 'WuBook RateChecker' is present and well-targeted, but the surrounding terms ('data', 'records', 'workflows') are generic and lack synonyms or variations users might actually say.

3 / 5

Distinctiveness Conflict Risk

'WuBook RateChecker integration' carves out a clear, named-product niche with a distinct trigger that is unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

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.