open-map-stack

Plugin open-map-stack from marketplace open-map-stack in jaakla/openmapstack-skills. Commands read from the repo's manifest — 2 days ago.

Skills (12)

• neon-ai-gateway

  One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks. Use when a user wants to call an LLM, add AI/chat/an agent to their app, route between model providers (OpenAI, Anthropic, Google/Gemini, Meta, Alibaba, and more), or avoid juggling s

• neon-auth

  Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, passkeys, MFA, trusted domains, invalid domain, and @neondatabase/auth. No existing identity

• neon-functions

  Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASE_URL injected automatically and compute that runs next to your data. Use when a user wants to host an API, an AI agent with long streaming responses, a WebSocket or server-sent-events (SSE) server, a webhook

• neon-object-storage

  S3-compatible object storage that branches with your Neon project, so files and the database stay in sync across every branch. Use when a user wants object storage, a bucket, blob/file storage, or somewhere to put uploads, images, documents, avatars, or user-generated files for their app or agent —

• neon-postgres-branches

  Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, resetting a branch from its parent, branch expiration and CI/CD branch lif

• neon-postgres-egress-optimizer

  Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT * optimization, query overfetching,

• neon-postgres

  Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, and Lakebase Search. Use when the work is an existing DATABASE_URL, SQL,

• neon

  Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building

• geospatial-data-discovery

  Find and assess authoritative geospatial datasets or catalogs against known requirements: coverage, feature meaning, access, license, completeness, versions and reproducible pinning. Use for public sources, STAC/Portolan catalogs and read-only discovery of user data. Route joint source/compute/stora

• open-map-stack

  Plan and execute ambiguous or multi-stage GIS work, jointly choosing authoritative sources, compute, storage and delivery for the scale and team. Covers vector/raster/point-cloud analysis, routing, QGIS, tiles and web maps. Use for unresolved geospatial architecture and end-to-end analysis; prefer i

• reproducible-gis-project

  Compile, validate or maintain a reproducible GIS project from an existing analysis or chosen workflow: project.yaml, canonical pipeline, pinned sources, executable corrections, validation, reruns and QGIS/web presentation. Use when delivery and reproducibility are the task. Route unresolved source/c

• spatial-sql

  Write, review, debug or optimize spatial SQL on an already chosen engine, including DuckDB Spatial, PostGIS, BigQuery GIS, Snowflake and Sedona. Use for spatial predicates, joins, indexes, query plans, CRS and metric/geodesic correctness. Route unresolved engine or cross-system architecture choices

Similar plugins