Name: amazon-location-service
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

amazon-location-service

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

Quality

64%

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/amazon-location-service/SKILL.md

Quality

Content

67%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 solid, command-heavy integration guide with a clear authenticated connection workflow and a working polling feedback loop. Its main weaknesses are a padded marketing intro and a couple of broken step-cross-references ('Step 2') that slightly hurt clarity.

Suggestions

Cut the opening marketing paragraph and the 'so you can focus on the integration logic rather than auth plumbing' filler to improve token efficiency.

Fix the step numbering: label the 'Searching for actions' section as 'Step 2' or remove the 'skip to Step 2' / '1b' references so the workflow navigates cleanly.

Make 'Popular actions' actually list the popular actions instead of repeating the generic discovery command, to deliver on the section's promise.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening marketing paragraph ('lets developers add location data... without sacrificing data security or user privacy') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-pasteable commands throughout (install, login, connection ensure, action run, request) with a proxy flag table, placing it above anchor 3; placeholders like CONNECTION_ID and the 'Popular actions' section that repeats discovery without listing actual actions are minor gaps keeping it below 5.	4 / 5
Workflow Clarity	The connection setup is a clear sequence with a real feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED then re-poll, check error states); it stays below 5 because 'skip to Step 2' and the '1b' label reference a Step 2 that is never labeled, creating minor navigation gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections in a single file with no bundle files present; given the moderate length and lack of need for external references it is well-structured, though the detailed clientAction sub-fields and proxy flag table could optionally live in a reference file.	4 / 5
	Total	15 / 20 Passed

Description

61%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 signals a distinct niche and includes an explicit 'Use when' trigger, but its capability verbs are generic and it omits the concrete Amazon Location Service features (maps, geocoding, routing, tracking, geofencing) that would make it specific and trigger-rich.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions such as 'search places, calculate routes, track assets, and manage geofences'.

Add natural trigger terms users actually say, e.g. 'Use when the user asks about maps, geocoding, routing, asset tracking, or geofencing with Amazon Location Service'.

Include the service's core resource types (Map, Place Index, Route, Tracker, Geofence) to improve both specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('Amazon Location Service integration') but the actions 'Manage data, records, and automate workflows' are generic and not the concrete capabilities (maps, geocoding, routing, tracking, geofencing) listed in the body, so it sits below anchor 3.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Amazon Location Service data') are explicitly present; the 'when' could be more specific and the 'what' is somewhat generic, so it does not reach 5.	4 / 5
Trigger Term Quality	It includes the specific product name and 'data' as triggers, but misses the natural synonyms a user would say (maps, geocoding, routing, tracking, geofencing, fleets), matching 'some relevant keywords but missing common variations.'	3 / 5
Distinctiveness Conflict Risk	Naming the specific AWS service 'Amazon Location Service' gives it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 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/amazon-location-service/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.