Name: whosonlocation
Rating: 59.2 (1 reviews)
Author: membranedev

whosonlocation

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

Quality

68%

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/whosonlocation/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 an efficient, actionable guide to the Membrane CLI integration with a well-sequenced connection workflow and explicit state-handling checkpoints, held back slightly by runtime-discovery reliance and a loose 'Step 2' label rather than concrete product-specific action examples.

Suggestions

Resolve the dangling 'Step 2' reference by explicitly labeling the 'Searching for actions' section as Step 2, or rephrase to avoid numbered step cross-references.

Add a short, concrete example of running one or two real WhosOnLocation actions (e.g. listing people on-site) so the actionability reaches copy-paste coverage for the common cases.

Trim the introductory 'WhosOnLocation is a visitor management system...' paragraph or move it to a one-line context note to further tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, built around executable commands and a flag table with only minor over-explanation (the introductory paragraph on what WhosOnLocation is and the 'Best practices' prose), so it sits clearly above the midpoint but not fully lean.	4 / 5
Actionability	It provides concrete, copy-pasteable commands for install, auth, connection, action search/run, and proxy with a flag table, but relies on runtime discovery and gives no specific WhosOnLocation action examples, a minor gap.	4 / 5
Workflow Clarity	The connect-then-use sequence is clear with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-action feedback loop, but the dangling 'Step 2' reference and absence of run-action error handling leave minor gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references needed for this single-file skill, good structure with only minor organization gaps.	4 / 5
	Total	16 / 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 cleanly answers both what and when and is anchored to a distinct named product, but its action list is generic rather than concrete and its trigger vocabulary is limited to the product name alone.

Suggestions

Replace generic verbs with concrete WhosOnLocation-specific actions (e.g. 'check people on-site, manage visitors, view zone presence, trigger notifications') to lift specificity.

Add natural trigger phrases users would say, such as 'visitor management', 'people on-site', or 'sign-in kiosk', beyond just the product name.

Tighten the 'when' clause with concrete triggers, e.g. 'Use when the user wants to track visitors, check who is on-site, or manage WhosOnLocation records.'

Dimension	Reasoning	Score
Specificity	Names the WhosOnLocation domain and a few action areas ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, landing at the 2/3 boundary; the listing of multiple action areas lifts it above the minimal anchor.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with WhosOnLocation data') are present and explicit, though the 'what' is somewhat generic, keeping it below a 5.	4 / 5
Trigger Term Quality	The only natural trigger keyword is the product name 'WhosOnLocation' (in 'interact with WhosOnLocation data'); it lacks common synonyms, variations, or file-extension-style terms a user might say.	3 / 5
Distinctiveness Conflict Risk	The named product 'WhosOnLocation' gives it a clear, distinct niche with minimal conflict risk, but the generic action phrasing ('manage data, records') leaves minor overlap risk with other CRM/data-management skills.	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/whosonlocation/SKILL.md
Commit: f484c82

Reviewed: 3 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.