fix: trim service principal emphasis; add data discovery and external data guidance

wherobots-usage: condense service principal to one line — it was
dominating responses at the expense of more useful guidance

wherobots-develop: add data discovery section — use MCP to browse open
data catalog before writing job logic; note external/proprietary data
can be registered via storage integrations and queried the same way

Author: ClayMav

.agents/skills/wherobots-develop/SKILL.md

@@ -7,6 +7,16 @@ description: Meta-knowledge for developing with the Wherobots CLI, Python SDK, a
 
 Use this skill when writing code, submitting jobs, or building integrations with the Wherobots platform.
 
+## Data Discovery Before Writing Job Logic
+
+Before implementing spatial job logic, use the MCP server to understand what data is actually available:
+
+- Browse `wherobots_open_data` with `list_databases_tool` / `list_tables_tool` to find pre-loaded datasets (Overture, FEMA, OpenStreetMap, etc.)
+- Use `describe_table_tool` to confirm geometry column names, CRS, and relevant filter fields
+- Test the spatial logic with `execute_query_tool` using `LIMIT 10` before committing to a job file
+
+**Proprietary or external data**: Wherobots supports registering external catalogs (your own S3 buckets, GCS, etc.) as catalog sources so they appear alongside open data in Sedona SQL. Use `wherobots api` CLI commands to discover and configure storage integrations — this lets job code reference external tables the same way it references `wherobots_open_data`.
+
 ## CLI-First for API Operations
 
 When implementing a workflow that involves Wherobots API operations (creating job runs, checking status, listing resources, managing workspaces), **plan to use the `wherobots` CLI first**. The CLI covers the full job lifecycle and is the right tool for operational tasks; reach for the Python or TypeScript SDK only when you need to integrate results into application code.

.agents/skills/wherobots-usage/SKILL.md

@@ -24,9 +24,7 @@ All interfaces use the same API key:
 - **VS Code extension**: stores the key in VS Code SecretStorage (set via Command Palette)
 - **Endpoint override**: `WHEROBOTS_API_URL` env var overrides the default `https://api.cloud.wherobots.com`
 
-**For production/automated jobs, always use a service principal API key**, not a personal user key. Service principals are not tied to any individual — jobs remain functional when team members leave. Personal API keys are for development only.
-
-Service principals and their API keys can be created via the API using `wherobots api` CLI commands (discover with `wherobots api --help`), enabling fully agentic setup without dashboard access. The org must be on Professional or Enterprise edition and the authenticating key must belong to an org admin.
+For production jobs, use a **service principal** API key rather than a personal one — service principals can be created via `wherobots api` CLI commands and are not tied to any individual.
 
 ## Scheduled / Recurring Jobs