Amazon Location Service
ClineOfficialCreated by aws-geospatialDistributed by Cline
- Skill
- Tool integration
- Cloud and DevOps
- MIT-0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Amazon Location Service provides a suite of geospatial APIs for web and mobile applications. This skill covers the integration of maps, geocoding, routing, places search, geofencing, and device tracking. It emphasizes using the bundled JavaScript client for web development and leveraging resourceless API operations to simplify deployment and IAM management. The skill provides guidance on authentication via API keys or Cognito, proper MapLibre configuration, and best practices for address input and verification.
What it does
- Provides interactive maps using MapLibre or static map images.
- Converts addresses to coordinates (geocoding) and coordinates to addresses (reverse geocoding).
- Calculates routes, travel times, and service areas with traffic estimation.
- Enables text-based place search, nearby search, and autocomplete suggestions.
- Monitors geographical boundaries with geofences and tracks device locations.
- Simplifies authentication using API keys for public apps or Cognito for secure resources.
When to use it
- When building location-aware web or mobile applications on AWS.
- When you need to implement address autocomplete, validation, or standardization.
- When integrating interactive maps or route calculation into your software.
- When you need to track assets or monitor geofence entry and exit events.
- When migrating existing geospatial features to Amazon Location Service.
Advantages
- Reduces complexity by supporting resourceless API operations.
- Simplifies web integration with a pre-bundled JavaScript client.
- Provides granular control over authentication via IAM or API keys.
- Ensures consistent data quality through standardized address verification.
- Optimizes performance by using direct URL passing for map styles.
Usage examples
- “How do I implement an address autocomplete field for my web form?”
- The agent will guide you to use the Autocomplete API, display Address.Label instead of Title, and use GetPlace to retrieve full details once a user selects a suggestion.
- “How should I authenticate my map component for a public website?”
- The agent will recommend using an API Key with restricted AllowActions (e.g., geo-maps:GetTile) to avoid exposing AWS credentials while enabling map rendering.
- “What is the best way to verify a user-submitted address before saving it to my database?”
- The agent will advise using the Geocode API to validate and standardize the address string, checking for multiple matches to handle ambiguity.
- “How do I initialize a MapLibre map with Amazon Location Service?”
- The agent will provide the configuration steps, including passing the style descriptor URL directly and setting validateStyle to false for faster loading.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/cline/amazon-location-service/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip amazon-location-service.zip -d .agents/skills
Documentation by aws-geospatial
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
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:
Using
Titleinstead ofAddress.Labelfor display: In Autocomplete results, always displayAddress.Label. TheTitlefield may show components in reverse order and is not suitable for user-facing text.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.Forgetting
validateStyle: falsein MapLibre config: Always setvalidateStyle: falsein the MapLibre Map constructor for faster map load times with Amazon Location styles.Mixing resource-based and resourceless operations: When possible, prefer resourceless operations (direct API calls without pre-created resources) for simpler deployment and permissions.
Inconsistent API operation naming: Use the format
service:Operationwhen referencing APIs (e.g.,geo-places:Geocode,geo-maps:GetStyleDescriptor). SDK clients use@aws-sdk/client-*format.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.Wrong action names in API Key permissions: API key
AllowActionsusegeo-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 & Validation
Autocomplete → Type-ahead in address forms (partial input: "123 Main")
GetPlace → Get full details after user selects autocomplete result (by PlaceId)
Geocode → Validate complete user-typed address or convert address to coordinates
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:
Developer Guide: https://docs.aws.amazon.com/location/latest/developerguide/llms.txt
API Reference: https://docs.aws.amazon.com/location/latest/APIReference/llms.txt
Key Guidance for Better Recommendations
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:
@aws-sdk/client-geo-maps
@aws-sdk/client-geo-places
@aws-sdk/client-geo-routes
@aws-sdk/client-location
@aws-sdk/credential-providers
https://github.com/aws-geospatial/amazon-location-utilities-auth-helper-js
Resources:
NPM Package: @aws/amazon-location-client
GitHub Repository: aws-geospatial/amazon-location-client-js
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):
| Service | AllowActions | AllowResources |
|---|---|---|
| Maps | geo-maps:GetTile, geo-maps:GetStaticMap | arn:aws:geo-maps:REGION::provider/default |
| Places | geo-places:Autocomplete, geo-places:Geocode, geo-places:ReverseGeocode, geo-places:SearchText, geo-places:SearchNearby, geo-places:Suggest, geo-places:GetPlace | arn:aws:geo-places:REGION::provider/default |
| Routes | geo-routes:CalculateRoutes, geo-routes:CalculateRouteMatrix, geo-routes:CalculateIsolines, geo-routes:OptimizeWaypoints, geo-routes:SnapToRoads | arn: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.
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 - Validate addresses input from users before taking actions or persisting to databases
Calculate Routes - Calculate routes between locations with customizable travel options and display them on maps
Dynamic Map Rendering - Render dynamic maps with MapLibre
Places Search - Search for places or points of interest
Web JavaScript - Integrate Amazon Location services into web browser applications
Files
- ATTRIBUTION.mdAdded by AutoGineer883 B
- SKILL.md12.5 KiB
- references/address-input.md8.9 KiB
- references/address-verification.md15.9 KiB
- references/calculate-routes.md40.6 KiB
- references/dynamic-map.md10.6 KiB
- references/places-search.md17.4 KiB
- references/web-javascript.md14.9 KiB
references/address-verification.md
Address Verification
Audience Note: Keywords MUST, SHOULD, MAY in this document indicate requirements for agent recommendations to users, following RFC 2119.
Validate and standardize addresses before persisting to databases or taking actions.
Distinction from Address Input: The address-input reference covers the UI/UX of collecting addresses from users (autocomplete, type-ahead). This reference covers validation and standardization of addresses AFTER collection, before storage or processing.
Table of Contents
Overview
When to Verify Addresses
Basic Verification
Handling Verification Results
Complete Validation Flows
Storage Considerations and Pricing
Error Handling
Best Practices
Overview
Address verification ensures data quality by:
Validating - Confirming address exists in postal database
Standardizing - Converting to canonical format (proper casing, abbreviations)
Enriching - Adding coordinates, postal codes, country codes
Cleaning - Fixing typos, removing ambiguity
Use geo-places:Geocode for address verification AFTER user has completed input.
When to Verify Addresses
Verify addresses in these scenarios:
Before database insertion: Ensure only valid, standardized addresses are stored
Before shipping/delivery: Verify delivery address is valid and complete
Before API calls: Validate address before passing to routing or distance APIs
Batch processing: Clean existing address databases
Form submission: Final validation before accepting user submission
Integration imports: Validate addresses from external systems
Do NOT verify on every keystroke (use Autocomplete for that - see address-input reference).
Basic Verification
Single Address Verification
const authHelper = amazonLocationClient.withAPIKey(API_KEY, REGION);
const client = new amazonLocationClient.GeoPlacesClient(authHelper.getClientConfig());
async function verifyAddress(addressString) {
try {
const command = new amazonLocationClient.places.GeocodeCommand({
QueryText: addressString,
MaxResults: 5 // Get multiple matches to detect ambiguity
});
const response = await client.send(command);
if (response.ResultItems.length === 0) {
return {
valid: false,
reason: 'ADDRESS_NOT_FOUND',
message: 'Address not found in postal database'
};
}
const topResult = response.ResultItems[0];
// Check for ambiguous input (multiple strong matches)
const isAmbiguous = response.ResultItems.length > 1 &&
response.ResultItems[1].Address.Label.toLowerCase() !== topResult.Address.Label.toLowerCase();
return {
valid: true,
ambiguous: isAmbiguous,
standardized: topResult.Address,
coordinates: {
lat: topResult.Position[1],
lon: topResult.Position[0]
},
originalInput: addressString,
allMatches: response.ResultItems
};
} catch (error) {
console.error('Verification error:', error);
return {
valid: false,
reason: 'VERIFICATION_ERROR',
message: error.message
};
}
}
// Usage
const result = await verifyAddress("500 E 4th St, Austin, TX 78701");
if (result.valid) {
console.log('Valid address:', result.standardized.Label);
console.log('Coordinates:', result.coordinates);
} else {
console.log('Invalid:', result.message);
}Structured Address Verification
// Verify address from form fields
async function verifyStructuredAddress(fields) {
// Build address string from components
const parts = [
fields.street,
fields.city,
fields.state,
fields.postalCode,
fields.country
].filter(Boolean);
const addressString = parts.join(', ');
return await verifyAddress(addressString);
}
// Usage
const formData = {
street: "500 E 4th St",
city: "Austin",
state: "CA",
postalCode: "94043",
country: "USA"
};
const verification = await verifyStructuredAddress(formData);Handling Verification Results
Perfect Match
if (result.valid && !result.ambiguous) {
// Address is valid and unambiguous
// Store standardized version
await saveAddress({
original: result.originalInput,
standardized: result.standardized.Label,
street: result.standardized.Street,
addressNumber: result.standardized.AddressNumber,
locality: result.standardized.Locality,
region: result.standardized.Region?.Code,
postalCode: result.standardized.PostalCode,
country: result.standardized.Country?.Code2,
latitude: result.coordinates.lat,
longitude: result.coordinates.lon,
verified: true,
verifiedAt: new Date().toISOString()
});
}Address Not Found
if (!result.valid && result.reason === 'ADDRESS_NOT_FOUND') {
// Show error to user
showError(
'We could not verify this address. Please check for typos and try again.'
);
// Offer suggestions
if (result.originalInput.length > 10) {
// Suggest using autocomplete
showSuggestion(
'Try using the address autocomplete field for better results.'
);
}
// Still allow submission if user insists
showOption(
'Submit anyway (address will be marked as unverified)',
async () => {
await saveAddress({
original: result.originalInput,
verified: false,
verifiedAt: null
});
}
);
}Ambiguous Address
if (result.valid && result.ambiguous) {
// Present user with options
showAmbiguityDialog(
'We found multiple matches for this address. Please select the correct one:',
result.allMatches.map(match => ({
label: match.Address.Label,
details: {
locality: match.Address.Locality,
region: match.Address.Region?.Name,
postalCode: match.Address.PostalCode
},
onSelect: async () => {
await saveAddress({
standardized: match.Address.Label,
latitude: match.Position[1],
longitude: match.Position[0],
verified: true
});
}
}))
);
}Standardization Differences
// Check if geocoded address differs from input
if (result.valid) {
const inputNormalized = result.originalInput.toLowerCase().trim();
const standardizedNormalized = result.standardized.Label.toLowerCase().trim();
if (inputNormalized !== standardizedNormalized) {
// Show user the standardized version
const confirmed = await confirmDialog(
'We found a slight difference in the address:',
{
original: result.originalInput,
standardized: result.standardized.Label,
question: 'Use the standardized version?'
}
);
if (confirmed) {
// Use standardized
await saveAddress({
standardized: result.standardized.Label,
...result.coordinates,
verified: true
});
} else {
// Keep original but mark as manually confirmed
await saveAddress({
original: result.originalInput,
...result.coordinates,
verified: true,
manuallyConfirmed: true
});
}
}
}Complete Validation Flows
Pre-Submission Validation
// Validate form before submission
async function validateAddressForm(formElement) {
const submitButton = formElement.querySelector('button[type="submit"]');
const statusDiv = document.getElementById('validation-status');
formElement.addEventListener('submit', async (e) => {
e.preventDefault();
// Show loading state
submitButton.disabled = true;
statusDiv.innerHTML = 'Verifying address...';
// Get address from form
const addressInput = formElement.querySelector('#address').value;
try {
const result = await verifyAddress(addressInput);
if (!result.valid) {
statusDiv.innerHTML = `
<div class="error">
<strong>Address verification failed:</strong>
<p>${result.message}</p>
<button onclick="submitAnyway()">Submit Anyway</button>
<button onclick="editAddress()">Edit Address</button>
</div>
`;
submitButton.disabled = false;
return;
}
if (result.ambiguous) {
statusDiv.innerHTML = '<div class="warning">Multiple matches found. Please select:</div>';
showAmbiguityOptions(result.allMatches);
submitButton.disabled = false;
return;
}
// Update form with standardized address
if (result.standardized.Label !== addressInput) {
const useStandardized = confirm(
`Use standardized address?\n\nYou entered:\n${addressInput}\n\nStandardized:\n${result.standardized.Label}`
);
if (useStandardized) {
formElement.querySelector('#address').value = result.standardized.Label;
}
}
// Store coordinates in hidden fields
formElement.querySelector('#latitude').value = result.coordinates.lat;
formElement.querySelector('#longitude').value = result.coordinates.lon;
// Mark as verified
formElement.querySelector('#verified').value = 'true';
// Submit form
statusDiv.innerHTML = '<div class="success">Address verified!</div>';
formElement.submit();
} catch (error) {
statusDiv.innerHTML = `
<div class="error">
Verification error: ${error.message}
</div>
`;
submitButton.disabled = false;
}
});
}Batch Verification
// Verify multiple addresses (e.g., cleaning existing database)
async function batchVerifyAddresses(addresses) {
const results = [];
for (const address of addresses) {
try {
const result = await verifyAddress(address.text);
results.push({
id: address.id,
originalAddress: address.text,
verified: result.valid,
standardized: result.valid ? result.standardized.Label : null,
coordinates: result.valid ? result.coordinates : null,
ambiguous: result.ambiguous,
error: result.valid ? null : result.message
});
// Rate limiting - wait between requests
await new Promise(resolve => setTimeout(resolve, 100));
} catch (error) {
results.push({
id: address.id,
originalAddress: address.text,
verified: false,
error: error.message
});
}
// Progress indicator
console.log(`Verified ${results.length}/${addresses.length}`);
}
return results;
}
// Generate report
function generateVerificationReport(results) {
const stats = {
total: results.length,
verified: results.filter(r => r.verified && !r.ambiguous).length,
ambiguous: results.filter(r => r.ambiguous).length,
invalid: results.filter(r => !r.verified).length,
errors: results.filter(r => r.error).length
};
console.log('Verification Report:', stats);
return {
stats,
needsReview: results.filter(r => !r.verified || r.ambiguous)
};
}
// Usage
const addressesToVerify = [
{ id: 1, text: "500 E 4th St, Austin, TX 78701" },
{ id: 2, text: "301 Congress Ave, Austin, TX 78701" },
// ... more addresses
];
const verificationResults = await batchVerifyAddresses(addressesToVerify);
const report = generateVerificationReport(verificationResults);Storage Considerations and Pricing
IMPORTANT: How you store Places API results affects pricing. Review the Places API Stored Pricing documentation before implementing storage.
Pricing Tiers Based on Storage
Amazon Location Places API has different pricing based on the IntendedUse parameter:
Stored Pricing (IntendedUse: "Storage"):
✅ Can store results indefinitely
✅ Supports all features (Label, Core, Advanced)
✅ Price cap - maximum cost per API call
💰 Higher per-request cost
Use when: Building applications that cache results long-term or perform analysis on historical data
Other Pricing Tiers:
⚠️ Label & Core: Results cannot be stored permanently
⚠️ Advanced: Results can be cached temporarily but not stored indefinitely
💰 Lower per-request cost
Use when: Real-time lookups without long-term storage needs
Setting Stored Pricing
// To enable stored pricing (allows indefinite storage)
const command = new amazonLocationClient.places.GeocodeCommand({
QueryText: addressString,
IntendedUse: "Storage", // Required for long-term storage
MaxResults: 1
});Storage Decision Guide
Ask yourself:
Do you need to store results indefinitely?
YES → Use
IntendedUse: "Storage"and pay stored pricingNO → Use default pricing, don't store permanently
Will you reuse results to reduce API calls?
YES → Consider stored pricing for cost-effectiveness over time
NO → Use real-time lookups with default pricing
Are you building analytics on historical place data?
YES → Use
IntendedUse: "Storage"NO → Use default pricing
Error Handling
Validation Error Types
async function verifyAddressWithDetailedErrors(addressString) {
try {
const result = await verifyAddress(addressString);
if (!result.valid) {
// Classify error
if (addressString.length < 10) {
return {
valid: false,
errorCode: 'TOO_SHORT',
message: 'Address is too short. Please provide a complete address.',
suggestion: 'Include street, city, and state/postal code.'
};
}
if (!/\d/.test(addressString)) {
return {
valid: false,
errorCode: 'MISSING_NUMBER',
message: 'Address appears to be missing a street number.',
suggestion: 'Add the building or house number.'
};
}
if (!/[A-Z]{2}/.test(addressString.toUpperCase())) {
return {
valid: false,
errorCode: 'MISSING_STATE',
message: 'Please include the state or province.',
suggestion: 'Add the 2-letter state code (e.g., CA, NY).'
};
}
return {
valid: false,
errorCode: 'NOT_FOUND',
message: 'Address not found in postal database.',
suggestion: 'Check for typos or try entering in a different format.'
};
}
return result;
} catch (error) {
return {
valid: false,
errorCode: 'VERIFICATION_FAILED',
message: 'Unable to verify address due to technical error.',
technicalError: error.message
};
}
}Best Practices
When to Verify
Always verify before storage: Prevent bad data from entering database
Verify before critical actions: Shipping, delivery, routing
Don't verify on every keystroke: Use autocomplete during input, geocode at submission
Batch verification: For data imports, verify in batches with rate limiting
Data Quality
Understand pricing implications: Review stored pricing before implementing long-term storage
Use IntendedUse parameter: Set
IntendedUse: "Storage"if storing results indefinitelyConsider caching vs storage: Temporary session caching doesn't require stored pricing
Handle missing components: Not all addresses have all fields (street number, etc.)
User Experience
Show what changed: When standardizing, show user the difference
Allow manual override: Let users keep their version if they insist
Handle ambiguity gracefully: Present options, don't guess
Provide helpful errors: Explain WHY address is invalid and how to fix
Performance
Cache results: Cache verification results temporarily within your session
Rate limit batch jobs: Wait 100ms between batch verifications
Verify once per session: Don't re-verify address user already confirmed
Use autocomplete first: Preferred over post-hoc verification
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs an API key
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- aws-geospatial
- Publisher
- Cline (Official)
- Distributed by
- Cline
- Source
- cline/skills · skills/amazon-location-service · commit 2637846
- Licence
- MIT No Attribution (redistribution allowed)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by aws-geospatial or Cline.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download amazon-location-service.zip