CtrlK
BlogDocsLog inGet started
Tessl Logo

hostaway

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

57

Quality

66%

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/hostaway/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 highly actionable with a well-sequenced connection workflow and clear state handling, but it is modestly verbose and lacks an explicit validation step before destructive action runs. Fixing the broken step references and trimming filler would lift the lower dimensions.

Suggestions

Add an explicit validation/verification step before running write or destructive actions (e.g., dry-run the action or confirm the target record before executing).

Fix the dangling cross-references: either add a labeled "Step 1"/"Step 2" or replace "skip to Step 2" and "1b" with stable section links.

Trim filler phrases such as "so you can focus on the integration logic rather than auth plumbing" and "burn less tokens" to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient command documentation, but it carries several padded asides ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", "burn less tokens") that could be trimmed without losing clarity.

3 / 5

Actionability

It provides copy-paste-ready commands across the full flow (install, login, connection ensure/get, action list/run, proxy) plus a flags table, but relies on unsubstituted placeholders (CONNECTION_ID, <actionId>) and includes no worked end-to-end example with real values, leaving minor gaps.

4 / 5

Workflow Clarity

The connection setup is a clear sequence with a state machine and feedback loops (poll BUILDING, act on CLIENT_ACTION_REQUIRED, re-poll, handle CONFIGURATION_ERROR), but running actions on live Hostaway data lacks an explicit validation/verification step for potentially destructive operations.

4 / 5

Progressive Disclosure

No bundle files exist, but the single SKILL.md is organized into clear topical sections; minor navigation gaps (a "skip to Step 2" with no Step 2, and a "1b" with no "1a") keep it just below fully clean navigation.

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 is distinctive and answers both what and when, but its action language is generic and its trigger vocabulary is limited to the product name alone. Tightening the verbs and adding common phrasing variations would raise it.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Hostaway actions such as "create and update reservations, sync listings, and send guest messages".

Expand trigger terms beyond the product name to natural variations users say, e.g. "Use when the user mentions Hostaway, vacation rental bookings, guest messages, or listing management".

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Hostaway domain plus a few actions, but "manage data/records" is generic verb phrasing rather than a list of specific concrete actions, matching the anchor for domain + 1-2 concrete actions that is not comprehensive.

3 / 5

Completeness

It states a clear "what" ("Manage data, records, and automate workflows") and an explicit "Use when" clause ("Use when the user wants to interact with Hostaway data"), but the "when" trigger is slightly generic, so it sits just below the level that requires concrete trigger phrases.

4 / 5

Trigger Term Quality

The natural trigger keyword is essentially just "Hostaway" / "Hostaway data" — one relevant term with no synonyms, file extensions, or common variations, so it lands at "some relevant keywords but missing common variations" rather than good multi-keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"Hostaway" is a uniquely named platform, giving the skill a clear niche with a distinct trigger and minimal risk of firing for an unrelated skill.

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.