PyGraphistry connector workflows for external data sources and graph databases. Use when asked to "connect graphistry to Neo4j", "load from Splunk into graphistry", "query Kusto/ADX and visualize", "Databricks graph", "TigerGraph with pygraphistry", "ingest SQL into a graph", or any "graphistry + [external platform]" request. Also triggers on Neptune, Postgres, BigQuery, Memgraph, or connector/plugin keywords. Proactively suggest when the user has data in an external system and wants graph visu…
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars2
LicenseLICENSE
Default branchmain
Open issues8
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md4,307 B
docsSUMMARY.md582 B
History
First seen on skills.sh
First recorded snapshot · 36 installs
SKILL.md
PyGraphistry Connectors
Doc routing (local + canonical)
First route with ../pygraphistry/references/pygraphistry-readthedocs-toc.md.
Use ../pygraphistry/references/pygraphistry-readthedocs-top-level.tsv for section-level shortcuts.
Only scan ../pygraphistry/references/pygraphistry-readthedocs-sitemap.xml when a needed page is missing.
Use one batched discovery read before deep-page reads; avoid cat * and serial micro-reads.
In user-facing answers, prefer canonical https://pygraphistry.readthedocs.io/en/latest/... links.
Strategy
Prefer dataframe-first ingestion when practical, then bind with edges()/nodes().
Use connector-specific notebook patterns when auth/query semantics are specialized.
For very large datasets, push filtering/aggregation upstream before plotting.
Keep connector and Graphistry credentials in env vars or secret stores; no hardcoded keys.
Never use placeholder literals like username='user' / password='pass' / username='...'; use os.environ[...] or os.environ.get(...).
For concise tasks, respond with a single compact code block and minimal prose.
In concise snippets, prefer explicit privacy literals ('private' or 'organization') over placeholder variables.
Connector triage rubric
Use native graph-db connectors (cypher(), Neptune/TigerGraph flows) when traversal is best expressed upstream.
For local Cypher-style queries on in-memory PyGraphistry graphs (no external DB), use g.gfql("MATCH ..."). Note: graphistry.cypher() is a distinct Neo4j/Memgraph/Neptune connector, not the same as local GFQL Cypher.
Use SQL/log source extraction when your source is tabular or SIEM-centric, then bind in PyGraphistry.
If unsure, start with source-native query -> dataframe -> edges()/nodes(), then optimize connector depth.