data-loading
Discover connected data sources, add new data connectors through a user-confirmed form, inspect table metadata, and run bounded read-only probes when the current workspace data is insufficient.
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 1.8w
- Forks
- 1.7k
01 前言 Front Matter
- name
- data-loading
- tools
- [ "list_data", "find_data", "describe_data", "probe_data", "list_connectors", "describe_connector" ]
- actions
- [ "propose_data_operation", "propose_connection" ]
- always_on
- false
- description
- Discover connected data sources, add new data connectors through a user-confirmed form, inspect table metadata, and run bounded read-only probes when the current workspace data is insufficient.
- when_to_use
- The user's question needs data that is not already available as a workspace input, the user asks what connected data is available, or the user wants to connect a database, warehouse, or cloud source. Not for analyzing tables already listed in the workspace context.
02 资源文件 3
- 脚本__init__.py41 B
- 脚本skill.py14.5 KB
- 参考文档tools.json9.2 KB
03 SKILL.md 正文
Skill: Data discovery
The workspace tables listed in your context are the data already loaded into the system, and the only data that can be read directly. Everything these tools return is not loaded yet — it lives in a connected source and only becomes usable after the user selects a loading option and the server materializes it.
Use these tools to determine whether connected sources contain data needed for the user's goal. They are read-only: discovering, describing, or probing a source does not add anything to the workspace analysis inputs.
Adding a connector
When the user wants to connect a new source, do not merely ask them to navigate to settings and do not attempt to connect on their behalf.
- Call
list_connectorsfirst because available built-ins and plugins vary by deployment. For a broad request such as "help me connect", summarize the concrete available types and ask which one they use. - Once the source type is known, call
describe_connectorwhen field or auth details are useful. - When the requested source type is known and available, you MUST call
propose_connectionin this same turn. Do not stop with text such as "I'll open the form", "you'll need to provide", or a list of required fields. Only the action opens the form. Include one or two helpful sentences alongside the action call explaining what the user should review or supply; this text appears above the chat while the form opens on the canvas. Passprefilledvalues the user already supplied, including values parsed from a connection string or config snippet. Never invent missing values. - The form is only a proposal. The user reviews it and clicks Connect; the action must never connect automatically.
Prefilled values may include credentials the user deliberately supplied. Do not repeat those values in prose or subsequent tool output. They are transient form seeds and are removed from persisted UI state.
Discovery sequence
- Use
find_datawhen the user names a business concept or table. Uselist_datawhen you need to browse available sources or hierarchy. - Use
describe_databefore relying on columns, types, row counts, or filter values. Pass the exactsource_idandtable_keyreturned by discovery. - Use
probe_dataonly when metadata is insufficient to choose a useful bounded result. Probes are limited, read-only, and may be approximate. - First reconcile discoveries with every table in
[PRIMARY TABLE(S)],[OTHER AVAILABLE TABLES], or[AVAILABLE TABLES]. If the needed data is already loaded, use or explain that workspace table instead of proposing it. - When there are genuinely missing useful alternatives, call
propose_data_operationwith one to three complete immutable plans. This pauses for the user's choice; it does not load data yet.
Proposing loading options
Write your answer as message text alongside the call — that prose is what the user reads, so it carries the whole answer. Do not put it in an action field, and do not leave the call bare. Say what you went looking for, what you actually found, and what each option would give them — enough that they can choose without opening a single preview. Two to four sentences; more when the options differ in ways that matter (grain, coverage, freshness, joins needed), fewer when the choice is obvious. Name real tables and columns you saw during discovery, and say plainly when an option is a compromise or when you'd pick one yourself. Write it as you'd say it to a colleague, not as a schema summary.
- Each
optionis a complete alternative: a concise action label (2–6 words) and one or more tables. The labels are buttons, not sentences — the reasoning belongs in your message text. The application displays table previews separately, so don't list columns as a substitute for explaining. - Use only source IDs, table keys, columns, and values grounded by discovery.
- For a whole table, omit
query. Use the optional raw-row query only when the request needs filters, projection, ordering, or an intentional limit. It uses the samefilters/columns/order_by/limitvocabulary asprobe_data, without aggregation. - Do not invent operation IDs, plan IDs, or hashes. The server creates them.
- Never propose an exact connector query already represented by a workspace table. The server also enforces this using persisted load provenance.
Grounding rules
- Never invent source IDs, table keys, columns, or category values.
- Prefer cached catalog discovery before a live probe.
- Treat probe rows as evidence for planning, not as analysis input data.
- Keep queries structured and bounded. Do not generate source-specific SQL.
- If a source is unavailable or permissions changed, report the tool result and ask the user for the needed connection or choose another source.
04 同仓库更多 Skills
report
Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.
data-loading
Discover connected data sources, add new data connectors through a user-confirmed form, inspect table metadata, and run bounded read-only probes when the current workspace data is insufficient.
core
The analyst's built-in capabilities: data-inspection tools and the always-available actions (visualize and ask_user).
path-safety
服务端路径安全与文件访问编码规范。在编写文件下载路由、Agent 工具(文件读取/目录列出)、数据连接器/Loader、Workspace 路径操作、沙箱配置时使用。
language-injection
LLM Agent 多语言注入规范。在修改 Agent 提示词、添加新的 Agent 端点、处理用户可见的后端消息(message_code)时使用。
error-handling
统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。