pygraphistry

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill as a dispatcher to specialized skills. Treat this as the Python SDK entrypoint; for a cross-interface entrypoint use

graphistry

将此技能用作专业技能的调度器。将其视为Python SDK的入口点；如需跨接口入口点，请使用

graphistry

。

Setup/auth/first plot from tables: use
```
pygraphistry-core
```
.
Direct Graphistry REST endpoint requests (
```
curl
```
,
```
/api/v2/...
```
, JWT/Bearer, upload/session/url params): immediately use
```
graphistry-rest-api
```
and skip ReadTheDocs discovery.
Styling/layout/static output/privacy and sharing: use
```
pygraphistry-visualization
```
.
Pattern matching, GFQL/Cypher queries, Let/DAG bindings, GRAPH constructors, predicates, remote graph queries: use
```
pygraphistry-gfql
```
.
UMAP/DBSCAN/embedding/anomaly and graph-AI notebooks: use
```
pygraphistry-ai
```
.
Database/platform integrations (Neo4j, Splunk, Kusto, Databricks, SQL, etc.): use
```
pygraphistry-connectors
```
.

从表格进行设置/授权/首次绘图：使用
```
pygraphistry-core
```
。
直接Graphistry REST端点请求（
```
curl
```
、
```
/api/v2/...
```
、JWT/Bearer、上传/会话/URL参数）：立即使用
```
graphistry-rest-api
```
，跳过ReadTheDocs探索。
样式/布局/静态输出/隐私与分享：使用
```
pygraphistry-visualization
```
。
模式匹配、GFQL/Cypher查询、Let/DAG绑定、GRAPH构造器、谓词、远程图查询：使用
```
pygraphistry-gfql
```
。
UMAP/DBSCAN/嵌入/异常检测与图AI笔记本：使用
```
pygraphistry-ai
```
。
数据库/平台集成（Neo4j、Splunk、Kusto、Databricks、SQL等）：使用
```
pygraphistry-connectors
```
。

REST-intent exception: do not run this protocol for REST tasks routed to
```
graphistry-rest-api
```
.

Start from

references/pygraphistry-readthedocs-toc.md

; do not crawl broad docs first.

Use

references/pygraphistry-readthedocs-top-level.tsv

for section-level shortcuts.

Pick exactly one primary skill and at most two secondary docs before fetching content.
Do one batched discovery read first (TOC + top-level index), then pick targets.
After discovery, do at most one deep-page read per iteration.

Prefer section indexes (

.../gfql/index.html

.../visualization/index.html

) before deep pages.

For routing replies, prefer ReadTheDocs URLs (
```
https://pygraphistry.readthedocs.io/...
```
) over GitHub/local file paths unless the user explicitly asks for source code links.
Keep the first routing response compact (typically 3-5 lines): selected skill + top links.
Escalate to deeper page fetches only after the user confirms direction or asks for detail.
Avoid serial micro-reads across many files when one batched lookup can answer routing.
Avoid blind full dumps (
```
cat *
```
, full sitemap dumps) that bloat context without improving routing quality.
For canonical URL verification, prefer local snapshot evidence first; use web fallback when the user requests freshness or local mapping is missing.

使用

references/pygraphistry-readthedocs-top-level.tsv

获取章节级快捷方式。

在获取内容前，准确选择一个主技能和至多两个辅助文档。
先进行一次批量发现读取（目录+顶级索引），然后选择目标。
发现后，每次迭代至多进行一次深度页面读取。
在深度页面之前，优先选择章节索引（
```
.../gfql/index.html
```
、
```
.../visualization/index.html
```
）。
对于路由回复，优先使用ReadTheDocs URL（
```
https://pygraphistry.readthedocs.io/...
```
）而非GitHub/本地文件路径，除非用户明确要求源代码链接。
保持首次路由回复简洁（通常3-5行）：选定的技能+顶级链接。
仅在用户确认方向或询问细节后，才进行更深层次的页面获取。
当一次批量查找即可完成路由时，避免跨多个文件进行串行微读取。
避免盲目完整转储（
```
cat *
```
、完整站点地图转储），这会膨胀上下文而不提高路由质量。
对于规范URL验证，优先使用本地快照证据；当用户要求新鲜度或本地映射缺失时，使用网络回退。

Read credentials from environment variables; do not hardcode secrets in tracked files.
Prefer
```
api=3
```
for modern features.
Prefer a plain
```
type
```
column on both nodes and edges for legend/category defaults.
Set explicit privacy mode before sharing links for sensitive data.
For large graphs, reduce columns/rows before upload and visualize focused subgraphs first.

Docs TOC snapshot:

references/pygraphistry-readthedocs-toc.md

文档目录快照：

references/pygraphistry-readthedocs-toc.md