CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/amazon-location-service/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is strongly command-driven with a well-modeled connection state machine, making it genuinely actionable. Its weaknesses are duplicated boilerplate, a marketing-style intro about a service Claude already knows, a dangling "Step 2" reference, and no offloading of detail into reference files despite exceeding a single-screen length.

Suggestions

Delete or compress the intro paragraph about what Amazon Location Service is and who uses it; keep only the feature list and official docs link.

Fix the broken step navigation: either number the steps (Step 1, 1b, 2...) so "skip to Step 2" resolves, or drop the step references entirely.

Deduplicate the CLI invocation forms (pick `membrane` or `npx @membranehq/cli` consistently) and merge the "Popular actions" section into "Searching for actions"; consider moving the clientAction state-handling detail to a references file.

DimensionReasoningScore

Conciseness

The opening paragraph ("Amazon Location Service lets developers add location data and functionality... without sacrificing data security or user privacy") explains a service Claude already knows, and there is duplicated content: the install command appears in two forms (`membrane` vs `npx @membranehq/cli`), and "Popular actions" repeats the search command from the previous section.

3 / 5

Actionability

Concrete copy-paste commands throughout (install, login, connection ensure, action list/run with JSON input, proxy requests with a full flag table), but examples remain placeholder-level with no worked example using a real action or intent, and the CLI invocation form is inconsistent.

4 / 5

Workflow Clarity

The connection state machine (READY / BUILDING-poll / CLIENT_ACTION_REQUIRED-re-poll / CONFIGURATION_ERROR) is a clear sequence with feedback loops, but "skip to **Step 2**" references a step that is never labeled or numbered, leaving the sequence's landmarks broken.

4 / 5

Progressive Disclosure

Everything is inlined in a single ~140-line file with no bundle files; the detailed connection-state handling (clientAction schema, polling semantics) is content that would fit better in a separate reference file, and the inline structure is not leveraged to split it.

3 / 5

Total

14

/

20

Passed

Description

57%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 names the domain and includes an explicit 'Use when...' clause, but the capability statement is generic boilerplate that gives no hint of the actual Location capabilities (maps, places, routes, trackers, geofences). Trigger coverage relies almost entirely on the service name itself.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete capabilities from the body, e.g. "Query place indexes, calculate routes, read tracker positions, and manage geofences via the Membrane CLI."

Add natural trigger terms and synonyms users would actually say, such as maps, geocoding, routing, geofencing, tracking, or track assets.

Clarify the Membrane/CLI relationship in the description so users understand this skill shells out to the Membrane CLI rather than calling the AWS API directly.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" is generic language that could describe any data skill; no Location-specific actions (maps, geocoding, tracking, geofencing) appear in the description even though the domain is named.

2 / 5

Completeness

Both what ("Amazon Location Service integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Amazon Location Service data") are present; the when is explicit but the what is vague, matching the anchor where 'when' could be more specific.

4 / 5

Trigger Term Quality

"Amazon Location Service" is the natural trigger users would say, but common variations and synonyms (maps, geocoding, routing, track assets, geofencing) are absent, so coverage beyond the service name is thin.

3 / 5

Distinctiveness Conflict Risk

The named AWS service gives a clear niche with distinct triggers, but the generic "manage data, records, and automate workflows" tail creates minor overlap risk with other data/workflow skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill