New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Amazon Location Service

by awslabs in awslabs/agent-plugins

Integrates Amazon Location Service APIs for AWS applications.

OfficialApache-2.0Auto-check passedBackend & APIs

Install Amazon Location Service

skills CLI
$ npx skills add awslabs/agent-plugins --skill amazon-location-service -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install awslabs/agent-plugins amazon-location-service --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/awslabs/agent-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/amazon-location-service/skills/amazon-location-service .claude/skills/amazon-location-service && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
amazon-location-service
GitHub stars
916
Token cost
~4k tokens
SKILL.md length
1,497 words
Files
12 (incl. references)
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

Integrates Amazon Location Service APIs for AWS applications.

  • Works in 7 steps: Using Title instead of Address.Label for… → Using GetStyleDescriptor API for map… → Forgetting validateStyle: false in… → …
  • Users want to add maps (interactive MapLibre
  • SKILL.md covers Overview, When to Use This Skill, Amazon Location Service API… and Common Mistakes, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Amazon Location Service is an agent skill from awslabs/agent-plugins, published by the product's own GitHub organization. Integrates Amazon Location Service APIs for AWS applications. Use this skill when users want to add maps (interactive MapLibre or static images); geocode addresses to coordinates or reverse geocode coordinates to addresses; calculate routes, travel times, or service areas; find places and businesses through text search, nearby search, or autocomplete suggestions; retrieve detailed place information including hours, contacts, and addresses; monitor geographical boundaries with geofences; or track device locations…

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/address-input.md`, `references/address-verification.md` and `references/calculate-routes.md`).

It sits in Backend & APIs, covering Third-party API integration and Geospatial analysis. It works with Amazon Web Services. The repository describes itself as: Agent Plugins for AWS equip AI coding agents with the skills to help you architect, deploy, and operate on AWS. The licence is Apache-2.0.

When your agent uses it

  • Users want to add maps (interactive MapLibre
  • Geocode addresses to coordinates
  • Reverse geocode coordinates to addresses
  • Calculate routes

Example prompts

  • “Use the amazon-location-service skill to integrate Amazon Location Service APIs for AWS applications”
  • “/amazon-location-service”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Using Title instead of Address.Label for display: In Autocomplete results, always display Address.Label. The Title field may show…
  2. Using GetStyleDescriptor API for map initialization: MUST use direct URL passing to MapLibre…
  3. Forgetting validateStyle: false in MapLibre config: Always set validateStyle: false in the MapLibre Map constructor for faster map load…
  4. Mixing resource-based and resourceless operations: When possible, prefer resourceless operations (direct API calls without pre-created…
  5. Inconsistent API operation naming: Use the format service:Operation when referencing APIs (e.g., geo-places:Geocode…
  6. Not handling nested Address objects correctly: The Address object from GetPlace contains nested objects (Region.Code, Region.Name…
  7. Wrong action names in API Key permissions: API key AllowActions use geo-maps:, geo-places:, geo-routes: prefixes (e.g…

What it can do on your machine

Read from SKILL.md and the folder at commit fbefb37. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.aws.amazon.com
    • github.com
    • maplibre.org
    • npmjs.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Amazon Location Service loads about 4k tokens when it runs, and up to ~63k if it reads all its reference files. Until then it costs about 157 tokens; SKILL.md has 1,497 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~157
When it runs · the whole SKILL.md, loaded when a task matches
~4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~63k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from awslabs/agent-plugins at commit fbefb37, republished under its Apache-2.0 licence (© awslabs). 1,497 words, ~3,967 tokens.

Download SKILL.mdSave it as .claude/skills/amazon-location-service/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
amazon-location-service
description
Integrates Amazon Location Service APIs for AWS applications. Use this skill when users want to add maps (interactive MapLibre or static images); geocode addresses to coordinates or reverse geocode coordinates to addresses; calculate routes, travel times, or service areas; find places and businesses through text search, nearby search, or autocomplete suggestions; retrieve detailed place information including hours, contacts, and addresses; monitor geographical boundaries with geofences; or track device locations. Covers authentication, SDK integration, and all Amazon Location Service capabilities.
license
Apache-2.0
metadata.author
aws-geospatial
metadata.version
1.1

Overview

Amazon Location Service provides geospatial APIs for maps, geocoding, routing, places search, geofencing, and tracking. Prefer the bundled JavaScript client (@aws/amazon-location-client) for web development and use resourceless API operations to avoid managing AWS resources.

When to Use This Skill

Use this skill when:

  • Building location-aware web or mobile applications
  • Working with Amazon Location Service projects
  • Implementing maps, geocoding, routing, or places search
  • Adding geofencing or device tracking functionality
  • Integrating geospatial features into AWS applications

Do NOT use this skill for:

  • Google Maps, Mapbox, or Leaflet-with-OSM projects (unless migrating to Amazon Location)
  • Generic GIS operations without AWS context
  • Non-AWS geospatial services

Amazon Location Service API Overview

Places (SDK: geo-places, JS: @aws-sdk/client-geo-places)

  • Geocode (Forward/Reverse): Convert addresses to coordinates and vice versa
  • Search (Text/Nearby): Find points of interest with contact and hours info
  • Autocomplete: Predict addresses based on user input
  • Suggest: Predict places and points of interest based on partial or misspelled user input
  • Get Place: Retrieve place details by place ID

Jobs (SDK: location, JS: @aws-sdk/client-location)

  • Address Validation: Verify and standardize addresses in bulk with the asynchronous Jobs API (StartJob with Action ValidateAddress, then GetJob/ListJobs/CancelJob). It adds what Geocode lacks — a postal-authority verdict (ValidationGranularity, Mailable/Locatable, per-component StatusDetail), not just coordinates. Coverage is US, CA, UK, and AU only; for other countries use Geocode.

Maps (SDK: geo-maps, JS: @aws-sdk/client-geo-maps)

  • Dynamic Maps: Interactive maps using tiles with MapLibre rendering
  • Static Maps: Pre-rendered, non-interactive map images, good for including an image into a web page, or for thumbnail images

Routes (SDK: geo-routes, JS: @aws-sdk/client-geo-routes)

  • Route calculation with traffic and distance estimation
  • Service area/isoline creation
  • Matrix calculations for multiple origins/destinations
  • GPS trace alignment to road segments
  • Route optimization (traveling salesman problem)

Geofences & Trackers (SDK: location, JS: @aws-sdk/client-location)

  • Geofences: Detect entry/exit from geographical boundaries
  • Trackers: Current and historical device location tracking

API Keys (SDK: location, JS: @aws-sdk/client-location)

  • API Keys: Grant access to public applications without exposing AWS credentials

Common Mistakes

Avoid these frequent errors:

  1. Using Title instead of Address.Label for display: In Autocomplete results, always display Address.Label. The Title field may show components in reverse order and is not suitable for user-facing text.

  2. Using GetStyleDescriptor API for map initialization: MUST use direct URL passing to MapLibre (https://maps.geo.{region}.amazonaws.com/v2/styles/Standard/descriptor?key={apiKey}) instead of making GetStyleDescriptor API calls. The direct URL method is required for proper map rendering.

  3. Forgetting validateStyle: false in MapLibre config: Always set validateStyle: false in the MapLibre Map constructor for faster map load times with Amazon Location styles.

  4. Mixing resource-based and resourceless operations: When possible, prefer resourceless operations (direct API calls without pre-created resources) for simpler deployment and permissions.

  5. Inconsistent API operation naming: Use the format service:Operation when referencing APIs (e.g., geo-places:Geocode, geo-maps:GetStyleDescriptor). SDK clients use @aws-sdk/client-* format.

  6. Not handling nested Address objects correctly: The Address object from GetPlace contains nested objects (Region.Code, Region.Name, Country.Code2, etc.), not flat strings. Access nested properties correctly.

  7. Wrong action names in API Key permissions: API key AllowActions use geo-maps:, geo-places:, geo-routes: prefixes (e.g., geo-places:Geocode, geo-routes:CalculateRoutes). Do NOT use SDK client names (@aws-sdk/client-geo-places) or IAM-style actions. See the Authentication and Permissions section for the complete list.

Defaults

Use these default choices unless the user explicitly requests otherwise:

  • JavaScript SDK: Bundled client (CDN) for browser-only apps; npm modular SDKs (@aws-sdk/client-geo-*) for React and build tool apps
  • API operations: Resourceless for Maps/Places/Routes (Geofencing/Tracking always require pre-created resources)
  • Authentication: API Key for Maps/Places/Routes; Cognito for Geofencing/Tracking
  • Map style: Standard
  • Coordinate format: [longitude, latitude] (GeoJSON order)

Override: User can specify "use Cognito for Maps/Places/Routes" or "use bundled client for React".

API Selection Guidance

Choose the right API for your use case:

Address Input (interactive forms)
  • Autocomplete → Type-ahead in address forms (partial input: "123 Main")
  • GetPlace → Get full details after user selects autocomplete result (by PlaceId)
  • Geocode → Resolve a complete user-typed address to coordinates. Returns coordinates, a matched label, and match quality (MatchScores overall + per-component, AddressNumberCorrected) synchronously in one call — but no postal-deliverability verdict or standardized output.
Address Validation (verify & standardize)
  • StartJob (Action ValidateAddress) → Verify and standardize addresses in bulk against authoritative postal data; async Jobs API with Parquet input/output in Amazon S3. Coverage: US, CA, UK, AU only; for other countries use Geocode.
  • GetJob / ListJobs / CancelJob → Track, enumerate, and cancel validation jobs
  • Choose the Jobs API when you need a postal-authority verdict (ValidationGranularity, Mailable/Locatable, per-component StatusDetail) or bulk throughput. For a single ad-hoc check of whether one address resolves and how well it matched, the synchronous Geocode MatchScores is the right tool — do not stand up a job. See the address-verification reference.
Finding Locations
  • SearchText → General text search ("pizza near Seattle")
  • SearchNearby → Find places near a coordinate (restaurants within 5km)
  • Suggest → Predict places/POIs from partial or misspelled input
  • Autocomplete → Address-specific predictions (not for general POI search)
Geocoding
  • Geocode (Forward) → Address string → Coordinates
  • ReverseGeocode → Coordinates → Address
Maps
  • Dynamic Maps (tiles + MapLibre) → Interactive maps requiring pan, zoom, markers
  • Static Maps (image) → Non-interactive map images for thumbnails or email
Routing
  • CalculateRoutes → Single route between origin and destination
  • CalculateRouteMatrix → Multiple origins/destinations travel times
  • CalculateIsolines → Service areas (all locations reachable within time/distance)

LLM Context Files

When you need detailed API parameter specifications or service capabilities not covered in the reference files, fetch these llms.txt resources:

Key Guidance for Better Recommendations

Show full SKILL.md (635 more words)Show less
Prefer the Bundled JavaScript Client for Web Development

For convenient web application development, Amazon Location Service provides a bundled JavaScript client that simplifies integration and provides optimized functionality without custom bundling. This bundled client includes all libraries required to build client side web applications with Amazon Location Service.

Features included in the bundled client:

  • Enables direct pre-bundled dependency inclusion without custom bundle / build
  • Simplified authentication and API integration
  • TypeScript support with comprehensive type definitions
  • Support for all Amazon Location SDKs

Included SDKs and Libraries:

Resources:

Prefer Resourceless Operations

Amazon Location Places, Maps and Routes services offer both resource-based and resourceless API operations. Resourceless operations are often simpler and more appropriate for many use cases.

Resource-based operations require you to:

  • Create and configure Amazon Location Service resources (maps, place indexes, route calculators)
  • Manage resource lifecycle and permissions
  • Handle resource naming and organization

Resourceless operations allow you to:

  • Make API calls directly without pre-creating resources
  • Reduce deployment complexity
  • Simplify IAM permissions and API Key permissions
Authentication and Permissions

When discussing permissions for Amazon Location Places, Maps and Routes services, always include both IAM permissions and API Key permissions in your guidance. If the type of application being developed is clear, recommend the appropriate authorization tool as described below:

IAM Permissions - Recommended for server-side applications and AWS SDK usage:

  • Used with AWS credentials (access keys, roles, etc.)
  • Provide fine-grained access control
  • Required for resource management operations

API Key Permissions - Alternative authentication method, especially useful for client-side applications or applications deployed to unauthenticated (public) users:

  • Simplified authentication without exposing AWS credentials
  • Can be configured with specific allowed operations
  • Useful for web and mobile applications
  • Supports both resource-based and resourceless operations
  • Enables faster subsequent map loads through CDN caching

API Key Action Names - API keys use their own action naming convention. Do NOT use SDK client names or IAM action names — they will be rejected.

Resourceless API key actions (recommended):

ServiceAllowActionsAllowResources
Mapsgeo-maps:GetTile, geo-maps:GetStaticMaparn:aws:geo-maps:REGION::provider/default
Placesgeo-places:Autocomplete, geo-places:Geocode, geo-places:ReverseGeocode, geo-places:SearchText, geo-places:SearchNearby, geo-places:Suggest, geo-places:GetPlacearn:aws:geo-places:REGION::provider/default
Routesgeo-routes:CalculateRoutes, geo-routes:CalculateRouteMatrix, geo-routes:CalculateIsolines, geo-routes:OptimizeWaypoints, geo-routes:SnapToRoadsarn:aws:geo-routes:REGION::provider/default

Do NOT use legacy geo: prefixed actions (e.g., geo:GetMap*, geo:CalculateRoute) — these are for pre-created resources only and will not work with resourceless APIs.

LocationClient Setup

Geofencing and Tracking use LocationClient (@aws-sdk/client-location). These are resource-based operations — you MUST create resources (trackers, geofence collections) before using them.

javascript
import { LocationClient } from "@aws-sdk/client-location";

// Server-side: uses IAM credentials from environment/role
const client = new LocationClient({ region: "us-east-1" });
javascript
// Client-side: uses Amazon Cognito
import { LocationClient } from "@aws-sdk/client-location";
import { fromCognitoIdentityPool } from "@aws-sdk/credential-providers";

const client = new LocationClient({
  region: "us-east-1",
  credentials: fromCognitoIdentityPool({
    identityPoolId: "us-east-1:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    clientConfig: { region: "us-east-1" },
  }),
});

MCP Server Integration

Integrates with the AWS MCP Server (Apache-2.0 license) which provides access to AWS documentation, API references, and direct API interactions. See the Getting Started Guide for setup and credential configuration. To use a non-default region, add "--metadata", "AWS_REGION=<your-region>" to your MCP config args.

Additional Resources

Reference Files

Load these resources as needed for specific implementation guidance:

  • Address Input - Create effective address input forms for users with address type ahead completion improving input speed and accuracy
  • Address Verification - Verify and standardize addresses in bulk against authoritative postal data using the asynchronous Jobs API (StartJob with Action ValidateAddress), before persisting to databases or taking downstream actions
  • Calculate Routes - Calculate routes between locations with customizable travel options and display them on maps
  • Device Tracking - Track device locations in real time and query position history
  • Dynamic Map Rendering - Render dynamic maps with MapLibre
  • Google Maps Migration (Android) - Migrate Android application from Google Maps SDK for Android to Amazon Location Service
  • Google Maps Migration (iOS) - Migrate iOS application from Google Maps SDK for iOS to Amazon Location Service
  • Google Maps Migration (JavaScript) - Migrate JavaScript web application from Google Maps API to Amazon Location Service
  • Places Search - Search for places or points of interest
  • Web JavaScript - Integrate Amazon Location services into web browser applications
  • Zone Alerts - Monitor device positions against geographic boundaries and react to zone entry or exit

© awslabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (references) in plugins/amazon-location-service/skills/amazon-location-service of awslabs/agent-plugins.

  • SKILL.md
  • references/address-input.md
  • references/address-verification.md
  • references/calculate-routes.md
  • references/device-tracking.md
  • references/dynamic-map.md
  • references/google-migration-android.md
  • references/google-migration-ios.md
  • references/google-migration-web.md
  • references/places-search.md
  • references/web-javascript.md
  • references/zone-alerts.md

Open the folder on GitHubat commit fbefb37

Compare with similar skills

Amazon Location Service next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Amazon Location Service compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Amazon Location Service this skillawslabs/agent-plugins916—~4kAutomated safety check: PassApache-2.0
AWS Lambda Java Integrationgiuseppe-trisciuoglio/developer-kit357—~1.9kAutomated safety check: NotesMIT
AWS Lambda Php Integrationgiuseppe-trisciuoglio/developer-kit357—~2.3kAutomated safety check: NotesMIT
AWS Lambda Python Integrationgiuseppe-trisciuoglio/developer-kit357—~2.4kAutomated safety check: NotesMIT
AWS Lambda Typescript Integrationgiuseppe-trisciuoglio/developer-kit357—~2.9kAutomated safety check: NotesMIT
Firecrawl Build Onboardingfirecrawl/firecrawl190k1 repos~1.4kAutomated safety check: NotesISC

Similar skills

  • AWS Lambda Java Integration

    giuseppe-trisciuoglio/developer-kit

    Provides AWS Lambda integration patterns for Java with cold start optimization.

    357 GitHub stars~1.9k tokensUpdated 29 days ago
    Backend & APIsAuto-check: notes

  • AWS Lambda Php Integration

    giuseppe-trisciuoglio/developer-kit

    Provides AWS Lambda integration patterns for PHP with Symfony using the Bref framework.

    357 GitHub stars~2.3k tokensUpdated 29 days ago
    Backend & APIsAuto-check: notes

  • AWS Lambda Python Integration

    giuseppe-trisciuoglio/developer-kit

    Provides AWS Lambda integration patterns for Python with cold start optimization.

    357 GitHub stars~2.4k tokensUpdated 29 days ago
    Backend & APIsAuto-check: notes

  • AWS Lambda Typescript Integration

    giuseppe-trisciuoglio/developer-kit

    Provides AWS Lambda integration patterns for TypeScript with cold start optimization.

    357 GitHub stars~2.9k tokensUpdated 29 days ago
    Backend & APIsAuto-check: notes

  • Firecrawl Build Onboarding

    firecrawl/firecrawl

    Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

    190k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check: notes

  • Firecrawl Search Integration

    firecrawl/firecrawl

    Guidance for adding Firecrawl's /search endpoint to product code and agent workflows when a feature starts from a query rather than a URL.

    190k GitHub starsUsed in 1 repo~1.1k tokens
    Backend & APIsAuto-check passed

More from awslabs/agent-plugins

All 33 skills in this repo

  • Dataset Evaluation

    awslabs/agent-plugins

    Official

    Validates dataset formatting and quality for SageMaker model fine-tuning (SFT, DPO, or RLVR).

    916 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

  • Dataset Transformation

    awslabs/agent-plugins

    Official

    Generates code that transforms datasets between ML schemas for model training or evaluation.

    916 GitHub starsUsed in 1 repo~3.5k tokens
    Auto-check passed

  • AWS Lambda Managed Instances

    awslabs/agent-plugins

    Official

    Evaluate, configure, and migrate workloads to AWS Lambda Managed Instances (LMI).

    916 GitHub stars~4k tokensUpdated today
    Auto-check passed

  • Finetuning Technique

    awslabs/agent-plugins

    Official

    Selects a fine-tuning technique (SFT, DPO, RLVR, or RLAIF) for the user's use case and validates it against the selected model's available recipes.

    916 GitHub stars~604 tokensUpdated today
    Auto-check passed

  • Hyperpod Issue Report

    awslabs/agent-plugins

    Official

    Generate comprehensive issue reports from HyperPod clusters (EKS and Slurm) by collecting diagnostic logs and configurations for troubleshooting and AWS Support cases.

    916 GitHub stars~890 tokensUpdated today
    Auto-check passed

  • Hyperpod Performance Debugger

    awslabs/agent-plugins

    Official

    Diagnose performance issues on Amazon SageMaker HyperPod clusters — uneven NCCL bandwidth across nodes and poor filesystem throughput.

    916 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Amazon Location Service

What does Amazon Location Service do?

Integrates Amazon Location Service APIs for AWS applications. Amazon Location Service is an agent skill from awslabs/agent-plugins, published by the product's own GitHub organization. Integrates Amazon Location Service APIs for AWS applications.

When should I use Amazon Location Service?

Amazon Location Service fits situations like: users want to add maps (interactive MapLibre; geocode addresses to coordinates; reverse geocode coordinates to addresses; calculate routes.

How do I install Amazon Location Service in Claude Code?

Run `npx skills add awslabs/agent-plugins --skill amazon-location-service -a claude-code`. Or copy the skill folder (plugins/amazon-location-service/skills/amazon-location-service in awslabs/agent-plugins) into .claude/skills/amazon-location-service in your project. Claude Code loads it when a task matches its description.

How do I install Amazon Location Service in Codex?

Run `npx skills add awslabs/agent-plugins --skill amazon-location-service -a codex`. Or copy the skill folder (plugins/amazon-location-service/skills/amazon-location-service in awslabs/agent-plugins) into .agents/skills/amazon-location-service in your project. Codex loads it when a task matches its description.

Can I use Amazon Location Service in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add awslabs/agent-plugins --skill amazon-location-service -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amazon-location-service, .gemini/skills/amazon-location-service, .github/skills/amazon-location-service and .opencode/skills/amazon-location-service in your project.

What does Amazon Location Service need to run?

SKILL.md names no scripts, command-line tools or credentials: Amazon Location Service is instructions for the agent only.

Does Amazon Location Service access the network?

SKILL.md names 4 domains. As links in the text: docs.aws.amazon.com, github.com, maplibre.org and npmjs.com. This is read from the text; nothing was executed.

Is Amazon Location Service safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Amazon Location Service use?

Amazon Location Service is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Amazon Location Service use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 59k tokens, read only when the agent opens those files.

What are the alternatives to Amazon Location Service?

Skills that share tags, products or a category with Amazon Location Service: AWS Lambda Java Integration (giuseppe-trisciuoglio/developer-kit, 357 stars), AWS Lambda Php Integration (giuseppe-trisciuoglio/developer-kit, 357 stars), AWS Lambda Python Integration (giuseppe-trisciuoglio/developer-kit, 357 stars) and AWS Lambda Typescript Integration (giuseppe-trisciuoglio/developer-kit, 357 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Amazon Location Service?

awslabs (a GitHub organization, an official publisher) maintains it in awslabs/agent-plugins, which has 916 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 2026.

Source: awslabs/agent-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.