Ikuzo - The Map Editor

Manage maps, spots, and travel plans on Ikuzo (ikuzo.app) — a location-based exploration app. Use when creating/editing maps, adding/searching spots, planning trips with day-by-day itineraries, finding nearby places, or managing travel logistics. Triggers on map management, spot tracking, trip planning, location discovery, and "where should I go" questions.

Security Scan

The skill's instructions call an authenticated Ikuzo API (Bearer token) but the registry metadata does not declare any required credentials or config locations — this mismatch and the ambiguous 'user config / TOOLS.md' guidance is a notable inconsistency that should be clarified before use.

Purpose & Capability

The declared purpose (map/spot/trip management for Ikuzo) matches the API surface described in SKILL.md (maps, spots, travels). However, SKILL.md requires a Bearer token for the API but the registry metadata lists no required environment variables or primary credential — that is inconsistent. A legitimate integration would normally declare a required API token (e.g., IKUZO_API_TOKEN).

Instruction Scope

The SKILL.md is instruction-only and confined to JSON-RPC calls to https://ikuzo.app/api/mcp and schema lookups. It does not instruct reading arbitrary system files or running local binaries. However it refers to Auth: 'Bearer token (from TOOLS.md or user config)', which is vague and could lead the agent to search for stored credentials or tooling documentation — this ambiguity expands the agent's scope unless clarified.

Install Mechanism

No install spec and no code files are included (instruction-only), so nothing will be written to disk or automatically installed by the skill itself. This is the lowest-risk install profile.

Credentials

Although the skill needs an API bearer token to operate, the skill declares no required environment variables or primary credential. The SKILL.md's suggestion to fetch the token 'from TOOLS.md or user config' is not justified by the registry metadata and could encourage credential lookup in unspecified places. The absence of a declared, scoped credential is disproportionate to the described functionality.

Persistence & Privilege

The skill does not request always:true and has no install or config-writing behavior described. It does not request elevated or persistent system privileges in the manifest.

What to consider before installing

Before installing, ask the publisher to clarify and fix the credential handling: they should declare an explicit required credential (for example IKUZO_API_TOKEN) or document exactly where the token comes from (and why the agent should not search arbitrary user config files). Verify the endpoint https://ikuzo.app is legitimate and that the token scope is least-privilege. Avoid pasting secrets into free-text chat — supply API tokens through the platform's secure credential mechanism. If you must test the skill, use a limited test account/token and confirm it only accesses maps/spots you expect (note that spots_nearby can search across all 'accessible' maps). If the publisher cannot provide a clear credential and privacy model, treat the skill as untrusted.

Ikuzo

Ikuzo is a map & travel planning app. Access via MCP (JSON-RPC 2.0 over HTTP POST).

Connection

Endpoint: https://ikuzo.app/api/mcp
Auth: Bearer token (from TOOLS.md or user config)
Protocol: JSON-RPC 2.0 — POST with {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"<tool>","arguments":{...}}}

Tools

Maps

• maps_list — list all maps (owned + shared)
• maps_get(mapId) — get map details
• maps_create(title) — create a new empty map, returns map with ID

Spots

• spots_list(mapId, ...) — list/filter spots in a map. Filters: status[], type[], period[], momentFrom/To, text, limit, offset, fields[]
• spots_get(spotId) — get spot details
• spots_create(mapId, title, gps{lat,lng}, ...) — create spot. Optional: description, type, status, period[], moment{date, repeat, reminder[]}
• spots_update(spotId, ...) — update any field (including moment, rating)
• spots_delete(spotId) — soft delete (recoverable)
• spots_nearby(lat, lng, ...) — find spots near a point across ALL accessible maps. Optional: radius (km, default 10, max 500), mapIds[], all spot filters. Returns sorted by distance.
• spots_box(north, south, east, west, ...) — find spots in bounding box. Same filters as nearby.

Travel Plans

• travels_list — list all travel plans
• travels_get(travelId) — get plan with steps
• travels_create(title) — create plan
• travels_update(travelId, title) — rename plan
• travels_delete(travelId) — delete plan

Steps (within a travel plan)

• steps_add(travelId, type, ...) — add step. type="spot" requires spotId, type="day" requires title. Optional: orderKey
• steps_update(stepId, ...) — update position or title
• steps_delete(stepId) — remove step

Utility

• ping — test connection
• schema — get valid values for type, status, period
• quota — check API usage (doesn't count against quota)

Schema Reference

See references/schema.md for valid spot types, statuses, and periods. Call schema tool at runtime if unsure.

Key Patterns

Find spots to visit nearby

spots_nearby(lat, lng, radius=20, status=["a","b"])

Status a = "Ikuzo!" (priority), b = "To Visit"

Seasonal spots with upcoming moments

spots_list(mapId, momentFrom="2026-03-01", momentTo="2026-04-30")

Create a trip itinerary

1. travels_create(title) → get travelId
2. steps_add(travelId, type="day", title="Day 1 - Arrival")
3. steps_add(travelId, type="spot", spotId="...") for each spot
4. Repeat day dividers + spots for each day

Efficient listing (reduce tokens)

Use fields to request only what you need:

spots_list(mapId, fields=["_id","title","gps","status","type"])

Image URLs

Spot images use Ikuzo's CDN:

https://ik.offbeatjapan.org/ikuzo/{imageId}.{ext}?tr=h-{height},w-{width}

Where imageId and ext come from the spot's image[] array.