[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CB8C0FSRZPQ8MDTWPZQAY9":3,"skill-same:01M7CB8C0FSRZPQ8MDTWPZQAY9":58},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7CB8C0FSRZPQ8MDTWPZQAY9","sf-datacloud-segment",null,"Salesforce Data Cloud Segment phase. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO\u002Fmapping\u002Fidentity-resolution work (use sf-datacloud-harmonize), activation work (use sf-datacloud-act), query\u002Fsearch-index work (use sf-datacloud-retrieve), or STDM\u002Fsession tracing (use sf-ai-agentforce-observability).","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-datacloud-segment\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-datacloud-segment\ndescription: >\n  Salesforce Data Cloud Segment phase.\n  TRIGGER when: user creates or publishes segments, manages calculated insights,\n  inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud.\n  DO NOT TRIGGER when: the task is DMO\u002Fmapping\u002Fidentity-resolution work (use sf-datacloud-harmonize),\n  activation work (use sf-datacloud-act), query\u002Fsearch-index work (use sf-datacloud-retrieve),\n  or STDM\u002Fsession tracing (use sf-ai-agentforce-observability).\nlicense: MIT\ncompatibility: \"Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org\"\nmetadata:\n  version: \"1.0.0\"\n  author: \"Gnanasekaran Thoppae\"\n  phase: \"Segment\"\n---\n\n# sf-datacloud-segment: Data Cloud Segment Phase\n\nUse this skill when the user needs **audience and insight work**: segments, calculated insights, publish workflows, member counts, or troubleshooting Data Cloud segment SQL.\n\n## When This Skill Owns the Task\n\nUse `sf-datacloud-segment` when the work involves:\n- `sf data360 segment *`\n- `sf data360 calculated-insight *`\n- segment publish workflows\n- member counts and segment troubleshooting\n- calculated insight execution and verification\n\nDelegate elsewhere when the user is:\n- still building DMOs, mappings, or identity resolution → [sf-datacloud-harmonize](..\u002Fsf-datacloud-harmonize\u002FSKILL.md)\n- activating a segment downstream → [sf-datacloud-act](..\u002Fsf-datacloud-act\u002FSKILL.md)\n- writing read-only SQL or search-index queries → [sf-datacloud-retrieve](..\u002Fsf-datacloud-retrieve\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias\n- unified DMO or base entity name\n- whether the user wants create, publish, inspect, or troubleshoot\n- whether the asset is a segment or calculated insight\n- expected success metric: member count, aggregate value, or publish status\n\n---\n\n## Core Operating Rules\n\n- Treat Data Cloud segment SQL as distinct from CRM SOQL.\n- Run the shared readiness classifier before mutating audience assets: `node ~\u002F.claude\u002Fskills\u002Fsf-datacloud\u002Fscripts\u002Fdiagnose-org.mjs -o \u003Corg> --phase segment --json`.\n- Prefer reusable JSON definitions for repeatable segment and CI creation.\n- Use `--api-version 64.0` when segment creation behavior is unstable on newer defaults.\n- Verify with counts or SQL after publish\u002Frun steps instead of assuming success.\n- Use SQL joins rather than `segment members` when readable member details are needed.\n\n---\n\n## Recommended Workflow\n\n### 1. Classify readiness for segment work\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fsf-datacloud\u002Fscripts\u002Fdiagnose-org.mjs -o \u003Corg> --phase segment --json\n```\n\n### 2. Inspect current state\n```bash\nsf data360 segment list -o \u003Corg> 2>\u002Fdev\u002Fnull\nsf data360 calculated-insight list -o \u003Corg> 2>\u002Fdev\u002Fnull\n```\n\n### 3. Create with reusable JSON definitions\n```bash\nsf data360 segment create -o \u003Corg> -f segment.json --api-version 64.0 2>\u002Fdev\u002Fnull\nsf data360 calculated-insight create -o \u003Corg> -f ci.json 2>\u002Fdev\u002Fnull\n```\n\n### 4. Publish or run explicitly\n```bash\nsf data360 segment publish -o \u003Corg> --name My_Segment 2>\u002Fdev\u002Fnull\nsf data360 calculated-insight run -o \u003Corg> --name Lifetime_Value 2>\u002Fdev\u002Fnull\n```\n\n### 5. Verify with counts or SQL\n```bash\nsf data360 segment count -o \u003Corg> --name My_Segment 2>\u002Fdev\u002Fnull\nsf data360 query sql -o \u003Corg> --sql 'SELECT COUNT(*) FROM \"UnifiedssotIndividualMain__dlm\"' 2>\u002Fdev\u002Fnull\n```\n\n---\n\n## High-Signal Gotchas\n\n- Segment creation can require `--api-version 64.0`.\n- `segment members` returns opaque IDs; use SQL joins when human-readable member details are needed.\n- Segment SQL is not SOQL.\n- Calculated insight assets and segment SQL have different limitations.\n- Publish\u002Frun steps may kick off asynchronous work even when the command returns quickly.\n- An empty segment or calculated-insight list usually means the module is reachable but unconfigured, not unavailable.\n\n---\n\n## Output Format\n\n```text\nSegment task: \u003Csegment \u002F calculated-insight>\nAction: \u003Ccreate \u002F publish \u002F inspect \u002F troubleshoot>\nTarget org: \u003Calias>\nArtifacts: \u003Cdefinition files \u002F commands>\nVerification: \u003Cmember count \u002F query result \u002F publish state>\nNext step: \u003Cact \u002F retrieve \u002F follow-up>\n```\n\n---\n\n## References\n\n- [README.md](README.md)\n- [..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fcalculated-insight.template.json](..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fcalculated-insight.template.json)\n- [..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fsegment.template.json](..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fsegment.template.json)\n- [..\u002Fsf-datacloud\u002Freferences\u002Ffeature-readiness.md](..\u002Fsf-datacloud\u002Freferences\u002Ffeature-readiness.md)\n- [..\u002Fsf-datacloud\u002FUPSTREAM.md](..\u002Fsf-datacloud\u002FUPSTREAM.md)\n","# sf-datacloud-segment: Data Cloud Segment Phase\n\nUse this skill when the user needs **audience and insight work**: segments, calculated insights, publish workflows, member counts, or troubleshooting Data Cloud segment SQL.\n\n## When This Skill Owns the Task\n\nUse `sf-datacloud-segment` when the work involves:\n- `sf data360 segment *`\n- `sf data360 calculated-insight *`\n- segment publish workflows\n- member counts and segment troubleshooting\n- calculated insight execution and verification\n\nDelegate elsewhere when the user is:\n- still building DMOs, mappings, or identity resolution → [sf-datacloud-harmonize](..\u002Fsf-datacloud-harmonize\u002FSKILL.md)\n- activating a segment downstream → [sf-datacloud-act](..\u002Fsf-datacloud-act\u002FSKILL.md)\n- writing read-only SQL or search-index queries → [sf-datacloud-retrieve](..\u002Fsf-datacloud-retrieve\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias\n- unified DMO or base entity name\n- whether the user wants create, publish, inspect, or troubleshoot\n- whether the asset is a segment or calculated insight\n- expected success metric: member count, aggregate value, or publish status\n\n---\n\n## Core Operating Rules\n\n- Treat Data Cloud segment SQL as distinct from CRM SOQL.\n- Run the shared readiness classifier before mutating audience assets: `node ~\u002F.claude\u002Fskills\u002Fsf-datacloud\u002Fscripts\u002Fdiagnose-org.mjs -o \u003Corg> --phase segment --json`.\n- Prefer reusable JSON definitions for repeatable segment and CI creation.\n- Use `--api-version 64.0` when segment creation behavior is unstable on newer defaults.\n- Verify with counts or SQL after publish\u002Frun steps instead of assuming success.\n- Use SQL joins rather than `segment members` when readable member details are needed.\n\n---\n\n## Recommended Workflow\n\n### 1. Classify readiness for segment work\n```bash\nnode ~\u002F.claude\u002Fskills\u002Fsf-datacloud\u002Fscripts\u002Fdiagnose-org.mjs -o \u003Corg> --phase segment --json\n```\n\n### 2. Inspect current state\n```bash\nsf data360 segment list -o \u003Corg> 2>\u002Fdev\u002Fnull\nsf data360 calculated-insight list -o \u003Corg> 2>\u002Fdev\u002Fnull\n```\n\n### 3. Create with reusable JSON definitions\n```bash\nsf data360 segment create -o \u003Corg> -f segment.json --api-version 64.0 2>\u002Fdev\u002Fnull\nsf data360 calculated-insight create -o \u003Corg> -f ci.json 2>\u002Fdev\u002Fnull\n```\n\n### 4. Publish or run explicitly\n```bash\nsf data360 segment publish -o \u003Corg> --name My_Segment 2>\u002Fdev\u002Fnull\nsf data360 calculated-insight run -o \u003Corg> --name Lifetime_Value 2>\u002Fdev\u002Fnull\n```\n\n### 5. Verify with counts or SQL\n```bash\nsf data360 segment count -o \u003Corg> --name My_Segment 2>\u002Fdev\u002Fnull\nsf data360 query sql -o \u003Corg> --sql 'SELECT COUNT(*) FROM \"UnifiedssotIndividualMain__dlm\"' 2>\u002Fdev\u002Fnull\n```\n\n---\n\n## High-Signal Gotchas\n\n- Segment creation can require `--api-version 64.0`.\n- `segment members` returns opaque IDs; use SQL joins when human-readable member details are needed.\n- Segment SQL is not SOQL.\n- Calculated insight assets and segment SQL have different limitations.\n- Publish\u002Frun steps may kick off asynchronous work even when the command returns quickly.\n- An empty segment or calculated-insight list usually means the module is reachable but unconfigured, not unavailable.\n\n---\n\n## Output Format\n\n```text\nSegment task: \u003Csegment \u002F calculated-insight>\nAction: \u003Ccreate \u002F publish \u002F inspect \u002F troubleshoot>\nTarget org: \u003Calias>\nArtifacts: \u003Cdefinition files \u002F commands>\nVerification: \u003Cmember count \u002F query result \u002F publish state>\nNext step: \u003Cact \u002F retrieve \u002F follow-up>\n```\n\n---\n\n## References\n\n- [README.md](README.md)\n- [..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fcalculated-insight.template.json](..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fcalculated-insight.template.json)\n- [..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fsegment.template.json](..\u002Fsf-datacloud\u002Fassets\u002Fdefinitions\u002Fsegment.template.json)\n- [..\u002Fsf-datacloud\u002Freferences\u002Ffeature-readiness.md](..\u002Fsf-datacloud\u002Freferences\u002Ffeature-readiness.md)\n- [..\u002Fsf-datacloud\u002FUPSTREAM.md](..\u002Fsf-datacloud\u002FUPSTREAM.md)\n",{"name":5,"license":15,"metadata":24,"description":28,"compatibility":29},{"phase":25,"author":26,"version":27},"Segment","Gnanasekaran Thoppae","1.0.0","Salesforce Data Cloud Segment phase. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO\u002Fmapping\u002Fidentity-resolution work (use sf-datacloud-harmonize), activation work (use sf-datacloud-act), query\u002Fsearch-index work (use sf-datacloud-retrieve), or STDM\u002Fsession tracing (use sf-ai-agentforce-observability).\n","Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-datacloud-segment",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-datacloud-segment",{"tool":44,"command":45},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-datacloud-segment",{"tool":47,"command":48},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-datacloud-segment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-datacloud-segment\u002FSkill.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"metadata.json","REFERENCE","参考文档",454,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-datacloud-segment\u002Fmetadata.json",[59,66,71,78,83,90],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":67,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":79,"name":73,"nameZh":6,"description":74,"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":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":91,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]