AI Agent Hub
Back to skills
SuperMap iServer CLI Assistant icon

SuperMap iServer CLI Assistant

Development Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_f47c39e1/iserver-skills.

About this skill

Problem

Operations around SuperMap iServer accumulate a lot of small details: login, service lifecycle, map export, spatial queries, and dataset queries all depend on exact commands, URLs, service names, layer names, and JSON parameters. When debugging service health or demonstrating GIS lookups, it is easy to mix up map-China versus map-China/rest, authorization modes such as PUBLIC, AUTHENTICATED, and PRIVATE, or query modes like BoundsQuery.

How it works

The skill translates natural-language intent into iserver commands. It can begin with iserver login, iserver ping, and iserver config --show, then route the request to service, map, or data subcommands. For example, “list available data services” can become iserver data list, while “export a map screenshot” can be shaped with --view-bounds, --center, and --scale. Main coverage includes:
- Server management: login, logout, version, connectivity, token, and logs.
- Service management: list, status, start/stop, delete, authorization, publish, and cache clearing.
- Map services: map details, legends, image export, BoundsQuery, DistanceQuery, FindNearest, SpatialQuery, and SqlQuery.
- Data services: data sources, datasets, and feature queries by ID or SQL.

Boundaries

It is intended for environments where the iserver CLI and a reachable SuperMap iServer endpoint are already available. Service names are case-sensitive; lifecycle commands usually use component names without /rest; tokens are valid for about 8 hours and must be refreshed after expiry; legend export for @@LayerGroup is not supported yet. If the CLI is unavailable or the session is not authenticated, the skill should remain in check-and-explain mode instead of performing side-effecting operations.

Use Cases

  • Check whether an iServer service is healthy by verifying login, ping, version, and service status before restarting it.
  • Prepare a map-service review by listing services, inspecting a map, and exporting a bounded screenshot for discussion.
  • Find features in a layer using BoundsQuery, SpatialQuery, or SQL to match a range, intersection condition, or attribute filter.
  • Inspect a data service by listing data sources and datasets, then query features by ID or SQL while checking limits.

Best For

  • GIS operations engineers who need to check iServer login, connectivity, service lifecycle, and token status.
  • Geospatial application engineers who inspect map details, export screenshots, legends, and spatial query results.
  • Data integration engineers who list data sources and datasets, then query features by ID or SQL.
  • Solution demonstrators who showcase iServer service availability, map queries, and data-service calls to customers.