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

Blog Docs Log in Get started

lodgify

Lodgify integration. Manage Properties, Channels, Users. Use when the user wants to interact with Lodgify 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/lodgify/SKILL.md

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 a strongly actionable CLI integration guide with executable commands, a clear connection-state workflow, and well-organized sections. Its weaknesses are mild marketing-style padding in the intro and a couple of unresolved cross-references ("Step 2") that slightly reduce conciseness and workflow clarity.

Suggestions

Trim the promotional intro paragraph to a one-line factual description of Lodgify and drop filler phrases like "auth plumbing" to improve token efficiency.

Resolve the dangling "Step 2" reference by either numbering the subsequent sections (Step 2: Discover actions) or rewording to "skip to Searching for actions".

Add an explicit validation/check step before destructive proxy requests (e.g., confirm method and path, or dry-run GET first) to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the intro paragraph ("software platform that enables vacation rental owners... streamline operations and increase bookings") and phrases like "auth plumbing" add promotional/explanatory padding Claude does not need, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides copy-paste-ready commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run", "membrane request") plus a concrete flags table, fully covering the common cases with executable guidance.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED) and a poll-again feedback loop after user action, but it references a "Step 2" that is never labeled as such and lacks explicit validation before destructive proxy requests, leaving minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized with clear headers (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no nested references, giving good structure with only minor organization gaps rather than the ideal one-level-deep reference split.	4 / 5
	Total	16 / 20 Passed

Description

73%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 cleanly names a specific integration platform and its core resources with an explicit Use-when clause, making it distinct and reasonably complete. Its main weakness is the generic verb "Manage" and a slightly broad trigger phrase that keep specificity and completeness just below the top anchors.

Suggestions

Replace the generic verb "Manage" with 2-3 concrete actions (e.g., "Create, update, and query Properties, Bookings, and Channels") to raise specificity.

Sharpen the Use-when clause with concrete trigger phrases users would say, e.g., "Use when the user wants to manage Lodgify properties, bookings, guests, or channel connections."

Align the listed resources with the body: the description names "Channels, Users" but the body emphasizes Bookings, Guests, Inquiries, Payments, etc.

Dimension	Reasoning	Score
Specificity	"Manage Properties, Channels, Users" names the domain and several concrete resource objects, but relies on a single generic action verb ("Manage") rather than enumerating distinct actions, matching the anchor that names domain and 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	It states both what ("Manage Properties, Channels, Users") and an explicit when ("Use when the user wants to interact with Lodgify data"), but the trigger clause is somewhat generic compared to the concrete multi-trigger anchor at 5, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	"Lodgify" is repeated as the core trigger alongside entity names (Properties, Channels, Users) and the natural phrase "interact with Lodgify data", giving good keyword coverage with only minor synonyms missing, fitting just above the midpoint anchor.	4 / 5
Distinctiveness Conflict Risk	"Lodgify integration" targets a single named SaaS platform with distinct triggers, creating a clear niche with minimal overlap risk against other skills, matching the top anchor.	5 / 5
	Total	16 / 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/lodgify/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.