Agent skills for the Wherobots spatial analytics platform. These skills provide AI coding assistants with the meta-knowledge they need to work effectively with Wherobots tools.
| Skill | Description |
|---|---|
wherobots-usage |
Decision matrix for choosing between MCP, CLI, SDK, and Dashboard; auth setup; scheduling guidance |
wherobots-explore |
MCP workflow patterns for data discovery, schema exploration, and spatial query generation |
wherobots-develop |
CLI discovery patterns, non-obvious flags, job submission workflow, Python and TypeScript SDK usage |
npx skills add wherobots/agent-skills@wherobots-usage
npx skills add wherobots/agent-skills@wherobots-explore
npx skills add wherobots/agent-skills@wherobots-developSkills are bundled in the Wherobots VS Code extension and available automatically in Copilot Chat and Claude Code when the extension is installed.
This repository is also a Cursor plugin. Installing it registers the Wherobots MCP server and all three skills in one step, with no manual .cursor/mcp.json editing. Search for Wherobots in Cursor's marketplace.
To install it before the listing is live:
git clone https://github.com/wherobots/agent-skills ~/.cursor/plugins/local/wherobotsReload Cursor, then check Cursor Settings > Tools & MCPs for wherobots-mcp-server. The first tool call opens a browser to sign in to Wherobots and pick an organization. Manual setup, including the API key alternative to OAuth, is documented at Set Up Wherobots in Cursor.
The repository root is the plugin, so Cursor ships the same SKILL.md files that CI validates here. There is no vendored copy to keep in sync.
| Path | Purpose |
|---|---|
.cursor-plugin/plugin.json |
Plugin manifest, validated in CI against Cursor's published schema |
mcp.json |
Registers wherobots-mcp-server at https://api.cloud.wherobots.com/mcp/ |
assets/logo.svg |
Marketplace listing icon |
Two constraints shape this layout. Cursor manifest paths cannot use parent traversal, so a plugin in a subdirectory could not reach .agents/skills/, which is why the plugin sits at the repo root. And skills is set explicitly to .agents/skills rather than Cursor's default skills/ directory, because the VS Code extension resolves skills from that path.
Bump version in plugin.json for every marketplace submission. Cursor manually reviews each release.
Every line in a skill must pass this test: "Does this make the agent measurably more effective, or can the agent already discover this from --help / MCP tool descriptions?"
Skills contain meta-knowledge only:
- Interface selection guidance (when to use MCP vs CLI vs SDK)
- Non-obvious workflows and sequences
- Gotchas that waste agent turns when discovered by trial and error
- Decision points between equally valid approaches
Skills do NOT contain:
- Tool parameter documentation (already in MCP/CLI
--help) - API reference material (discoverable at runtime)
- Tutorials or step-by-step guides
The benchmarks/ directory contains tasks for evaluating skill effectiveness. See benchmarks/README.md for details.
- Fork this repository
- Create a branch (
feat/improve-explore-skill) - Edit the relevant
SKILL.mdfile - Ensure frontmatter is valid:
namemust match the parent directory,descriptionis required - Open a pull request -- CI will validate frontmatter and lint markdown
MIT