Name: protel
Rating: 64 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

protel

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

Quality

76%

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/protel/SKILL.md

Quality

Content

82%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 highly actionable, well-structured integration guide anchored in concrete CLI commands and a solid connection-readiness workflow. Its weaknesses are minor: some padded prose, inconsistent step numbering, and a dense inline reference section that could be split out.

Suggestions

Fix the step numbering (label 'Step 1: Connect' and 'Step 2: Search/Run actions') so the 'skip to Step 2' references resolve.

Add a brief validation checkpoint after running actions or proxy requests (e.g. check the `output`/response status before reporting success), especially for destructive HTTP methods.

Verify the 'Official docs' link — it points to altium.com (PCB design tool), which conflicts with the hotel-PMS framing in the intro; correct it to Protel's documentation.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, with only minor padded prose such as 'so you can focus on the integration logic rather than auth plumbing'; the clientAction state reference is detailed but justified reference content rather than over-explanation of concepts Claude already knows.	4 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (install, login, connection ensure, action list/run, request) plus a concrete flags table for proxy requests, covering the common cases fully.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-for-ready → search → run sequence with feedback loops for connection state (poll, act on CLIENT_ACTION_REQUIRED, re-poll), but step numbering is inconsistent ('skip to Step 2' with no labeled Step 1/2) and running/destructive actions lack an explicit result-validation checkpoint.	4 / 5
Progressive Disclosure	The single self-contained file is well-organized into clearly headed sections with no nested external references; the dense clientAction state reference is arguably inline material that could live in a separate file, keeping it just short of a 5.	4 / 5
	Total	17 / 20 Passed

Description

70%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 successfully pairs a 'what' with an explicit 'Use when' trigger and anchors on a distinct named product. Its main weakness is generic, non-concrete action verbs that limit specificity and completeness from reaching the top of the scale.

Suggestions

Replace generic verbs with concrete Protel actions the integration actually performs (e.g. 'look up reservations, sync guest records, post charges, pull folio data').

Expand the 'Use when' trigger with concrete phrases users say (e.g. 'Use when the user wants to query reservations, manage guest profiles, or post charges in Protel').

Add common surface terms users mention (e.g. reservations, folios, check-in/check-out) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the Protel domain and several capability areas ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete (e.g. no 'extract', 'fill', 'merge'-style verbs), landing between the 'minimal/generic' and 'concrete actions' anchors.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Protel data'), but the 'what' actions are generic and the trigger is singular rather than the multi-trigger concrete phrases of a 5.	4 / 5
Trigger Term Quality	Includes the natural product name 'Protel' and the phrase 'interact with Protel data' that a user would actually say; coverage is good though it lacks synonyms, which largely don't exist for a proper-noun product.	4 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific named product 'Protel' gives it a clear niche with minimal conflict risk, but the generic action verbs ('manage data', 'automate workflows') create minor overlap with other integration skills when a user omits the product name.	4 / 5
	Total	15 / 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/protel/SKILL.md
Commit: f484c82

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