ncloud-mapsQuery Naver Cloud Maps APIs for route navigation. Smart routing: Directions5 by default, auto-switches to Directions15 for 5+ waypoints.
Install via ClawdBot CLI:
clawdbot install beomsu317/ncloud-mapsWhen a user requests a route calculation with addresses or coordinates, use this skill to calculate driving time, distance, and cost.
Usage:
/skill ncloud-maps [waypoints] longitude,latitude format OR addresses (convert using goplaces/naver-local-search first)Examples:
/skill ncloud-maps "126.9633,37.5524" "127.0165,37.4889" (coordinates)/skill ncloud-maps μνμ μμ΄μ (addresses - requires geocoding skill first)Query Naver Cloud Maps APIs for intelligent routing (Directions5 + Directions15).
v1.0.8+ β By default, the skill uses Directions5 for queries with fewer than 5 waypoints, and automatically switches to Directions15 when you have 5 or more waypoints. No manual selection needed.
| Waypoints | API Used | Max Waypoints |
|-----------|----------|---------------|
| 0β4 | Directions5 | 5 |
| 5+ | Directions15 | 15 |
Client ID (API Key ID) and Client Secret (API Key)export NCLOUD_API_KEY_ID="your-api-key-id"
export NCLOUD_API_KEY="your-api-key-secret"
Or create a .env file:
NCLOUD_API_KEY_ID=your-api-key-id
NCLOUD_API_KEY=your-api-key-secret
cd ~/.openclaw/workspace/skills/ncloud-maps
npm install
ncloud-maps requires coordinates in longitude,latitude format. If you have address-based location data, use one of these compatible skills to convert addresses to coordinates:
Available Options (choose based on your environment):
| Skill | Provider | Coordinates | Setup Required |
|-------|----------|-------------|-----------------|
| goplaces | Google Places API | Yes (lon,lat) | GOOGLE_PLACES_API_KEY |
| naver-local-search | Naver Local Search | Yes (lon,lat) | NAVER_CLIENT_ID, NAVER_CLIENT_SECRET |
| Custom API | Your choice | Yes (lon,lat) | Your setup |
Example workflow with goplaces:
# Get coordinates from address
COORDS=$(goplaces resolve "κ°λ¨μ, μμΈ" --json | jq -r '.places[0] | "\(.location.longitude),\(.location.latitude)"')
# Use coordinates with ncloud-maps
npx ts-node scripts/index.ts --start "$COORDS" --goal "127.0049,37.4947"
Example workflow with naver-local-search:
# Get coordinates from address
COORDS=$(naver-local-search search "κ°λ¨μ" --format json | jq -r '.[0] | "\(.x),\(.y)"')
# Use coordinates with ncloud-maps
npx ts-node scripts/index.ts --start "$COORDS" --goal "127.0049,37.4947"
Or integrate any other geocoding service that returns longitude,latitude coordinates.
By default, no --api flag needed. The skill automatically:
Provide coordinates in longitude,latitude format:
# 0β4 waypoints β Directions5 (automatic)
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087" \
--waypoints "127.0100,37.5000|127.0200,37.5100"
# 5+ waypoints β Directions15 (automatic)
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087" \
--waypoints "127.0100,37.5000|127.0200,37.5100|127.0300,37.5200|127.0400,37.5300|127.0500,37.5400"
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087"
If you need to override the smart routing:
# Force Directions5 (max 5 waypoints)
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087" \
--api directions5 \
--waypoints "127.0100,37.5000|127.0200,37.5100"
# Force Directions15 (max 15 waypoints)
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087" \
--api directions15 \
--waypoints "127.0100,37.5000|127.0200,37.5100|127.0300,37.5200|127.0400,37.5300|127.0500,37.5400"
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087" \
--waypoints "127.0100,37.5000"
Multiple waypoints:
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087" \
--waypoints "127.0100,37.5000|127.0200,37.5100"
Choose from: trafast (fast), tracomfort (comfort), traoptimal (default), traavoidtoll (toll-free), traavoidcaronly (avoid car-only roads)
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087" \
--option "traavoidtoll"
npx ts-node scripts/index.ts \
--start "127.0683,37.4979" \
--goal "126.9034,37.5087" \
--cartype 2 \
--fueltype "diesel" \
--mileage 10.5
Vehicle types:
1 (default): Small sedan2: Medium van/cargo3: Large vehicle4: 3-axle cargo truck5: 4+ axle special cargo6: Compact carFuel types: gasoline (default), highgradegasoline, diesel, lpg
{
"success": true,
"start": "127.0683,37.4979",
"goal": "126.9034,37.5087",
"distance": 12850,
"duration": 1145000,
"toll_fare": 0,
"taxi_fare": 18600,
"fuel_price": 1550,
"departure_time": "2026-02-21T14:10:00"
}
success - Whether the query succeededstart - Starting point coordinatesgoal - Destination coordinatesdistance - Total distance in metersduration - Total duration in milliseconds (Γ·1000 = seconds)toll_fare - Toll/highway fare in KRWtaxi_fare - Estimated taxi fare in KRWfuel_price - Estimated fuel cost in KRWdeparture_time - Query timestamperror - Error message (if success=false)longitude,latitude format from the resultlongitude,latitude format (direct input or from geocoding skill)longitude,latitude formatβ οΈ This skill only calculates vehicle (car) routes. It does not support:
For those use cases, use transit-specific APIs (e.g., Kakao Map, Naver Map Transit API).
Required:
NCLOUD_API_KEY_ID - Naver Cloud API Key IDNCLOUD_API_KEY - Naver Cloud API Key SecretSmart Routing:
General:
Common errors:
μ’ν νμ μ€λ₯ - Invalid coordinate format (use longitude,latitude)Authentication Failed - Invalid API credentialsQuota Exceeded - API rate limit hitNo routes found - No valid route between pointsCheck Naver Cloud Console for:
See api-spec.md for detailed API specifications.
Generated Mar 1, 2026
Delivery companies can use this skill to calculate optimal routes for drivers, factoring in multiple stops, toll costs, and fuel efficiency. It helps in scheduling deliveries by estimating travel time and expenses, improving operational efficiency and customer service.
Ride-hailing apps can integrate this skill to provide accurate fare estimates, route planning, and ETA predictions for drivers and passengers. It supports dynamic routing with waypoints for shared rides and calculates taxi fares and fuel costs for profitability analysis.
Businesses with vehicle fleets can use this skill to plan routes for sales teams, service technicians, or company cars, optimizing for time and cost. It enables tracking of toll and fuel expenses, aiding in budget management and reducing operational overhead.
Travel agencies or tour operators can leverage this skill to create detailed driving itineraries for tourists, including multiple attractions as waypoints. It calculates distances and durations to help plan day trips, ensuring efficient use of time and cost-effective travel.
Emergency services or field technicians can use this skill for quick route calculation to incident locations, prioritizing fast or toll-free options. It aids in dispatching resources efficiently by estimating arrival times and managing multiple service calls with waypoints.
Offer this skill as part of a subscription-based software service for businesses needing regular route optimization. Charge monthly fees based on usage tiers, such as number of queries or advanced features like custom vehicle settings, generating recurring revenue.
License this skill to other developers or companies for integration into their own applications, such as logistics platforms or mobile apps. Charge per API call or through annual licensing agreements, providing a scalable revenue stream from high-volume users.
Provide consulting services to help businesses implement and customize this skill for specific needs, such as integrating with existing geocoding tools or optimizing for unique fleet requirements. Charge project-based or hourly rates for setup and support.
π¬ Integration Tip
Ensure geocoding skills like goplaces or naver-local-search are set up first to convert addresses to coordinates, as ncloud-maps requires longitude,latitude format for input.
Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).
Reorder Foodora orders + track ETA/status with ordercli. Never confirm without explicit user approval. Triggers: order food, reorder, track ETA.
Google Maps integration for OpenClaw with Routes API. Use for: (1) Distance/travel time calculations with traffic prediction, (2) Turn-by-turn directions, (3...
Flight tracking and scheduling. Track live flights in real-time by region, callsign, or airport using OpenSky Network. Search flight schedules between airports. Use for queries like "What flights are over Switzerland?" or "When do flights from Hamburg arrive in Zurich?" or "Track flight SWR123".
Use when the user asks to "find flights", "compare itineraries", "search hidden-city routes", "check cheapest dates", "explore destinations", "search hotels"...
Comprehensive travel planning, booking, and management skill. Use when needing to plan international trips, manage multi-destination itineraries, handle family travel logistics, optimize travel costs, and coordinate complex travel arrangements.