[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CCNT2XM4AYBJ9556XK6PKC":3,"skill-same:01M6CCNT2XM4AYBJ9556XK6PKC":74},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":50,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6CCNT2XM4AYBJ9556XK6PKC","mixpanel-headless-setup",null,"This skill installs mixpanel_headless, pandas, numpy, matplotlib, seaborn, networkx, anytree, scipy (and pyarrow on Python 3.11+), then verifies Mixpanel credentials. It should be invoked when setting up a new environment for Mixpanel data analysis, when dependencies are missing, or when configuring service account or OAuth credentials for the first time.","stigmer\u002Fstigmer","stigmer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255479904?v=4","01M6CCFBFXXRZC4ZVNS3JSDV4W","Stigmer","01M6CCFBKY7M8QGR4GH9TT35MY",9,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Fplugins\u002Fmixpanel-headless\u002Fskills\u002Fsetup\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"setup","mixpanel headless setup","data analysis","python","pandas","data","OAuth","first","analysis","matplotlib","networkx","credentials","seaborn","Bash","environment","up","2026-11-10 10:12:30",false,"---\nname: mixpanel-headless-setup\ndescription: This skill installs mixpanel_headless, pandas, numpy, matplotlib, seaborn, networkx, anytree, scipy (and pyarrow on Python 3.11+), then verifies Mixpanel credentials. It should be invoked when setting up a new environment for Mixpanel data analysis, when dependencies are missing, or when configuring service account or OAuth credentials for the first time.\ndisable-model-invocation: false\nallowed-tools: Bash\n---\n\n# mixpanel-headless — Setup\n\nInstall dependencies and verify credentials for CodeMode analytics.\n\n## Run Setup\n\nBefore running bundled scripts, set `SKILL_DIR` to the absolute path of this\n`skills\u002Fsetup` directory.\n\n```bash\nbash $SKILL_DIR\u002Fscripts\u002Fsetup.sh\n```\n\nThis will:\n1. Verify Python 3.10+ is available\n2. Install `mixpanel_headless`, `pandas`, `numpy`, `matplotlib`, `seaborn`, `networkx>=3.0`, `anytree>=2.8.0`, `scipy`, and `pyarrow>=17.0` on Python 3.11+ (tries uv, pip in order)\n3. Verify all packages import successfully (including pyarrow on 3.11+, networkx, anytree, and scipy)\n4. Check for configured Mixpanel credentials (single schema — Account → Project → Workspace)\n\n## Check Credentials\n\nAfter installation, check the active session:\n\n```bash\npython3 $SKILL_DIR\u002F..\u002Fmixpanelyst\u002Fscripts\u002Fauth_manager.py session\n```\n\nParse the JSON `state` field:\n- **`ok`** — credentials configured. Show `account.name` → project `project.id` and proceed to verification.\n- **`needs_account`** — no account configured. Read `next` for onboarding suggestions and follow \"If Credentials Are Missing\" below.\n- **`needs_project`** — account configured but no project pinned. Suggest `mp project list` then `mp project use \u003Cid>`.\n- **`error`** — show `error.message`. If `error.actionable` is true, the message names a concrete next command.\n\n## If Credentials Are Missing\n\nIf no credentials are configured, guide the user to one of these methods:\n\n### Recommended: `mp login`\n\nThe frictionless one-shot path. Tell the user to run:\n\n```bash\nmp login\n```\n\n`mp login` runs the right auth flow for the environment, derives the\naccount name from `\u002Fme`, and pins a default project. For laptops with a\nusable browser, this opens the PKCE flow; for environments with\n`MP_USERNAME` + `MP_SECRET` set, it skips the browser and uses the\nservice-account path; for `MP_OAUTH_TOKEN` set, it uses the static\nbearer.\n\nRegion behavior:\n- `service_account` and `oauth_token` paths probe `us → eu → in` when\n  `--region` is omitted.\n- `oauth_browser` (the bare-`mp login` default) defaults to `us`. EU and\n  India browser users must pass `--region eu` or `--region in`.\n\nUseful flags: `--name NAME`, `--region us|eu|in`, `--project ID`,\n`--service-account`, `--token-env VAR`, `--no-browser`, `--secret-stdin`.\n\n### Alternative: Guided Setup (explicit account add)\n\nUse the `mixpanel-auth` skill's account-add workflow for a\nstep-by-step walkthrough. The workflow never prompts for secrets in\nconversation — it instructs the user to run `mp account add ...`\nthemselves so the secret is read with hidden input. Use this path when\nthe user wants explicit control over the account name, region, and type\nat registration time.\n\n### Alternative: Service-Account Environment Variables (temporary)\n\nFor quick testing, set all four variables in the shell — the resolver\npicks them up directly without account registration:\n\n```bash\nexport MP_USERNAME=\"service-account-username\"\nexport MP_SECRET=\"service-account-secret\"\nexport MP_PROJECT_ID=\"12345\"\nexport MP_REGION=\"us\"  # or \"eu\", \"in\"\n```\n\n### Alternative: Raw OAuth Bearer Token (best for agents \u002F CI)\n\nIf the user has an OAuth 2.0 access token from another source, they can use\nit directly without the PKCE browser flow:\n\n```bash\nexport MP_OAUTH_TOKEN=\"\u003Cbearer-token>\"\nexport MP_PROJECT_ID=\"12345\"\nexport MP_REGION=\"us\"  # or \"eu\", \"in\"\n```\n\nThis is the recommended mode for non-interactive contexts. The full\nservice-account env-var set (`MP_USERNAME` + `MP_SECRET` + `MP_PROJECT_ID`\n+ `MP_REGION`) takes precedence when both sets are complete.\n\n## Remote Environment\n\nIf running inside a remote or sandboxed agent environment, credentials work differently:\n\n- **OAuth login and interactive account setup are NOT available** (no browser, no host terminal access)\n- Credentials must be configured on the **host machine** before starting the remote session\n\n### If No Credentials Found in the Remote Session\n\nTell the user:\n\n> No Mixpanel credentials found in this remote session.\n>\n> On your **host machine** (outside the remote session), run:\n> ```\n> mp account export-bridge --to ~\u002F.claude\u002Fmixpanel\u002Fauth.json\n> ```\n> This writes a v2 bridge file embedding your account record (and any\n> oauth_browser tokens) so the remote session can read your credentials\n> at startup.\n>\n> Then **start a new remote session** — credentials will be available automatically.\n\nDo NOT suggest the account-login or account-add interactive workflows — these won't work inside remote sessions without browser or terminal access.\n\n### If Bridge File Found But Token Expired\n\nThe library will auto-refresh the OAuth token via the on-disk refresh\ntoken (no browser needed). If refresh fails:\n\n> Your OAuth session has expired and could not be refreshed.\n> On your host machine, run:\n> ```\n> mp login --name personal             # re-authenticate (or `mp account login personal`)\n> mp account export-bridge --to ~\u002F.claude\u002Fmixpanel\u002Fauth.json\n> ```\n> Then start a new remote session.\n\n## Verify Everything Works\n\n```bash\npython3 $SKILL_DIR\u002F..\u002Fmixpanelyst\u002Fscripts\u002Fauth_manager.py account test\n```\n\nThe subcommand never raises — read `result.ok` to determine outcome.\n- `result.ok: true` → setup is complete; the user can ask analytics questions.\n- `result.ok: false` → suggest the `mixpanel-auth` account-test workflow for detailed diagnostics.\n\n## Post-Setup: Explore Your Data\n\nOnce authenticated, these slash commands help orient the user:\n\n- `mixpanel-auth` project-list workflow — discover all accessible projects via `\u002Fme`\n- `mixpanel-auth` session workflow — see active account \u002F project \u002F workspace\n- `mixpanel-auth` project-use workflow — switch to a different project\n- `mixpanel-auth` target-add workflow — save a named cursor position\n\nThe user can also construct a Workspace targeting a specific account \u002F project \u002F\nworkspace directly:\n\n```python\nimport mixpanel_headless as mp\n\nws = mp.Workspace()                                  # default session\nws = mp.Workspace(account=\"team\")                    # named account\nws = mp.Workspace(project=\"67890\")                   # explicit project (active account)\nws = mp.Workspace(account=\"team\", project=\"67890\")   # both axes\nws.use(project=\"98765\").events()                     # in-session switch (no re-auth)\n```\n\n_The mixpanelyst skill auto-triggers on analytics questions. For the analytical frameworks that guide investigations, see [analytical-frameworks.md](..\u002Fmixpanelyst\u002Freferences\u002Fanalytical-frameworks.md). For the complete Python API, see [python-api.md](..\u002Fmixpanelyst\u002Freferences\u002Fpython-api.md)._\n","# mixpanel-headless — Setup\n\nInstall dependencies and verify credentials for CodeMode analytics.\n\n## Run Setup\n\nBefore running bundled scripts, set `SKILL_DIR` to the absolute path of this\n`skills\u002Fsetup` directory.\n\n```bash\nbash $SKILL_DIR\u002Fscripts\u002Fsetup.sh\n```\n\nThis will:\n1. Verify Python 3.10+ is available\n2. Install `mixpanel_headless`, `pandas`, `numpy`, `matplotlib`, `seaborn`, `networkx>=3.0`, `anytree>=2.8.0`, `scipy`, and `pyarrow>=17.0` on Python 3.11+ (tries uv, pip in order)\n3. Verify all packages import successfully (including pyarrow on 3.11+, networkx, anytree, and scipy)\n4. Check for configured Mixpanel credentials (single schema — Account → Project → Workspace)\n\n## Check Credentials\n\nAfter installation, check the active session:\n\n```bash\npython3 $SKILL_DIR\u002F..\u002Fmixpanelyst\u002Fscripts\u002Fauth_manager.py session\n```\n\nParse the JSON `state` field:\n- **`ok`** — credentials configured. Show `account.name` → project `project.id` and proceed to verification.\n- **`needs_account`** — no account configured. Read `next` for onboarding suggestions and follow \"If Credentials Are Missing\" below.\n- **`needs_project`** — account configured but no project pinned. Suggest `mp project list` then `mp project use \u003Cid>`.\n- **`error`** — show `error.message`. If `error.actionable` is true, the message names a concrete next command.\n\n## If Credentials Are Missing\n\nIf no credentials are configured, guide the user to one of these methods:\n\n### Recommended: `mp login`\n\nThe frictionless one-shot path. Tell the user to run:\n\n```bash\nmp login\n```\n\n`mp login` runs the right auth flow for the environment, derives the\naccount name from `\u002Fme`, and pins a default project. For laptops with a\nusable browser, this opens the PKCE flow; for environments with\n`MP_USERNAME` + `MP_SECRET` set, it skips the browser and uses the\nservice-account path; for `MP_OAUTH_TOKEN` set, it uses the static\nbearer.\n\nRegion behavior:\n- `service_account` and `oauth_token` paths probe `us → eu → in` when\n  `--region` is omitted.\n- `oauth_browser` (the bare-`mp login` default) defaults to `us`. EU and\n  India browser users must pass `--region eu` or `--region in`.\n\nUseful flags: `--name NAME`, `--region us|eu|in`, `--project ID`,\n`--service-account`, `--token-env VAR`, `--no-browser`, `--secret-stdin`.\n\n### Alternative: Guided Setup (explicit account add)\n\nUse the `mixpanel-auth` skill's account-add workflow for a\nstep-by-step walkthrough. The workflow never prompts for secrets in\nconversation — it instructs the user to run `mp account add ...`\nthemselves so the secret is read with hidden input. Use this path when\nthe user wants explicit control over the account name, region, and type\nat registration time.\n\n### Alternative: Service-Account Environment Variables (temporary)\n\nFor quick testing, set all four variables in the shell — the resolver\npicks them up directly without account registration:\n\n```bash\nexport MP_USERNAME=\"service-account-username\"\nexport MP_SECRET=\"service-account-secret\"\nexport MP_PROJECT_ID=\"12345\"\nexport MP_REGION=\"us\"  # or \"eu\", \"in\"\n```\n\n### Alternative: Raw OAuth Bearer Token (best for agents \u002F CI)\n\nIf the user has an OAuth 2.0 access token from another source, they can use\nit directly without the PKCE browser flow:\n\n```bash\nexport MP_OAUTH_TOKEN=\"\u003Cbearer-token>\"\nexport MP_PROJECT_ID=\"12345\"\nexport MP_REGION=\"us\"  # or \"eu\", \"in\"\n```\n\nThis is the recommended mode for non-interactive contexts. The full\nservice-account env-var set (`MP_USERNAME` + `MP_SECRET` + `MP_PROJECT_ID`\n+ `MP_REGION`) takes precedence when both sets are complete.\n\n## Remote Environment\n\nIf running inside a remote or sandboxed agent environment, credentials work differently:\n\n- **OAuth login and interactive account setup are NOT available** (no browser, no host terminal access)\n- Credentials must be configured on the **host machine** before starting the remote session\n\n### If No Credentials Found in the Remote Session\n\nTell the user:\n\n> No Mixpanel credentials found in this remote session.\n>\n> On your **host machine** (outside the remote session), run:\n> ```\n> mp account export-bridge --to ~\u002F.claude\u002Fmixpanel\u002Fauth.json\n> ```\n> This writes a v2 bridge file embedding your account record (and any\n> oauth_browser tokens) so the remote session can read your credentials\n> at startup.\n>\n> Then **start a new remote session** — credentials will be available automatically.\n\nDo NOT suggest the account-login or account-add interactive workflows — these won't work inside remote sessions without browser or terminal access.\n\n### If Bridge File Found But Token Expired\n\nThe library will auto-refresh the OAuth token via the on-disk refresh\ntoken (no browser needed). If refresh fails:\n\n> Your OAuth session has expired and could not be refreshed.\n> On your host machine, run:\n> ```\n> mp login --name personal             # re-authenticate (or `mp account login personal`)\n> mp account export-bridge --to ~\u002F.claude\u002Fmixpanel\u002Fauth.json\n> ```\n> Then start a new remote session.\n\n## Verify Everything Works\n\n```bash\npython3 $SKILL_DIR\u002F..\u002Fmixpanelyst\u002Fscripts\u002Fauth_manager.py account test\n```\n\nThe subcommand never raises — read `result.ok` to determine outcome.\n- `result.ok: true` → setup is complete; the user can ask analytics questions.\n- `result.ok: false` → suggest the `mixpanel-auth` account-test workflow for detailed diagnostics.\n\n## Post-Setup: Explore Your Data\n\nOnce authenticated, these slash commands help orient the user:\n\n- `mixpanel-auth` project-list workflow — discover all accessible projects via `\u002Fme`\n- `mixpanel-auth` session workflow — see active account \u002F project \u002F workspace\n- `mixpanel-auth` project-use workflow — switch to a different project\n- `mixpanel-auth` target-add workflow — save a named cursor position\n\nThe user can also construct a Workspace targeting a specific account \u002F project \u002F\nworkspace directly:\n\n```python\nimport mixpanel_headless as mp\n\nws = mp.Workspace()                                  # default session\nws = mp.Workspace(account=\"team\")                    # named account\nws = mp.Workspace(project=\"67890\")                   # explicit project (active account)\nws = mp.Workspace(account=\"team\", project=\"67890\")   # both axes\nws.use(project=\"98765\").events()                     # in-session switch (no re-auth)\n```\n\n_The mixpanelyst skill auto-triggers on analytics questions. For the analytical frameworks that guide investigations, see [analytical-frameworks.md](..\u002Fmixpanelyst\u002Freferences\u002Fanalytical-frameworks.md). For the complete Python API, see [python-api.md](..\u002Fmixpanelyst\u002Freferences\u002Fpython-api.md)._\n",{"name":5,"description":7,"allowed-tools":37,"disable-model-invocation":41},"main","49002d2ddc1f123a8d1148f6c6d73d7b385bb0b1","plugins\u002Fmixpanel-headless\u002Fskills\u002Fsetup",6,"https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer","https:\u002F\u002Fstigmer.ai","https:\u002F\u002Fgithub.com\u002Fstigmer","The open-source backend for the agents in your product.","2026-11-14 02:41:36",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add stigmer\u002Fstigmer --skill mixpanel-headless-setup",{"tool":60,"command":61},"bunx","bunx skills add stigmer\u002Fstigmer --skill mixpanel-headless-setup",{"tool":63,"command":64},"pnpm","pnpm dlx skills add stigmer\u002Fstigmer --skill mixpanel-headless-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Fplugins\u002Fmixpanel-headless\u002Fskills\u002Fsetup\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fsetup.sh","SCRIPT","脚本",6101,"https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Fplugins\u002Fmixpanel-headless\u002Fskills\u002Fsetup\u002Fscripts\u002Fsetup.sh",[75,103,123,141,154,165],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":92,"publishedAt":40},"01M6CCSERKR4YRSZJ2TB6B0X60","writing-hookify-rules","This skill should be used when the user asks to \"create a hookify rule\", \"write a hook rule\", \"configure hookify\", \"add a hookify rule\", or needs guidance on hookify rule syntax and patterns.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fsupport\u002Ffixtures\u002Fclaude-plugins\u002Fhookify\u002Fskills\u002Fwriting-rules\u002FSKILL.md",[81,84,87],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[93,94,95,96,97,98,99,100,101,102],"writing","Writing Hookify Rules","Rules","hookify rules","create","guidance","user","write","configure","syntax",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":115,"publishedAt":40},"01M6CCSC63RKCGC2S1EZDEMXZE","sql-migrations","Write safe database schema migrations - reversible steps, online index builds, and backfills in batches.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fsql-migrations\u002FSKILL.md",[109,112],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":113,"categoryName":114,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000033","数据分析师",[116,117,118,119,100,120,121,122],"sql","sql migrations","migrations","schema","index","database","safe",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":40},"01M6CCS9Q8E0R3TYHPZHCPN0JZ","repo-conventions","How to change Go code in this repository - error wrapping, table-driven tests, doc comments, no new dependencies, and running go test before finishing.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Frepo-conventions\u002FSKILL.md",[],[130,131,132,133,134,135,136,137,138,139,140],"repo","repo conventions","table","go","test","change","doc comments","code","repository","doc","how",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":40},"01M6CCS7F2D1YZ9H3N63XTEV09","incident-postmortem","Write a blameless incident postmortem - timeline, impact, root cause, contributing factors and follow-up actions with owners.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fincident-postmortem\u002FSKILL.md",[],[148,149,100,150,151,152,153,39],"incident postmortem","postmortem","contributing","actions","timeline","owners",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":162,"publishedAt":40},"01M6CCS4W1D2K257KHC40HS8JG","data-analysis","Summarise a data export or table - lead with the key finding and give every number its baseline or comparison.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fdata-analysis\u002FSKILL.md",[160,161],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":113,"categoryName":114,"taxonomyType":90,"taxonomyTypeDesc":91},[32,26,29,163,132,164],"baseline","export",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":40},"01M6CCS2MNQYK9S24AYHJAVPWF","customer-support","Answer customer questions about orders, returns and refunds from the written policies and the order system, ending with a clear next step.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fcustomer-support\u002FSKILL.md",[],[172,173,174,175,176,177],"support","customer","customer support","system","refunds","returns"]