[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699KAQ4ZTVEQA7CJZD9MHTN":3,"skill-same:01M699KAQ4ZTVEQA7CJZD9MHTN":75},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":74},"01M699KAQ4ZTVEQA7CJZD9MHTN","add-connector",null,"Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.","microsoft\u002Fpower-platform-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699JVYJFB75D9JM70BN4H0Q",1149,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-apps\u002Fskills\u002Fadd-connector\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"add connector","add","Connector","power","generic","for","true","apps","app","platform","lsp","power apps","edit","write","read","grep","Bash","code","connectors","power platform","2026-11-10 10:12:30",false,"---\nname: add-connector\ndescription: Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.\nuser-invocable: true\nallowed-tools: Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill\nmodel: sonnet\n---\n\n**? Shared Instructions: [shared-instructions.md](..\u002F..\u002Fshared\u002Fshared-instructions.md)** - Cross-cutting concerns.\n\n# Add Connector (Generic)\n\nFallback skill for any connector not covered by a specific `\u002Fadd-*` skill. For common connectors, prefer the dedicated skills:\n\n- `\u002Fadd-dataverse` -- Dataverse tables\n- `\u002Fadd-azuredevops` -- Azure DevOps\n- `\u002Fadd-teams` -- Microsoft Teams\n- `\u002Fadd-excel` -- Excel Online (Business)\n- `\u002Fadd-onedrive` -- OneDrive for Business\n- `\u002Fadd-sharepoint` -- SharePoint Online\n- `\u002Fadd-office365` -- Office 365 Outlook (calendar, email, contacts)\n- `\u002Fadd-workiq` -- Work IQ (M365 Copilot Search)\n\n## Workflow\n\n1. Check Memory Bank → 2. Identify Connector → 3. Add Connector → 4. Inspect & Configure → 5. Build → 6. Update Memory Bank\n\n---\n\n### Step 1: Check Memory Bank\n\nCheck for `memory-bank.md` per [shared-instructions.md](..\u002F..\u002Fshared\u002Fshared-instructions.md).\n\n### Step 2: Identify Connector\n\n**If `$ARGUMENTS` is provided or the caller already specified the connector**, use it directly and skip the question below.\n\nOtherwise, ask the user which connector they want to add. Browse available connectors: [Connector Reference](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fconnectors\u002Fconnector-reference\u002F)\n\n**Before proceeding, check if the connector has a dedicated skill. If it does, delegate immediately and STOP:**\n\n| Connector API name          | Delegate to        |\n| --------------------------- | ------------------ |\n| `shared_a365copilotchatmcp` | `\u002Fadd-workiq`      |\n| `sharepointonline`          | `\u002Fadd-sharepoint`  |\n| `teams`                     | `\u002Fadd-teams`       |\n| `excelonlinebusiness`       | `\u002Fadd-excel`       |\n| `onedriveforbusiness`       | `\u002Fadd-onedrive`    |\n| `visualstudioteamservices`  | `\u002Fadd-azuredevops` |\n| `office365`                 | `\u002Fadd-office365`   |\n| `commondataservice`         | `\u002Fadd-dataverse`   |\n\nMatch the API name with or without the `shared_` prefix (`pa connector list` shows it with the prefix, e.g. `shared_teams`).\n\nInvoke the appropriate skill with the same `$ARGUMENTS` and **do not continue this skill's workflow**.\n\nCommon connector API names:\n\n- `sharepointonline`, `teams`, `excelonlinebusiness`, `onedriveforbusiness`\n- `visualstudioteamservices` (Azure DevOps), `azureblob`, `azurequeues`\n- `office365`, `office365users`, `office365groups`\n- `sql`, `commondataservice`\n\n### Step 3: Add Connector\n\nGet the connection as described in [connector-reference.md](..\u002F..\u002Fshared\u002Fconnector-reference.md#connections). On CLI 1.3.0+ (`PA_INLINE_CONNECTIONS=yes`), tell the user a connection may be created with their account, run the add without `-c` and with `--non-interactive`, and handle the result with the outcome table there. On older CLIs, run `\u002Flist-connections` first to find the connection ID (if none exists, create one with `pa connection create` as described in connector-reference.md) and pass `-c \u003Cconnection-id>`.\n\n```bash\n# CLI 1.3.0+, connectors that only have actions (Teams, Office 365 Outlook, Azure DevOps, ...):\n# the CLI finds or creates the connection\npa app add data-source --connector \u003Cconnector-api-name> --non-interactive\n\n# CLI 1.3.0+, connectors that also support tables (SharePoint, SQL Server, Excel): choose\n# --as action (or a table, below). Without either, --non-interactive fails on the missing choice.\npa app add data-source --connector \u003Cconnector-api-name> --as action --non-interactive\n\n# Older CLIs: pass the connection ID\npa app add data-source --connector \u003Cconnector-api-name> -c \u003Cconnection-id>\n\n# Tables (SharePoint, Excel, SQL, etc.) on any CLI: dataset and table, plus the connection ID used to find them\npa app add data-source --connector \u003Cconnector-api-name> -c \u003Cconnection-id> -d '\u003Cdataset>' --table '\u003Ctable>'\n```\n\nTo check whether a connector also supports tables, read `isTabular` from `pa connector list --search '\u003Cconnector name>' --json`.\n\nFinding a table's dataset and name (`pa connection list-datasets` \u002F `list-tables`) needs a connection ID: unlike `add data-source`, these commands don't find or create connections, and without `-c` they fail in non-interactive mode. So for tables, look the connection up first, even on CLI 1.3.0+ (`pa connection list --search \u003Cconnector-api-name> --json`).\n\n**Parameter reference:**\n\n- `--connector` (apiId) -- connector name (e.g., `sharepointonline`, `teams`). On the flat `power-apps` binary this is `--api-id`\u002F`-a`.\n- `-c` (connectionId) -- required on CLIs older than 1.3.0. On 1.3.0+ it's optional: without it the CLI reuses or creates the connection (see connector-reference.md). Get IDs from `\u002Flist-connections`.\n- `-d` (dataset) -- required for tabular datasources (e.g., SharePoint site URL, SQL database). Not needed for Dataverse.\n- `--table` (table) -- table\u002Flist name for tabular datasources (e.g., SharePoint list, Dataverse table logical name). On the flat `power-apps` binary this is `--resource-name`\u002F`-t`.\n- `--as` -- `table` or `action`, for connectors that support both (CLI 1.2.0+). Use `--as action` to add the connector's actions instead of a table.\n- `--use-sso` -- use a single sign-on connection (CLI 1.3.0+). Ask the user first; see connector-reference.md.\n- `--non-interactive` -- the CLI never prompts; it fails with a message that says what's missing instead. Pass it on every add on CLI 1.3.0+: if the CLI runs in a real terminal, it would otherwise show prompts the agent can't answer, such as the connection picker when `-c` is omitted.\n\n### Step 4: Inspect & Configure\n\nAfter adding, inspect the generated files. **Generated service files can be very large** -- use `Grep` to find specific methods instead of reading the entire file:\n\n```\nGrep pattern=\"async \\w+\" path=\"src\u002Fgenerated\u002Fservices\u002F\u003CConnector>Service.ts\"\n```\n\nFiles to check:\n\n- `src\u002Fgenerated\u002Fservices\u002F\u003CConnector>Service.ts` -- available operations and their parameters\n- `src\u002Fgenerated\u002Fmodels\u002F\u003CConnector>Model.ts` -- TypeScript interfaces (if generated)\n- `.power\u002Fschemas\u002F\u003Cconnector>\u002F` -- connector schema and configuration\n\nFor each method the user needs:\n\n1. Grep for the method name to find its signature\n2. Read just that method's section (use `offset` and `limit` parameters on Read)\n3. Identify required vs optional parameters and response type\n\nHelp the user write code using the generated service methods.\n\n### Step 5: Build\n\n```bash\nnpm run build\n```\n\nFix TypeScript errors before proceeding. Do NOT deploy yet.\n\n### Step 6: Update Memory Bank\n\nUpdate `memory-bank.md` with: connector added, configured operations, build status.\n","**? Shared Instructions: [shared-instructions.md](..\u002F..\u002Fshared\u002Fshared-instructions.md)** - Cross-cutting concerns.\n\n# Add Connector (Generic)\n\nFallback skill for any connector not covered by a specific `\u002Fadd-*` skill. For common connectors, prefer the dedicated skills:\n\n- `\u002Fadd-dataverse` -- Dataverse tables\n- `\u002Fadd-azuredevops` -- Azure DevOps\n- `\u002Fadd-teams` -- Microsoft Teams\n- `\u002Fadd-excel` -- Excel Online (Business)\n- `\u002Fadd-onedrive` -- OneDrive for Business\n- `\u002Fadd-sharepoint` -- SharePoint Online\n- `\u002Fadd-office365` -- Office 365 Outlook (calendar, email, contacts)\n- `\u002Fadd-workiq` -- Work IQ (M365 Copilot Search)\n\n## Workflow\n\n1. Check Memory Bank → 2. Identify Connector → 3. Add Connector → 4. Inspect & Configure → 5. Build → 6. Update Memory Bank\n\n---\n\n### Step 1: Check Memory Bank\n\nCheck for `memory-bank.md` per [shared-instructions.md](..\u002F..\u002Fshared\u002Fshared-instructions.md).\n\n### Step 2: Identify Connector\n\n**If `$ARGUMENTS` is provided or the caller already specified the connector**, use it directly and skip the question below.\n\nOtherwise, ask the user which connector they want to add. Browse available connectors: [Connector Reference](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fconnectors\u002Fconnector-reference\u002F)\n\n**Before proceeding, check if the connector has a dedicated skill. If it does, delegate immediately and STOP:**\n\n| Connector API name          | Delegate to        |\n| --------------------------- | ------------------ |\n| `shared_a365copilotchatmcp` | `\u002Fadd-workiq`      |\n| `sharepointonline`          | `\u002Fadd-sharepoint`  |\n| `teams`                     | `\u002Fadd-teams`       |\n| `excelonlinebusiness`       | `\u002Fadd-excel`       |\n| `onedriveforbusiness`       | `\u002Fadd-onedrive`    |\n| `visualstudioteamservices`  | `\u002Fadd-azuredevops` |\n| `office365`                 | `\u002Fadd-office365`   |\n| `commondataservice`         | `\u002Fadd-dataverse`   |\n\nMatch the API name with or without the `shared_` prefix (`pa connector list` shows it with the prefix, e.g. `shared_teams`).\n\nInvoke the appropriate skill with the same `$ARGUMENTS` and **do not continue this skill's workflow**.\n\nCommon connector API names:\n\n- `sharepointonline`, `teams`, `excelonlinebusiness`, `onedriveforbusiness`\n- `visualstudioteamservices` (Azure DevOps), `azureblob`, `azurequeues`\n- `office365`, `office365users`, `office365groups`\n- `sql`, `commondataservice`\n\n### Step 3: Add Connector\n\nGet the connection as described in [connector-reference.md](..\u002F..\u002Fshared\u002Fconnector-reference.md#connections). On CLI 1.3.0+ (`PA_INLINE_CONNECTIONS=yes`), tell the user a connection may be created with their account, run the add without `-c` and with `--non-interactive`, and handle the result with the outcome table there. On older CLIs, run `\u002Flist-connections` first to find the connection ID (if none exists, create one with `pa connection create` as described in connector-reference.md) and pass `-c \u003Cconnection-id>`.\n\n```bash\n# CLI 1.3.0+, connectors that only have actions (Teams, Office 365 Outlook, Azure DevOps, ...):\n# the CLI finds or creates the connection\npa app add data-source --connector \u003Cconnector-api-name> --non-interactive\n\n# CLI 1.3.0+, connectors that also support tables (SharePoint, SQL Server, Excel): choose\n# --as action (or a table, below). Without either, --non-interactive fails on the missing choice.\npa app add data-source --connector \u003Cconnector-api-name> --as action --non-interactive\n\n# Older CLIs: pass the connection ID\npa app add data-source --connector \u003Cconnector-api-name> -c \u003Cconnection-id>\n\n# Tables (SharePoint, Excel, SQL, etc.) on any CLI: dataset and table, plus the connection ID used to find them\npa app add data-source --connector \u003Cconnector-api-name> -c \u003Cconnection-id> -d '\u003Cdataset>' --table '\u003Ctable>'\n```\n\nTo check whether a connector also supports tables, read `isTabular` from `pa connector list --search '\u003Cconnector name>' --json`.\n\nFinding a table's dataset and name (`pa connection list-datasets` \u002F `list-tables`) needs a connection ID: unlike `add data-source`, these commands don't find or create connections, and without `-c` they fail in non-interactive mode. So for tables, look the connection up first, even on CLI 1.3.0+ (`pa connection list --search \u003Cconnector-api-name> --json`).\n\n**Parameter reference:**\n\n- `--connector` (apiId) -- connector name (e.g., `sharepointonline`, `teams`). On the flat `power-apps` binary this is `--api-id`\u002F`-a`.\n- `-c` (connectionId) -- required on CLIs older than 1.3.0. On 1.3.0+ it's optional: without it the CLI reuses or creates the connection (see connector-reference.md). Get IDs from `\u002Flist-connections`.\n- `-d` (dataset) -- required for tabular datasources (e.g., SharePoint site URL, SQL database). Not needed for Dataverse.\n- `--table` (table) -- table\u002Flist name for tabular datasources (e.g., SharePoint list, Dataverse table logical name). On the flat `power-apps` binary this is `--resource-name`\u002F`-t`.\n- `--as` -- `table` or `action`, for connectors that support both (CLI 1.2.0+). Use `--as action` to add the connector's actions instead of a table.\n- `--use-sso` -- use a single sign-on connection (CLI 1.3.0+). Ask the user first; see connector-reference.md.\n- `--non-interactive` -- the CLI never prompts; it fails with a message that says what's missing instead. Pass it on every add on CLI 1.3.0+: if the CLI runs in a real terminal, it would otherwise show prompts the agent can't answer, such as the connection picker when `-c` is omitted.\n\n### Step 4: Inspect & Configure\n\nAfter adding, inspect the generated files. **Generated service files can be very large** -- use `Grep` to find specific methods instead of reading the entire file:\n\n```\nGrep pattern=\"async \\w+\" path=\"src\u002Fgenerated\u002Fservices\u002F\u003CConnector>Service.ts\"\n```\n\nFiles to check:\n\n- `src\u002Fgenerated\u002Fservices\u002F\u003CConnector>Service.ts` -- available operations and their parameters\n- `src\u002Fgenerated\u002Fmodels\u002F\u003CConnector>Model.ts` -- TypeScript interfaces (if generated)\n- `.power\u002Fschemas\u002F\u003Cconnector>\u002F` -- connector schema and configuration\n\nFor each method the user needs:\n\n1. Grep for the method name to find its signature\n2. Read just that method's section (use `offset` and `limit` parameters on Read)\n3. Identify required vs optional parameters and response type\n\nHelp the user write code using the generated service methods.\n\n### Step 5: Build\n\n```bash\nnpm run build\n```\n\nFix TypeScript errors before proceeding. Do NOT deploy yet.\n\n### Step 6: Update Memory Bank\n\nUpdate `memory-bank.md` with: connector added, configured operations, build status.\n",{"name":5,"model":49,"description":7,"allowed-tools":50,"user-invocable":51},"sonnet","Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill",true,"main","9d26fde082b47f04e9bb97cb30a46dd1eaaa776e","plugins\u002Fcode-apps\u002Fskills\u002Fadd-connector",232,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills","https:\u002F\u002Fmicrosoft.github.io\u002Fpower-platform-skills\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 21:46:39",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":51},[64,67,70],{"tool":65,"command":66},"npx","npx skills add microsoft\u002Fpower-platform-skills --skill add-connector",{"tool":68,"command":69},"bunx","bunx skills add microsoft\u002Fpower-platform-skills --skill add-connector",{"tool":71,"command":72},"pnpm","pnpm dlx skills add microsoft\u002Fpower-platform-skills --skill add-connector","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-apps\u002Fskills\u002Fadd-connector\u002FSKILL.md",[],[76,84,104,126,144,158],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"01M78JN2BFRRV1J54Q6WKZQ08D","compare-site-configurations","Compare Power Pages site configurations between two environments, such as dev, test and production, or between a local download and the live site, and explain which differences change site behavior. Use when a site works in one environment but not another (for example, works in dev but fails in test), to check configuration drift before promoting or deploying, or to see what changed between two sites. Produces a shareable HTML report and a JSON file that VS Code can import.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fcompare-site-configurations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":44},"01M699WVHX0XN59EPBTTPEKYPG","setup","Use when Process Intelligence needs building, explicit cloud\u002Faccount\u002Fenvironment configuration, sign-in, connection diagnostics, or recovery from an authentication error.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fsetup\u002FSKILL.md",[],[86,91,92,93,94,95,96,97,98,99,40,100,101,102,38,103],"configuration","diagnostics","error","environment","cloud","when","connection","authentication","use","recovery","process","sign","intelligence",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":115,"publishedAt":44},"01M699WSR9EX55YY1WD9J22FEG","report-issue","Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Freport-issue\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[116,117,118,119,99,96,120,121,101,122,103,123,124,29,125],"issue","report","report issue","bug-report","operation","draft","bug","summary","user","support",{"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":44},"01M699WR26YQ9Q21KE6MJF5B2G","investigate-process","Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Finvestigate-process\u002FSKILL.md",[],[133,101,134,135,99,136,137,96,138,139,140,38,141,142,143],"investigate","investigate process","question","process mining","business","across","perspectives","mining","pattern","investigation","analytical",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":44},"01M699WP9SDG5ZR12P8VYNXKTN","derive-metric","Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fderive-metric\u002FSKILL.md",[],[151,152,153,154,155,156,99,96,157,38],"metric","derive metric","missing","formula","custom","reuse","saved",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":44},"01M699WMG5R8P6SMTDAS1TKF9E","compare-cohorts","Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fcompare-cohorts\u002FSKILL.md",[],[165,166,99,96,167,101,38],"compare","compare cohorts","results"]