Name: hotspotsystem
Rating: 55.2 (1 reviews)
Author: membranedev

hotspotsystem

HotspotSystem integration. Manage Organizations, Users, Projects. Use when the user wants to interact with HotspotSystem data.

Quality

63%

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

Quality

Content

63%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 a solid, actionable integration guide with executable CLI commands and a well-sequenced connection workflow. It loses points for an unnecessary introductory overview, a dangling step reference, and a large inline actions table that would benefit from being split into a reference file.

Suggestions

Trim the introductory paragraph explaining what HotspotSystem is and remove soft padding like 'so you can focus on the integration logic rather than auth plumbing'; Claude does not need the platform primer.

Fix the workflow numbering: label 'Step 1a/1b' and 'Step 2' explicitly so the dangling 'Skip to Step 2' and '#### 1b' references resolve to real headings.

Move the 18-row 'Popular actions' table into a separate references file (e.g., ACTIONS.md) and link to it from the body, improving token efficiency and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation Claude does not need, such as the introductory paragraph describing what HotspotSystem is ('cloud-based WiFi management platform... captive portals, billing options, bandwidth management') and soft padding like 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request proxy) with a useful actions table; it sits at 4 rather than 5 because parameter examples use generic placeholders like '{"key": "value"}' with no fully worked real-action example.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop, but numbering is slightly incoherent ('1b' appears with a dangling reference to an unlabeled 'Step 2'), leaving minor validation/structural gaps.	4 / 5
Progressive Disclosure	The single-file skill has reasonable section headers, but the large 18-row 'Popular actions' table is inline reference content that could live in a separate file, and there are no external references or bundle files to provide one-level-deep navigation.	3 / 5
	Total	14 / 20 Passed

Description

62%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 adequate: it states the domain, lists managed entities, and includes an explicit 'Use when' trigger. Its main weaknesses are the single generic verb 'Manage' and a 'when' clause that is generic rather than rich with concrete trigger phrases.

Suggestions

Replace the generic 'Manage Organizations, Users, Projects' with distinct concrete actions (e.g., 'List transactions, issue vouchers, manage hotspot locations and customers') that reflect the skill's actual capabilities.

Sharpen the 'Use when' clause with concrete triggers a user would naturally say, such as 'Use when the user wants to manage WiFi hotspots, view voucher or billing transactions, or look up hotspot locations and customers.'

Align the listed resources with the skill's real entities — the body covers Customers, Vouchers, Locations, Payment Gateways, Packages, Realms, and API Keys, not 'Organizations, Users, Projects'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('HotspotSystem integration') and lists managed entities ('Manage Organizations, Users, Projects'), but 'Manage' is a single generic verb rather than multiple distinct concrete actions, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It answers both 'what' ('Manage Organizations, Users, Projects') and 'when' ('Use when the user wants to interact with HotspotSystem data'); the 'when' clause is explicit but generic ('interact with data'), so it falls short of the concrete trigger phrases needed for a 5.	4 / 5
Trigger Term Quality	It surfaces the brand name 'HotspotSystem' and the trigger phrase 'interact with HotspotSystem data', but offers few natural keyword variations or synonyms a user would actually say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'HotspotSystem' brand carves a clear niche with minimal conflict risk, but the generic 'Organizations, Users, Projects' phrasing could overlap with many SaaS skills, keeping it just below a 5.	4 / 5
	Total	14 / 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/hotspotsystem/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.