[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BFEDNAV78CW1QBH8AFEVT":3,"skill-same:01M69BFEDNAV78CW1QBH8AFEVT":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M69BFEDNAV78CW1QBH8AFEVT","data-loading",null,"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.","microsoft\u002Fdata-formulator","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BF44TK0TP41QE6EZXBGRY",17682,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002Fpy-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Fdata-loading\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[24,25,26,27],"data loading","connectors","connect","run","2026-11-10 10:12:30",false,"---\nname: data-loading\ndescription: >-\n   Discover connected data sources, add new data connectors through a\n   user-confirmed form, inspect table metadata, and run bounded read-only probes\n   when the current workspace data is insufficient.\nwhen_to_use: >-\n  The user's question needs data that is not already available as a workspace\n   input, the user asks what connected data is available, or the user wants to\n   connect a database, warehouse, or cloud source. Not for analyzing tables\n   already listed in the workspace context.\nalways_on: false\ntools:\n  - list_data\n  - find_data\n  - describe_data\n  - probe_data\n  - list_connectors\n  - describe_connector\nactions:\n  - propose_data_operation\n  - propose_connection\n---\n\n# Skill: Data discovery\n\nThe workspace tables listed in your context are the data already loaded into the\nsystem, and the only data that can be read directly. Everything these tools\nreturn is *not* loaded yet — it lives in a connected source and only becomes\nusable after the user selects a loading option and the server materializes it.\n\nUse these tools to determine whether connected sources contain data needed for\nthe user's goal. They are read-only: discovering, describing, or probing a\nsource does not add anything to the workspace analysis inputs.\n\n## Adding a connector\n\nWhen the user wants to connect a new source, do not merely ask them to navigate\nto settings and do not attempt to connect on their behalf.\n\n1. Call `list_connectors` first because available built-ins and plugins vary by\n   deployment. For a broad request such as \"help me connect\", summarize the\n   concrete available types and ask which one they use.\n2. Once the source type is known, call `describe_connector` when field or auth\n   details are useful.\n3. **When the requested source type is known and available, you MUST call\n   `propose_connection` in this same turn.** Do not stop with text such as\n   \"I'll open the form\", \"you'll need to provide\", or a list of required\n   fields. Only the action opens the form. Include one or two helpful sentences\n   alongside the action call explaining what the user should review or supply;\n   this text appears above the chat while the form opens on the canvas. Pass\n   `prefilled` values the user already supplied, including values parsed from a\n   connection string or config snippet. Never invent missing values.\n4. The form is only a proposal. The user reviews it and clicks Connect; the\n   action must never connect automatically.\n\nPrefilled values may include credentials the user deliberately supplied. Do not\nrepeat those values in prose or subsequent tool output. They are transient form\nseeds and are removed from persisted UI state.\n\n## Discovery sequence\n\n1. Use `find_data` when the user names a business concept or table. Use\n   `list_data` when you need to browse available sources or hierarchy.\n2. Use `describe_data` before relying on columns, types, row counts, or filter\n   values. Pass the exact `source_id` and `table_key` returned by discovery.\n3. Use `probe_data` only when metadata is insufficient to choose a useful\n   bounded result. Probes are limited, read-only, and may be approximate.\n4. First reconcile discoveries with every table in `[PRIMARY TABLE(S)]`,\n   `[OTHER AVAILABLE TABLES]`, or `[AVAILABLE TABLES]`. If the needed data is\n   already loaded, use or explain that workspace table instead of proposing it.\n5. When there are genuinely missing useful alternatives, call\n   `propose_data_operation` with one\n   to three complete immutable plans. This pauses for the user's choice; it\n   does not load data yet.\n\n## Proposing loading options\n\nWrite your answer as **message text alongside the call** — that prose is what\nthe user reads, so it carries the whole answer. Do not put it in an action\nfield, and do not leave the call bare. Say what you went looking for, what you\nactually found, and what each option would give them — enough that they can\nchoose without opening a single preview. Two to four sentences; more when the\noptions differ in ways that matter (grain, coverage, freshness, joins needed),\nfewer when the choice is obvious. Name real tables and columns you saw during\ndiscovery, and say plainly when an option is a compromise or when you'd pick one\nyourself. Write it as you'd say it to a colleague, not as a schema summary.\n\n- Each `option` is a complete alternative: a concise action label (2–6 words)\n   and one or more tables. The labels are buttons, not sentences — the\n   reasoning belongs in your message text. The application displays table\n   previews separately, so don't list columns as a substitute for explaining.\n- Use only source IDs, table keys, columns, and values grounded by discovery.\n- For a whole table, omit `query`. Use the optional raw-row query only when the\n   request needs filters, projection, ordering, or an intentional limit. It uses\n   the same `filters` \u002F `columns` \u002F `order_by` \u002F `limit` vocabulary as\n   `probe_data`, without aggregation.\n- Do not invent operation IDs, plan IDs, or hashes. The server creates them.\n- Never propose an exact connector query already represented by a workspace\n   table. The server also enforces this using persisted load provenance.\n\n## Grounding rules\n\n- Never invent source IDs, table keys, columns, or category values.\n- Prefer cached catalog discovery before a live probe.\n- Treat probe rows as evidence for planning, not as analysis input data.\n- Keep queries structured and bounded. Do not generate source-specific SQL.\n- If a source is unavailable or permissions changed, report the tool result and\n  ask the user for the needed connection or choose another source.","# Skill: Data discovery\n\nThe workspace tables listed in your context are the data already loaded into the\nsystem, and the only data that can be read directly. Everything these tools\nreturn is *not* loaded yet — it lives in a connected source and only becomes\nusable after the user selects a loading option and the server materializes it.\n\nUse these tools to determine whether connected sources contain data needed for\nthe user's goal. They are read-only: discovering, describing, or probing a\nsource does not add anything to the workspace analysis inputs.\n\n## Adding a connector\n\nWhen the user wants to connect a new source, do not merely ask them to navigate\nto settings and do not attempt to connect on their behalf.\n\n1. Call `list_connectors` first because available built-ins and plugins vary by\n   deployment. For a broad request such as \"help me connect\", summarize the\n   concrete available types and ask which one they use.\n2. Once the source type is known, call `describe_connector` when field or auth\n   details are useful.\n3. **When the requested source type is known and available, you MUST call\n   `propose_connection` in this same turn.** Do not stop with text such as\n   \"I'll open the form\", \"you'll need to provide\", or a list of required\n   fields. Only the action opens the form. Include one or two helpful sentences\n   alongside the action call explaining what the user should review or supply;\n   this text appears above the chat while the form opens on the canvas. Pass\n   `prefilled` values the user already supplied, including values parsed from a\n   connection string or config snippet. Never invent missing values.\n4. The form is only a proposal. The user reviews it and clicks Connect; the\n   action must never connect automatically.\n\nPrefilled values may include credentials the user deliberately supplied. Do not\nrepeat those values in prose or subsequent tool output. They are transient form\nseeds and are removed from persisted UI state.\n\n## Discovery sequence\n\n1. Use `find_data` when the user names a business concept or table. Use\n   `list_data` when you need to browse available sources or hierarchy.\n2. Use `describe_data` before relying on columns, types, row counts, or filter\n   values. Pass the exact `source_id` and `table_key` returned by discovery.\n3. Use `probe_data` only when metadata is insufficient to choose a useful\n   bounded result. Probes are limited, read-only, and may be approximate.\n4. First reconcile discoveries with every table in `[PRIMARY TABLE(S)]`,\n   `[OTHER AVAILABLE TABLES]`, or `[AVAILABLE TABLES]`. If the needed data is\n   already loaded, use or explain that workspace table instead of proposing it.\n5. When there are genuinely missing useful alternatives, call\n   `propose_data_operation` with one\n   to three complete immutable plans. This pauses for the user's choice; it\n   does not load data yet.\n\n## Proposing loading options\n\nWrite your answer as **message text alongside the call** — that prose is what\nthe user reads, so it carries the whole answer. Do not put it in an action\nfield, and do not leave the call bare. Say what you went looking for, what you\nactually found, and what each option would give them — enough that they can\nchoose without opening a single preview. Two to four sentences; more when the\noptions differ in ways that matter (grain, coverage, freshness, joins needed),\nfewer when the choice is obvious. Name real tables and columns you saw during\ndiscovery, and say plainly when an option is a compromise or when you'd pick one\nyourself. Write it as you'd say it to a colleague, not as a schema summary.\n\n- Each `option` is a complete alternative: a concise action label (2–6 words)\n   and one or more tables. The labels are buttons, not sentences — the\n   reasoning belongs in your message text. The application displays table\n   previews separately, so don't list columns as a substitute for explaining.\n- Use only source IDs, table keys, columns, and values grounded by discovery.\n- For a whole table, omit `query`. Use the optional raw-row query only when the\n   request needs filters, projection, ordering, or an intentional limit. It uses\n   the same `filters` \u002F `columns` \u002F `order_by` \u002F `limit` vocabulary as\n   `probe_data`, without aggregation.\n- Do not invent operation IDs, plan IDs, or hashes. The server creates them.\n- Never propose an exact connector query already represented by a workspace\n   table. The server also enforces this using persisted load provenance.\n\n## Grounding rules\n\n- Never invent source IDs, table keys, columns, or category values.\n- Prefer cached catalog discovery before a live probe.\n- Treat probe rows as evidence for planning, not as analysis input data.\n- Keep queries structured and bounded. Do not generate source-specific SQL.\n- If a source is unavailable or permissions changed, report the tool result and\n  ask the user for the needed connection or choose another source.",{"name":5,"tools":33,"actions":40,"always_on":29,"description":7,"when_to_use":43},[34,35,36,37,38,39],"list_data","find_data","describe_data","probe_data","list_connectors","describe_connector",[41,42],"propose_data_operation","propose_connection","The user's question needs data that is not already available as a workspace\n input, the user asks what connected data is available, or the user wants to\n connect a database, warehouse, or cloud source. Not for analyzing tables\n already listed in the workspace context.","main","5477f0e236426dc8f74a498ec400414fba7fbc0f","py-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Fdata-loading",1745,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator","https:\u002F\u002Fdata-formulator.ai\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-09 22:13:49",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add microsoft\u002Fdata-formulator --skill data-loading",{"tool":60,"command":61},"bunx","bunx skills add microsoft\u002Fdata-formulator --skill data-loading",{"tool":63,"command":64},"pnpm","pnpm dlx skills add microsoft\u002Fdata-formulator --skill data-loading","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002Fpy-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Fdata-loading\u002FSKILL.md",true,[68,74,78],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"__init__.py","SCRIPT","脚本",41,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002Fpy-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Fdata-loading\u002F__init__.py",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"skill.py",14820,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002Fpy-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Fdata-loading\u002Fskill.py",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"tools.json","REFERENCE","参考文档",9415,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002Fpy-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Fdata-loading\u002Ftools.json",[85,111,117,126,134,143],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":106,"publishedAt":28},"01M69BFJ823DGYDZQMYBFSPJAW","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002Fpy-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Freport\u002FSKILL.md",[91,96,99,100,103],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":97,"categoryName":98,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员",{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[87,107,108,109,110],"executive summary","dashboard","visualize","summarize",{"skillNo":112,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":28},"01M69BFGGPGA5AK2V3N6PM2EXY","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002Fpy-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Fdata_loading\u002FSKILL.md",[115],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,25,27,26],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":28},"01M69BFCDH9Z63K4ND9MXB07H5","core","The analyst's built-in capabilities: data-inspection tools and the always-available actions (visualize and ask_user).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002Fpy-src\u002Fdata_formulator\u002Fanalyst\u002Fskills\u002Fcore\u002FSKILL.md",[123],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[119,109,125],"python",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":28},"01M69BFAS2GHW4CCQJR1PAXZPD","path-safety","服务端路径安全与文件访问编码规范。在编写文件下载路由、Agent 工具（文件读取\u002F目录列出）、数据连接器\u002FLoader、Workspace 路径操作、沙箱配置时使用。","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fpath-safety\u002FSKILL.md",[],[133],"path safety",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":28},"01M69BF8TAXKYRA9J8HY978H0H","language-injection","LLM Agent 多语言注入规范。在修改 Agent 提示词、添加新的 Agent 端点、处理用户可见的后端消息（message_code）时使用。","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Flanguage-injection\u002FSKILL.md",[],[141,142],"language injection","code",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":158,"publishedAt":28},"01M69BF6N55FCZ9Y10Q9BJE5VN","error-handling","统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fdata-formulator\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Ferror-handling\u002FSKILL.md",[149,152,155],{"categoryNo":150,"categoryName":151,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":153,"categoryName":154,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[159,160,161],"error handling","testing","frontend"]