Name: locoia
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

locoia

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

Quality

72%

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/locoia/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 strong, executable integration guide with concrete CLI commands and a clear connection workflow including validation states. Its main weaknesses are a slightly padded overview, a redundant 'Popular actions' section, and an unlabeled 'Step 2' reference that slightly muddies the workflow sequence.

Suggestions

Trim the opening overview paragraph to Locoia-relevant essentials and merge the redundant 'Popular actions' section into 'Searching for actions' to remove the repeated action-list command.

Label the workflow steps explicitly (e.g., 'Step 1: Connect', 'Step 2: Discover actions', 'Step 3: Run') so the 'Skip to Step 2' references resolve cleanly.

Add a brief validation note for batch/destructive action runs (e.g., dry-run or confirm-before-run) so the workflow checkpoints extend to the action execution phase.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening paragraph explaining what Locoia is and the redundant 'Popular actions' section that repeats the action-list command add minor padding, keeping it just below a 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure/get, action list, action run, request proxy) with concrete flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear with polling and explicit state checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but 'Step 2' is referenced without being clearly labeled and the 'Popular actions' section disrupts the flow, so it falls short of a 5.	4 / 5
Progressive Disclosure	The content is well-organized into clear sections with no nested references and a single external docs link; it is one cohesive file rather than split into reference files, giving good structure with minor organization gaps.	4 / 5
	Total	17 / 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 correctly follows the 'what + when' structure with an explicit use-trigger and is anchored to a named app. It is held back by generic action verbs ('manage data, records') and thin trigger-term variety.

Suggestions

Replace generic verbs with concrete actions specific to Locoia (e.g., 'pull location data, monitor reviews, sync records, and automate Locoia workflows').

Expand the trigger clause with natural synonyms users would actually say, e.g., 'Use when the user mentions Locoia, asks about location data, review monitoring, or Locoia workflows'.

Avoid overlap ambiguity by listing a distinct Locoia-specific capability that no generic data skill would claim.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain (Locoia integration) plus 1-2 actions, but 'manage data, records' is generic and not comprehensive, matching the score-3 anchor.	3 / 5
Completeness	It states what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Locoia data'); the 'when' is explicit but could be more specific about the trigger scenarios, so not a 5.	4 / 5
Trigger Term Quality	The trigger 'interact with Locoia data' includes the app name as a keyword but misses natural synonyms or variations users might say, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Locoia is a named external app with a distinct trigger ('interact with Locoia data'), giving a clear niche with only minor overlap risk against generic 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/locoia/SKILL.md
Commit: f484c82

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