Graphistry Router

Use this skill as the shared entrypoint across Graphistry interfaces.

Route By Interface

• Python SDK tasks (import graphistry, DataFrame shaping, .plot(), .gfql() including Cypher/Let/DAG, PyGraphistry notebooks): use pygraphistry.
• REST API tasks (curl, /api/v2/..., JWT/Bearer auth, upload endpoints, graph.html URL params): use graphistry-rest-api.
• JavaScript/TypeScript SDK tasks (@graphistry/*, browser/frontend integrations): use graphistry-js if available.

Mixed Requests

• If a request mixes Python SDK and REST endpoints, start with pygraphistry and pull in graphistry-rest-api for exact endpoint syntax.
• For named-endpoint questions, keep guidance user-facing: /api/v2/o/<org>/functions/... for definition lifecycle and /api/v2/o/<org>/run/... for execution.
• Keep the first routing response compact: selected interface + one minimal snippet + one canonical doc link.

Safety Rules

• Use environment variables for credentials and secrets.
• Never put JWT tokens in URL query parameters.
• Prefer documented endpoints; avoid invented helper endpoints.