Name: mews
Rating: 64.8 (1 reviews)
Author: membranedev

mews

Mews integration. Manage Customers, Spaces, Products, Rates, Reservations, Payments and more. Use when the user wants to interact with Mews data.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/mews/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 copy-paste CLI commands and a well-structured connection workflow, and it is reasonably concise. The main gap is the absence of validation/verification checkpoints around state-changing actions (payments, reservations), which caps workflow clarity.

Suggestions

Add explicit verification after running actions or proxy requests (e.g., re-query the resource to confirm the change took effect, or check the response error/status fields before proceeding).

Number the end-to-end workflow as an explicit sequence (1. install → 2. authenticate → 3. ensure connection → 4. discover actions → 5. run/verify) so the flow is unambiguous.

Trim the introductory PMS explanation and "Use action names and parameters as needed." to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-focused with a clean options table, matching the anchor for efficient content with minor trimmable over-explanation. It is not a 5 because the intro PMS paragraph ("Mews is a property management system...") and filler like "Use action names and parameters as needed." could be trimmed, and not a 3 because the bulk is lean and actionable.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for the common cases (install, login, connection ensure, polling, action list/run with --input, request proxy) plus a complete flag table, matching the anchor for fully executable guidance. It is not a 4 because the examples are concrete and cover the standard workflow rather than having notable gaps.	5 / 5
Workflow Clarity	A sequence is present with good state-based branching for connections (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling, but the top-level steps are implied rather than crisply numbered and the action-execution half has no verification checkpoints. Because operations touch Payments and Reservations (potentially state-changing) with no validation/feedback loop, the destructive-operation cap holds it at 3.	3 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no deep or nested references, matching the anchor for good structure with minor organization gaps. It is not a 5 because the file exceeds 50 lines so the simple-skill exception does not apply, though no bundle files are present to evaluate further splitting.	4 / 5
	Total	16 / 20 Passed

Description

78%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 strong: it names the niche domain, lists concrete capability areas, and provides an explicit "Use when" trigger. Main weakness is the generic "when" phrasing and reliance on a single repeated verb ("Manage") rather than varied concrete actions.

Suggestions

Vary the action verbs beyond "Manage" to show concrete distinct actions (e.g., "Create and update reservations, process payments, search availability").

Sharpen the "Use when" clause with concrete triggers, e.g., "Use when the user wants to manage hotel reservations, guest check-ins, payments, or availability in Mews."

Drop "and more" or replace it with one or two more specific entities to avoid vague padding.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("Manage Customers, Spaces, Products, Rates, Reservations, Payments and more"), matching the anchor for several specific actions with minor gaps. It is not a 5 because every action collapses to the single verb "Manage" applied to an entity list, lacking action diversity.	4 / 5
Completeness	Explicitly answers both "what" (manage Mews entities) and "when" ("Use when the user wants to interact with Mews data"), matching the anchor where both are present but "when" could be more specific. It is not a 5 because the "when" clause is generic ("interact with Mews data") rather than enumerating concrete triggers.	4 / 5
Trigger Term Quality	Includes the natural term "Mews" plus the explicit trigger phrase "Use when the user wants to interact with Mews data", and entity names (reservations, payments) users would naturally say. It is not a 5 because there are few synonyms or file-extension-style variations, and not a 3 because the trigger phrase is explicit rather than a single bare keyword.	4 / 5
Distinctiveness Conflict Risk	Mews is a specific niche PMS and the trigger term "Mews" is highly distinctive, giving a clear niche with minimal conflict risk. It is not a 4 because there is no meaningful overlap with other skills — only Mews-related requests would match.	5 / 5
	Total	17 / 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/mews/SKILL.md
Commit: f484c82

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