ClawHub

Amazon Location Service

v1.0.2

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

⭐ 0· 42·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill's name and description match the SKILL.md: it documents using the Membrane CLI to access Amazon Location Service (maps, routes, trackers, etc.). No unrelated credentials, binaries, or config paths are requested.
✓
Instruction Scope
Runtime instructions are limited to installing and using the @membranehq/cli, performing Membrane login, creating connections, listing actions, running actions, and proxying requests to AWS Location Service. The instructions do not ask the agent to read arbitrary files, environment variables, or other system configuration.
ℹ
Install Mechanism
There is no registry install spec (instruction-only). The SKILL.md recommends 'npm install -g @membranehq/cli' — a standard public npm package install. This is expected for a CLI-based integration but carries the usual npm-global-install risk (trust the package publisher and verify package authenticity).
✓
Credentials
The skill declares no required env vars or credentials and explicitly advises letting Membrane manage credentials server-side. That is proportionate for a proxy-based integration. Users should be aware that the Membrane service will handle and therefore see the authentication tokens/requests.
✓
Persistence & Privilege
The skill is instruction-only, has no install spec that writes files, and is not configured always:true. Autonomous invocation is allowed (platform default) but not combined with other red flags.
Assessment
This skill appears coherent: it uses the Membrane CLI to mediate access to Amazon Location Service rather than asking for AWS keys directly. Before installing, verify you trust Membrane/@membranehq (check npm package page and the referenced GitHub repository), be comfortable authorizing via the browser (Membrane will receive proxy access to your Amazon Location data), and be aware that a global npm install runs third-party code on your machine. If you prefer not to route data via a third-party service, do not use this skill.

Like a lobster shell, security has layers — review code before you run it.

latestvk9783279tb43yjpf2catxqk8ys842vxa

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments