[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBFAVMGYY0Y8518M625X0J":3,"skill-same:01M7CBFAVMGYY0Y8518M625X0J":56},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CBFAVMGYY0Y8518M625X0J","sf-industry-commoncore-omnistudio-analyze",null,"Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, or requests dependency diagrams. DO NOT TRIGGER when: authoring OmniScripts (use sf-industry-commoncore-omniscript), building FlexCards (use sf-industry-commoncore-flexcard), creating Integration Procedures (use sf-industry-commoncore-integration-procedure), or configuring Data Mappers (use sf-industry-commoncore-datamapper).","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-industry-commoncore-omnistudio-analyze\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-industry-commoncore-omnistudio-analyze\ndescription: >\n  Cross-cutting OmniStudio analysis skill for namespace detection, dependency\n  visualization, and impact analysis across OmniScripts, FlexCards, Integration\n  Procedures, and Data Mappers.\n  TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection\n  (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, or requests\n  dependency diagrams.\n  DO NOT TRIGGER when: authoring OmniScripts (use sf-industry-commoncore-omniscript), building FlexCards\n  (use sf-industry-commoncore-flexcard), creating Integration Procedures (use sf-industry-commoncore-integration-procedure),\n  or configuring Data Mappers (use sf-industry-commoncore-datamapper).\nlicense: MIT\nmetadata:\n  version: \"1.0.0\"\n  author: \"David Ryan (weytani)\"\n---\n\n# sf-industry-commoncore-omnistudio-analyze: OmniStudio Cross-Component Analysis\n\nExpert OmniStudio analyst specializing in namespace detection, dependency mapping, and impact analysis across the full OmniStudio component suite. Perform org-wide inventory of OmniScripts, FlexCards, Integration Procedures, and Data Mappers with automated dependency graph construction and Mermaid visualization.\n\n## Core Responsibilities\n\n1. **Namespace Detection**: Identify whether an org uses Core (Industries), vlocity_cmt (Communications, Media & Energy), or vlocity_ins (Insurance & Health) namespace\n2. **Dependency Analysis**: Build directed graphs of cross-component dependencies using BFS traversal with circular reference detection\n3. **Impact Analysis**: Determine which components are affected when a given OmniScript, IP, FlexCard, or Data Mapper changes\n4. **Mermaid Visualization**: Generate dependency diagrams in Mermaid syntax for documentation and review\n5. **Org-Wide Inventory**: Catalog all OmniStudio components by type, status, language, and version\n\n---\n\n> **CRITICAL: Orchestration Order**\n>\n> When multiple OmniStudio skills are involved, follow this dependency chain:\n>\n> `sf-industry-commoncore-omnistudio-analyze` → `sf-industry-commoncore-datamapper` → `sf-industry-commoncore-integration-procedure` → `sf-industry-commoncore-omniscript` → `sf-industry-commoncore-flexcard`\n>\n> This skill runs first to establish namespace context and dependency maps that downstream skills consume.\n\n---\n\n## Key Insights\n\n| Insight | Detail |\n|---------|--------|\n| Three namespaces coexist | Core (OmniProcess), vlocity_cmt (vlocity_cmt__OmniScript__c), vlocity_ins (vlocity_ins__OmniScript__c) |\n| Dependencies are stored in JSON | PropertySetConfig (elements), Definition (FlexCards), InputObjectName\u002FOutputObjectName (Data Mappers) |\n| Circular references are possible | OmniScript A → IP B → OmniScript A via embedded call |\n| FlexCard data sources are typed | `dataSource.type === 'IntegrationProcedures'` (plural) in DataSourceConfig JSON |\n| Active vs Draft matters | Only active components participate in runtime dependency chains |\n\n---\n\n## Workflow (4-Phase Pattern)\n\n### Phase 1: Namespace Detection\n\n**Purpose**: Determine which OmniStudio namespace the org uses before querying any component metadata.\n\n**Detection Algorithm** — Probe objects in order until a successful COUNT() returns:\n\n1. **Core (Industries namespace)**:\n   ```soql\n   SELECT COUNT() FROM OmniProcess\n   ```\n   If this succeeds, the org uses the Core namespace (API 234.0+ \u002F Spring '22+).\n\n2. **vlocity_cmt (Communications, Media & Energy)**:\n   ```soql\n   SELECT COUNT() FROM vlocity_cmt__OmniScript__c\n   ```\n\n3. **vlocity_ins (Insurance & Health)**:\n   ```soql\n   SELECT COUNT() FROM vlocity_ins__OmniScript__c\n   ```\n\nIf none succeed, OmniStudio is not installed in the org.\n\n**CLI Commands for namespace detection**:\n```bash\n# Core namespace probe\nsf data query --query \"SELECT COUNT() FROM OmniProcess\" --target-org myorg --json 2>\u002Fdev\u002Fnull\n\n# vlocity_cmt namespace probe\nsf data query --query \"SELECT COUNT() FROM vlocity_cmt__OmniScript__c\" --target-org myorg --json 2>\u002Fdev\u002Fnull\n\n# vlocity_ins namespace probe\nsf data query --query \"SELECT COUNT() FROM vlocity_ins__OmniScript__c\" --target-org myorg --json 2>\u002Fdev\u002Fnull\n```\n\n**Evaluate results**: A successful query (exit code 0 with `totalSize` in JSON) confirms the namespace. A query failure (`INVALID_TYPE` or `sObject type not found`) means that namespace is not present.\n\n**See**: [references\u002Fnamespace-guide.md](references\u002Fnamespace-guide.md) for complete object\u002Ffield mapping across all three namespaces.\n\n---\n\n### Phase 2: Component Discovery\n\n**Purpose**: Build an inventory of all OmniStudio components in the org.\n\nUsing the detected namespace, query each component type:\n\n**OmniScripts** (Core example):\n```soql\nSELECT Id, Type, SubType, Language, IsActive, VersionNumber,\n       PropertySetConfig, LastModifiedDate\nFROM OmniProcess\nWHERE IsIntegrationProcedure = false\nORDER BY Type, SubType, Language, VersionNumber DESC\n```\n\n**Integration Procedures** (Core example):\n```soql\nSELECT Id, Type, SubType, Language, IsActive, VersionNumber,\n       PropertySetConfig, LastModifiedDate\nFROM OmniProcess\nWHERE IsIntegrationProcedure = true\nORDER BY Type, SubType, Language, VersionNumber DESC\n```\n\n**FlexCards** (Core example):\n```soql\nSELECT Id, Name, IsActive, DataSourceConfig, PropertySetConfig,\n       AuthorName, LastModifiedDate\nFROM OmniUiCard\nORDER BY Name\n```\n\n> **IMPORTANT**: The `OmniUiCard` object does NOT have a `Definition` field. Use `DataSourceConfig` for data source bindings and `PropertySetConfig` for card layout\u002Fstates configuration.\n\n**Data Mappers** (Core example):\n```soql\nSELECT Id, Name, IsActive, Type, LastModifiedDate\nFROM OmniDataTransform\nORDER BY Name\n```\n\n**Data Mapper Items** (for object dependency extraction):\n```soql\nSELECT Id, OmniDataTransformationId, InputObjectName, OutputObjectName,\n       InputObjectQuerySequence\nFROM OmniDataTransformItem\nWHERE OmniDataTransformationId IN ({datamapper_ids})\n```\n\n> **IMPORTANT**: The foreign key field is `OmniDataTransformationId` (full word \"Transformation\"), NOT `OmniDataTransformId`.\n\n**CLI Command pattern**:\n```bash\nsf data query --query \"SELECT Id, Type, SubType, Language, IsActive FROM OmniProcess WHERE IsIntegrationProcedure = false\" \\\n  --target-org myorg --json\n```\n\n---\n\n### Phase 3: Dependency Analysis\n\n**Purpose**: Parse component metadata to build a directed dependency graph.\n\n#### Algorithm: BFS with Circular Detection\n\n```\n1. Initialize empty graph G and visited set V\n2. For each root component C:\n   a. Enqueue C into work queue Q\n   b. While Q is not empty:\n      i.   Dequeue component X from Q\n      ii.  If X is in V, record circular reference and skip\n      iii. Add X to V\n      iv.  Parse X's metadata for dependency references\n      v.   For each dependency D found:\n           - Add edge X → D to graph G\n           - If D is not in V, enqueue D into Q\n3. Return graph G and any circular references detected\n```\n\n#### Element Type → Dependency Extraction\n\nOmniScript and IP elements store references in the `PropertySetConfig` JSON field. Parse each element to extract dependencies:\n\n| Element Type | JSON Path in PropertySetConfig | Dependency Target |\n|-------------|-------------------------------|-------------------|\n| DataRaptor Transform Action | `bundle`, `bundleName` | Data Mapper (by name) |\n| DataRaptor Turbo Action | `bundle`, `bundleName` | Data Mapper (by name) |\n| Remote Action | `remoteClass`, `remoteMethod` | Apex Class.Method |\n| Integration Procedure Action | `integrationProcedureKey` | IP (Type_SubType) |\n| OmniScript Action | `omniScriptKey` or `Type\u002FSubType` | OmniScript (Type_SubType) |\n| HTTP Action | `httpUrl`, `httpMethod` | External endpoint (URL) |\n| DocuSign Envelope Action | `docuSignTemplateId` | DocuSign template |\n| Apex Remote Action | `remoteClass` | Apex Class |\n\n**Parsing PropertySetConfig**:\n```\nFor each OmniProcessElement:\n  1. Read PropertySetConfig (JSON string)\n  2. Parse JSON\n  3. Check element.Type against extraction table\n  4. Extract referenced component name\u002Fkey\n  5. Resolve reference to an OmniProcess\u002FOmniDataTransform record\n  6. Add edge: parent component → referenced component\n```\n\n#### FlexCard Data Source Parsing\n\nFlexCards store their data source configuration in the `DataSourceConfig` JSON field (NOT `Definition` — that field does not exist on `OmniUiCard`):\n\n```\nParse DataSourceConfig JSON:\n  1. Access dataSource object (singular, not array)\n  2. For each dataSource where type === 'IntegrationProcedures' (note: PLURAL):\n     - Extract dataSource.value.ipMethod (IP Type_SubType)\n     - Add edge: FlexCard → Integration Procedure\n  3. For each dataSource where type === 'ApexRemote':\n     - Extract dataSource.value.className\n     - Add edge: FlexCard → Apex Class\n  4. For childCard references, parse PropertySetConfig:\n     - Add edge: FlexCard → child FlexCard\n```\n\n> **IMPORTANT**: The data source type for IPs is `IntegrationProcedures` (plural with capital P), not `IntegrationProcedure`.\n\n#### Data Mapper Object Dependencies\n\nData Mappers reference Salesforce objects via their items:\n\n```\nFor each OmniDataTransformItem:\n  1. Read InputObjectName → source sObject\n  2. Read OutputObjectName → target sObject\n  3. Add edge: Data Mapper → sObject (read from InputObjectName)\n  4. Add edge: Data Mapper → sObject (write to OutputObjectName)\n```\n\n**See**: [references\u002Fdependency-patterns.md](references\u002Fdependency-patterns.md) for complete dependency extraction rules and examples.\n\n---\n\n### Phase 4: Visualization & Reporting\n\n**Purpose**: Generate human-readable output from the dependency graph.\n\n#### Output Format 1: Mermaid Dependency Diagram\n\n```mermaid\ngraph LR\n    subgraph OmniScripts\n        OS1[\"createOrder\u003Cbr\u002F>English v3\"]\n        OS2[\"updateAccount\u003Cbr\u002F>English v1\"]\n    end\n    subgraph Integration Procedures\n        IP1[\"fetchAccountData\u003Cbr\u002F>English v2\"]\n        IP2[\"submitOrder\u003Cbr\u002F>English v1\"]\n    end\n    subgraph Data Mappers\n        DM1[\"AccountExtract\"]\n        DM2[\"OrderTransform\"]\n    end\n    subgraph FlexCards\n        FC1[\"AccountSummaryCard\"]\n    end\n\n    OS1 -->|IP Action| IP2\n    OS1 -->|DR Action| DM2\n    OS2 -->|IP Action| IP1\n    IP1 -->|DR Action| DM1\n    FC1 -->|Data Source| IP1\n\n    style OS1 fill:#dbeafe,stroke:#1d4ed8,color:#1f2937\n    style OS2 fill:#dbeafe,stroke:#1d4ed8,color:#1f2937\n    style IP1 fill:#fef3c7,stroke:#b45309,color:#1f2937\n    style IP2 fill:#fef3c7,stroke:#b45309,color:#1f2937\n    style DM1 fill:#d1fae5,stroke:#047857,color:#1f2937\n    style DM2 fill:#d1fae5,stroke:#047857,color:#1f2937\n    style FC1 fill:#fce7f3,stroke:#be185d,color:#1f2937\n```\n\n**Color scheme**:\n\n| Component Type | Fill | Stroke |\n|---------------|------|--------|\n| OmniScript | `#dbeafe` (blue-100) | `#1d4ed8` (blue-700) |\n| Integration Procedure | `#fef3c7` (amber-100) | `#b45309` (amber-700) |\n| Data Mapper | `#d1fae5` (green-100) | `#047857` (green-700) |\n| FlexCard | `#fce7f3` (pink-100) | `#be185d` (pink-700) |\n| Apex Class | `#e9d5ff` (purple-100) | `#7c3aed` (purple-700) |\n| External (HTTP) | `#f1f5f9` (slate-100) | `#475569` (slate-600) |\n\n#### Output Format 2: JSON Summary\n\n```json\n{\n  \"namespace\": \"Core\",\n  \"components\": {\n    \"omniScripts\": 12,\n    \"integrationProcedures\": 8,\n    \"flexCards\": 5,\n    \"dataMappers\": 15\n  },\n  \"dependencies\": [\n    { \"from\": \"OS:createOrder\", \"to\": \"IP:submitOrder\", \"type\": \"IPAction\" },\n    { \"from\": \"IP:fetchAccountData\", \"to\": \"DM:AccountExtract\", \"type\": \"DataRaptorAction\" }\n  ],\n  \"circularReferences\": [],\n  \"impactAnalysis\": {\n    \"DM:AccountExtract\": {\n      \"directDependents\": [\"IP:fetchAccountData\"],\n      \"transitiveDependents\": [\"OS:updateAccount\", \"FC:AccountSummaryCard\"]\n    }\n  }\n}\n```\n\n#### Output Format 3: Human-Readable Report\n\n```\nOmniStudio Dependency Report\n=============================\nOrg Namespace: Core (Industries)\nScan Date: 2026-03-06\n\nComponent Inventory:\n  OmniScripts:              12 (8 active, 4 draft)\n  Integration Procedures:    8 (6 active, 2 draft)\n  FlexCards:                  5 (5 active)\n  Data Mappers:             15 (12 active, 3 draft)\n\nDependency Summary:\n  Total edges:              23\n  Circular references:       0\n  Orphaned components:       2 (no inbound\u002Foutbound deps)\n\nImpact Analysis (most-depended components):\n  1. DM:AccountExtract       → 5 dependents\n  2. IP:fetchAccountData     → 3 dependents\n  3. DM:OrderTransform       → 2 dependents\n```\n\n---\n\n## Namespace Object\u002FField Mapping\n\nComplete mapping of OmniStudio objects and fields across all three namespaces:\n\n### Primary Objects\n\n| Concept | Core | vlocity_cmt | vlocity_ins |\n|---------|------|-------------|-------------|\n| OmniScript \u002F IP container | `OmniProcess` | `vlocity_cmt__OmniScript__c` | `vlocity_ins__OmniScript__c` |\n| OmniScript \u002F IP elements | `OmniProcessElement` | `vlocity_cmt__Element__c` | `vlocity_ins__Element__c` |\n| FlexCard | `OmniUiCard` | `vlocity_cmt__VlocityUITemplate__c` | `vlocity_ins__VlocityUITemplate__c` |\n| Data Mapper | `OmniDataTransform` | `vlocity_cmt__DRBundle__c` | `vlocity_ins__DRBundle__c` |\n| Data Mapper Item | `OmniDataTransformItem` | `vlocity_cmt__DRMapItem__c` | `vlocity_ins__DRMapItem__c` |\n\n### Key Fields\n\n| Concept | Core Field | vlocity_cmt Field | vlocity_ins Field |\n|---------|-----------|-------------------|-------------------|\n| Script type | `Type` | `vlocity_cmt__Type__c` | `vlocity_ins__Type__c` |\n| Script subtype | `SubType` | `vlocity_cmt__SubType__c` | `vlocity_ins__SubType__c` |\n| Language | `Language` | `vlocity_cmt__Language__c` | `vlocity_ins__Language__c` |\n| Is active | `IsActive` | `vlocity_cmt__IsActive__c` | `vlocity_ins__IsActive__c` |\n| Version | `VersionNumber` | `vlocity_cmt__Version__c` | `vlocity_ins__Version__c` |\n| Element config | `PropertySetConfig` | `vlocity_cmt__PropertySet__c` | `vlocity_ins__PropertySet__c` |\n| Is Integration Procedure | `IsIntegrationProcedure` | `vlocity_cmt__IsIntegrationProcedure__c` | `vlocity_ins__IsIntegrationProcedure__c` |\n| FlexCard data sources | `DataSourceConfig` | `vlocity_cmt__Definition__c` | `vlocity_ins__Definition__c` |\n| FlexCard layout\u002Fstates | `PropertySetConfig` | (same field) | (same field) |\n| DM input object | `InputObjectName` (on Item) | `vlocity_cmt__InterfaceObject__c` | `vlocity_ins__InterfaceObject__c` |\n| DM output object | `OutputObjectName` (on Item) | `vlocity_cmt__TargetFieldObjectType__c` | `vlocity_ins__TargetFieldObjectType__c` |\n\n**See**: [references\u002Fnamespace-guide.md](references\u002Fnamespace-guide.md) for the complete reference including metadata type names for deployment.\n\n---\n\n## CLI Commands Reference\n\n### Namespace Detection\n```bash\n# Probe all three namespaces (run sequentially, first success wins)\nsf data query --query \"SELECT COUNT() FROM OmniProcess\" --target-org myorg --json 2>\u002Fdev\u002Fnull && echo \"CORE\" || \\\nsf data query --query \"SELECT COUNT() FROM vlocity_cmt__OmniScript__c\" --target-org myorg --json 2>\u002Fdev\u002Fnull && echo \"VLOCITY_CMT\" || \\\nsf data query --query \"SELECT COUNT() FROM vlocity_ins__OmniScript__c\" --target-org myorg --json 2>\u002Fdev\u002Fnull && echo \"VLOCITY_INS\" || \\\necho \"NOT_INSTALLED\"\n```\n\n### Component Inventory (Core Namespace)\n```bash\n# Count OmniScripts\nsf data query --query \"SELECT COUNT() FROM OmniProcess WHERE IsIntegrationProcedure = false\" \\\n  --target-org myorg --json\n\n# Count Integration Procedures\nsf data query --query \"SELECT COUNT() FROM OmniProcess WHERE IsIntegrationProcedure = true\" \\\n  --target-org myorg --json\n\n# Count FlexCards\nsf data query --query \"SELECT COUNT() FROM OmniUiCard\" --target-org myorg --json\n\n# Count Data Mappers\nsf data query --query \"SELECT COUNT() FROM OmniDataTransform\" --target-org myorg --json\n```\n\n### Dependency Data Extraction (Core Namespace)\n```bash\n# Get OmniScript elements with their config\nsf data query --query \"SELECT Id, OmniProcessId, Name, Type, PropertySetConfig FROM OmniProcessElement WHERE OmniProcessId = '{process_id}'\" \\\n  --target-org myorg --json\n\n# Get FlexCard data sources (for dependency parsing)\nsf data query --query \"SELECT Id, Name, DataSourceConfig FROM OmniUiCard WHERE IsActive = true\" \\\n  --target-org myorg --json\n\n# Get Data Mapper items (for object dependencies)\nsf data query --query \"SELECT Id, OmniDataTransformationId, InputObjectName, OutputObjectName FROM OmniDataTransformItem\" \\\n  --target-org myorg --json\n```\n\n---\n\n## Cross-Skill Integration\n\n| Skill | Relationship | How This Skill Helps |\n|-------|-------------|---------------------|\n| sf-industry-commoncore-datamapper | Provides namespace and object dependency data | Data Mapper authoring uses detected namespace for correct API names |\n| sf-industry-commoncore-integration-procedure | Provides namespace and IP dependency map | IP authoring uses dependency graph to avoid circular references |\n| sf-industry-commoncore-omniscript | Provides namespace and element dependency data | OmniScript authoring uses namespace-correct field names |\n| sf-industry-commoncore-flexcard | Provides namespace and data source dependency map | FlexCard authoring uses detected IP references for validation |\n| sf-diagram-mermaid | Consumes dependency graph for visualization | This skill generates Mermaid output compatible with sf-diagram-mermaid styling |\n| sf-metadata | Provides sObject metadata for Data Mapper analysis | Object field validation during dependency extraction |\n| sf-deploy | Deployment uses namespace-correct metadata types | This skill provides the correct metadata type names per namespace |\n\n---\n\n## Edge Cases\n\n| Scenario | Handling |\n|----------|---------|\n| Mixed namespace org (migration in progress) | Probe all three namespaces; report if multiple return results. Components may exist under both old and migrated namespaces. |\n| Inactive components with dependencies | Include in dependency graph but mark as inactive. Warn if active component depends on inactive one. |\n| Large orgs (1000+ components) | Use SOQL pagination (LIMIT\u002FOFFSET or queryMore). Process in batches of 200. |\n| PropertySetConfig exceeds SOQL field length | Use Tooling API or REST API to fetch full JSON body for elements with truncated config. |\n| Circular dependency detected | Log the cycle path (A → B → C → A), mark all participating edges, continue traversal for remaining branches. |\n| Components referencing deleted items | Record as \"broken reference\" in output. Flag for cleanup. |\n| Version conflicts (multiple active versions) | Only the highest active version number participates in runtime. Warn if lower versions have unique dependencies. |\n\n---\n\n## Notes\n\n- **Dependencies**: Requires `sf` CLI with org authentication. Optional: sf-diagram-mermaid for styled visualization.\n- **Namespace must be detected first**: All downstream queries depend on knowing the correct object and field API names.\n- **PropertySetConfig is the key**: Nearly all dependency information lives in this JSON field on OmniProcessElement records.\n- **DataSourceConfig for FlexCards**: Data sources are in `DataSourceConfig`, NOT a `Definition` field (which does not exist on `OmniUiCard`). Card layout\u002Fstates are in `PropertySetConfig`.\n- **Data Mapper items contain object references**: InputObjectName and OutputObjectName on OmniDataTransformItem records reveal which sObjects a Data Mapper reads from and writes to. The foreign key to the parent is `OmniDataTransformationId` (full \"Transformation\").\n- **IsIntegrationProcedure is the discriminator**: `OmniProcess` uses a boolean `IsIntegrationProcedure` field, not a `TypeCategory` field (which does not exist). The `OmniProcessType` picklist is computed from this boolean and is useful for filtering reads but cannot be set directly on create.\n- **sf data create record limitations**: The `--values` flag cannot handle JSON strings in textarea fields (e.g., PropertySetConfig). Use `sf api request rest --method POST --body @file.json` instead for records with JSON configuration.\n- **Install related skills**: `\u002Fplugin install github:Jaganpro\u002Fsf-skills\u002Fsf-industry-commoncore-datamapper`, `\u002Fplugin install github:Jaganpro\u002Fsf-skills\u002Fsf-industry-commoncore-integration-procedure`, `\u002Fplugin install github:Jaganpro\u002Fsf-skills\u002Fsf-industry-commoncore-omniscript`, `\u002Fplugin install github:Jaganpro\u002Fsf-skills\u002Fsf-industry-commoncore-flexcard`\n\n---\n\n## License\n\nMIT License.\nCopyright (c) 2026 David Ryan (weytani)\n","# sf-industry-commoncore-omnistudio-analyze: OmniStudio Cross-Component Analysis\n\nExpert OmniStudio analyst specializing in namespace detection, dependency mapping, and impact analysis across the full OmniStudio component suite. Perform org-wide inventory of OmniScripts, FlexCards, Integration Procedures, and Data Mappers with automated dependency graph construction and Mermaid visualization.\n\n## Core Responsibilities\n\n1. **Namespace Detection**: Identify whether an org uses Core (Industries), vlocity_cmt (Communications, Media & Energy), or vlocity_ins (Insurance & Health) namespace\n2. **Dependency Analysis**: Build directed graphs of cross-component dependencies using BFS traversal with circular reference detection\n3. **Impact Analysis**: Determine which components are affected when a given OmniScript, IP, FlexCard, or Data Mapper changes\n4. **Mermaid Visualization**: Generate dependency diagrams in Mermaid syntax for documentation and review\n5. **Org-Wide Inventory**: Catalog all OmniStudio components by type, status, language, and version\n\n---\n\n> **CRITICAL: Orchestration Order**\n>\n> When multiple OmniStudio skills are involved, follow this dependency chain:\n>\n> `sf-industry-commoncore-omnistudio-analyze` → `sf-industry-commoncore-datamapper` → `sf-industry-commoncore-integration-procedure` → `sf-industry-commoncore-omniscript` → `sf-industry-commoncore-flexcard`\n>\n> This skill runs first to establish namespace context and dependency maps that downstream skills consume.\n\n---\n\n## Key Insights\n\n| Insight | Detail |\n|---------|--------|\n| Three namespaces coexist | Core (OmniProcess), vlocity_cmt (vlocity_cmt__OmniScript__c), vlocity_ins (vlocity_ins__OmniScript__c) |\n| Dependencies are stored in JSON | PropertySetConfig (elements), Definition (FlexCards), InputObjectName\u002FOutputObjectName (Data Mappers) |\n| Circular references are possible | OmniScript A → IP B → OmniScript A via embedded call |\n| FlexCard data sources are typed | `dataSource.type === 'IntegrationProcedures'` (plural) in DataSourceConfig JSON |\n| Active vs Draft matters | Only active components participate in runtime dependency chains |\n\n---\n\n## Workflow (4-Phase Pattern)\n\n### Phase 1: Namespace Detection\n\n**Purpose**: Determine which OmniStudio namespace the org uses before querying any component metadata.\n\n**Detection Algorithm** — Probe objects in order until a successful COUNT() returns:\n\n1. **Core (Industries namespace)**:\n   ```soql\n   SELECT COUNT() FROM OmniProcess\n   ```\n   If this succeeds, the org uses the Core namespace (API 234.0+ \u002F Spring '22+).\n\n2. **vlocity_cmt (Communications, Media & Energy)**:\n   ```soql\n   SELECT COUNT() FROM vlocity_cmt__OmniScript__c\n   ```\n\n3. **vlocity_ins (Insurance & Health)**:\n   ```soql\n   SELECT COUNT() FROM vlocity_ins__OmniScript__c\n   ```\n\nIf none succeed, OmniStudio is not installed in the org.\n\n**CLI Commands for namespace detection**:\n```bash\n# Core namespace probe\nsf data query --query \"SELECT COUNT() FROM OmniProcess\" --target-org myorg --json 2>\u002Fdev\u002Fnull\n\n# vlocity_cmt namespace probe\nsf data query --query \"SELECT COUNT() FROM vlocity_cmt__OmniScript__c\" --target-org myorg --json 2>\u002Fdev\u002Fnull\n\n# vlocity_ins namespace probe\nsf data query --query \"SELECT COUNT() FROM vlocity_ins__OmniScript__c\" --target-org myorg --json 2>\u002Fdev\u002Fnull\n```\n\n**Evaluate results**: A successful query (exit code 0 with `totalSize` in JSON) confirms the namespace. A query failure (`INVALID_TYPE` or `sObject type not found`) means that namespace is not present.\n\n**See**: [references\u002Fnamespace-guide.md](references\u002Fnamespace-guide.md) for complete object\u002Ffield mapping across all three namespaces.\n\n---\n\n### Phase 2: Component Discovery\n\n**Purpose**: Build an inventory of all OmniStudio components in the org.\n\nUsing the detected namespace, query each component type:\n\n**OmniScripts** (Core example):\n```soql\nSELECT Id, Type, SubType, Language, IsActive, VersionNumber,\n       PropertySetConfig, LastModifiedDate\nFROM OmniProcess\nWHERE IsIntegrationProcedure = false\nORDER BY Type, SubType, Language, VersionNumber DESC\n```\n\n**Integration Procedures** (Core example):\n```soql\nSELECT Id, Type, SubType, Language, IsActive, VersionNumber,\n       PropertySetConfig, LastModifiedDate\nFROM OmniProcess\nWHERE IsIntegrationProcedure = true\nORDER BY Type, SubType, Language, VersionNumber DESC\n```\n\n**FlexCards** (Core example):\n```soql\nSELECT Id, Name, IsActive, DataSourceConfig, PropertySetConfig,\n       AuthorName, LastModifiedDate\nFROM OmniUiCard\nORDER BY Name\n```\n\n> **IMPORTANT**: The `OmniUiCard` object does NOT have a `Definition` field. Use `DataSourceConfig` for data source bindings and `PropertySetConfig` for card layout\u002Fstates configuration.\n\n**Data Mappers** (Core example):\n```soql\nSELECT Id, Name, IsActive, Type, LastModifiedDate\nFROM OmniDataTransform\nORDER BY Name\n```\n\n**Data Mapper Items** (for object dependency extraction):\n```soql\nSELECT Id, OmniDataTransformationId, InputObjectName, OutputObjectName,\n       InputObjectQuerySequence\nFROM OmniDataTransformItem\nWHERE OmniDataTransformationId IN ({datamapper_ids})\n```\n\n> **IMPORTANT**: The foreign key field is `OmniDataTransformationId` (full word \"Transformation\"), NOT `OmniDataTransformId`.\n\n**CLI Command pattern**:\n```bash\nsf data query --query \"SELECT Id, Type, SubType, Language, IsActive FROM OmniProcess WHERE IsIntegrationProcedure = false\" \\\n  --target-org myorg --json\n```\n\n---\n\n### Phase 3: Dependency Analysis\n\n**Purpose**: Parse component metadata to build a directed dependency graph.\n\n#### Algorithm: BFS with Circular Detection\n\n```\n1. Initialize empty graph G and visited set V\n2. For each root component C:\n   a. Enqueue C into work queue Q\n   b. While Q is not empty:\n      i.   Dequeue component X from Q\n      ii.  If X is in V, record circular reference and skip\n      iii. Add X to V\n      iv.  Parse X's metadata for dependency references\n      v.   For each dependency D found:\n           - Add edge X → D to graph G\n           - If D is not in V, enqueue D into Q\n3. Return graph G and any circular references detected\n```\n\n#### Element Type → Dependency Extraction\n\nOmniScript and IP elements store references in the `PropertySetConfig` JSON field. Parse each element to extract dependencies:\n\n| Element Type | JSON Path in PropertySetConfig | Dependency Target |\n|-------------|-------------------------------|-------------------|\n| DataRaptor Transform Action | `bundle`, `bundleName` | Data Mapper (by name) |\n| DataRaptor Turbo Action | `bundle`, `bundleName` | Data Mapper (by name) |\n| Remote Action | `remoteClass`, `remoteMethod` | Apex Class.Method |\n| Integration Procedure Action | `integrationProcedureKey` | IP (Type_SubType) |\n| OmniScript Action | `omniScriptKey` or `Type\u002FSubType` | OmniScript (Type_SubType) |\n| HTTP Action | `httpUrl`, `httpMethod` | External endpoint (URL) |\n| DocuSign Envelope Action | `docuSignTemplateId` | DocuSign template |\n| Apex Remote Action | `remoteClass` | Apex Class |\n\n**Parsing PropertySetConfig**:\n```\nFor each OmniProcessElement:\n  1. Read PropertySetConfig (JSON string)\n  2. Parse JSON\n  3. Check element.Type against extraction table\n  4. Extract referenced component name\u002Fkey\n  5. Resolve reference to an OmniProcess\u002FOmniDataTransform record\n  6. Add edge: parent component → referenced component\n```\n\n#### FlexCard Data Source Parsing\n\nFlexCards store their data source configuration in the `DataSourceConfig` JSON field (NOT `Definition` — that field does not exist on `OmniUiCard`):\n\n```\nParse DataSourceConfig JSON:\n  1. Access dataSource object (singular, not array)\n  2. For each dataSource where type === 'IntegrationProcedures' (note: PLURAL):\n     - Extract dataSource.value.ipMethod (IP Type_SubType)\n     - Add edge: FlexCard → Integration Procedure\n  3. For each dataSource where type === 'ApexRemote':\n     - Extract dataSource.value.className\n     - Add edge: FlexCard → Apex Class\n  4. For childCard references, parse PropertySetConfig:\n     - Add edge: FlexCard → child FlexCard\n```\n\n> **IMPORTANT**: The data source type for IPs is `IntegrationProcedures` (plural with capital P), not `IntegrationProcedure`.\n\n#### Data Mapper Object Dependencies\n\nData Mappers reference Salesforce objects via their items:\n\n```\nFor each OmniDataTransformItem:\n  1. Read InputObjectName → source sObject\n  2. Read OutputObjectName → target sObject\n  3. Add edge: Data Mapper → sObject (read from InputObjectName)\n  4. Add edge: Data Mapper → sObject (write to OutputObjectName)\n```\n\n**See**: [references\u002Fdependency-patterns.md](references\u002Fdependency-patterns.md) for complete dependency extraction rules and examples.\n\n---\n\n### Phase 4: Visualization & Reporting\n\n**Purpose**: Generate human-readable output from the dependency graph.\n\n#### Output Format 1: Mermaid Dependency Diagram\n\n```mermaid\ngraph LR\n    subgraph OmniScripts\n        OS1[\"createOrder\u003Cbr\u002F>English v3\"]\n        OS2[\"updateAccount\u003Cbr\u002F>English v1\"]\n    end\n    subgraph Integration Procedures\n        IP1[\"fetchAccountData\u003Cbr\u002F>English v2\"]\n        IP2[\"submitOrder\u003Cbr\u002F>English v1\"]\n    end\n    subgraph Data Mappers\n        DM1[\"AccountExtract\"]\n        DM2[\"OrderTransform\"]\n    end\n    subgraph FlexCards\n        FC1[\"AccountSummaryCard\"]\n    end\n\n    OS1 -->|IP Action| IP2\n    OS1 -->|DR Action| DM2\n    OS2 -->|IP Action| IP1\n    IP1 -->|DR Action| DM1\n    FC1 -->|Data Source| IP1\n\n    style OS1 fill:#dbeafe,stroke:#1d4ed8,color:#1f2937\n    style OS2 fill:#dbeafe,stroke:#1d4ed8,color:#1f2937\n    style IP1 fill:#fef3c7,stroke:#b45309,color:#1f2937\n    style IP2 fill:#fef3c7,stroke:#b45309,color:#1f2937\n    style DM1 fill:#d1fae5,stroke:#047857,color:#1f2937\n    style DM2 fill:#d1fae5,stroke:#047857,color:#1f2937\n    style FC1 fill:#fce7f3,stroke:#be185d,color:#1f2937\n```\n\n**Color scheme**:\n\n| Component Type | Fill | Stroke |\n|---------------|------|--------|\n| OmniScript | `#dbeafe` (blue-100) | `#1d4ed8` (blue-700) |\n| Integration Procedure | `#fef3c7` (amber-100) | `#b45309` (amber-700) |\n| Data Mapper | `#d1fae5` (green-100) | `#047857` (green-700) |\n| FlexCard | `#fce7f3` (pink-100) | `#be185d` (pink-700) |\n| Apex Class | `#e9d5ff` (purple-100) | `#7c3aed` (purple-700) |\n| External (HTTP) | `#f1f5f9` (slate-100) | `#475569` (slate-600) |\n\n#### Output Format 2: JSON Summary\n\n```json\n{\n  \"namespace\": \"Core\",\n  \"components\": {\n    \"omniScripts\": 12,\n    \"integrationProcedures\": 8,\n    \"flexCards\": 5,\n    \"dataMappers\": 15\n  },\n  \"dependencies\": [\n    { \"from\": \"OS:createOrder\", \"to\": \"IP:submitOrder\", \"type\": \"IPAction\" },\n    { \"from\": \"IP:fetchAccountData\", \"to\": \"DM:AccountExtract\", \"type\": \"DataRaptorAction\" }\n  ],\n  \"circularReferences\": [],\n  \"impactAnalysis\": {\n    \"DM:AccountExtract\": {\n      \"directDependents\": [\"IP:fetchAccountData\"],\n      \"transitiveDependents\": [\"OS:updateAccount\", \"FC:AccountSummaryCard\"]\n    }\n  }\n}\n```\n\n#### Output Format 3: Human-Readable Report\n\n```\nOmniStudio Dependency Report\n=============================\nOrg Namespace: Core (Industries)\nScan Date: 2026-03-06\n\nComponent Inventory:\n  OmniScripts:              12 (8 active, 4 draft)\n  Integration Procedures:    8 (6 active, 2 draft)\n  FlexCards:                  5 (5 active)\n  Data Mappers:             15 (12 active, 3 draft)\n\nDependency Summary:\n  Total edges:              23\n  Circular references:       0\n  Orphaned components:       2 (no inbound\u002Foutbound deps)\n\nImpact Analysis (most-depended components):\n  1. DM:AccountExtract       → 5 dependents\n  2. IP:fetchAccountData     → 3 dependents\n  3. DM:OrderTransform       → 2 dependents\n```\n\n---\n\n## Namespace Object\u002FField Mapping\n\nComplete mapping of OmniStudio objects and fields across all three namespaces:\n\n### Primary Objects\n\n| Concept | Core | vlocity_cmt | vlocity_ins |\n|---------|------|-------------|-------------|\n| OmniScript \u002F IP container | `OmniProcess` | `vlocity_cmt__OmniScript__c` | `vlocity_ins__OmniScript__c` |\n| OmniScript \u002F IP elements | `OmniProcessElement` | `vlocity_cmt__Element__c` | `vlocity_ins__Element__c` |\n| FlexCard | `OmniUiCard` | `vlocity_cmt__VlocityUITemplate__c` | `vlocity_ins__VlocityUITemplate__c` |\n| Data Mapper | `OmniDataTransform` | `vlocity_cmt__DRBundle__c` | `vlocity_ins__DRBundle__c` |\n| Data Mapper Item | `OmniDataTransformItem` | `vlocity_cmt__DRMapItem__c` | `vlocity_ins__DRMapItem__c` |\n\n### Key Fields\n\n| Concept | Core Field | vlocity_cmt Field | vlocity_ins Field |\n|---------|-----------|-------------------|-------------------|\n| Script type | `Type` | `vlocity_cmt__Type__c` | `vlocity_ins__Type__c` |\n| Script subtype | `SubType` | `vlocity_cmt__SubType__c` | `vlocity_ins__SubType__c` |\n| Language | `Language` | `vlocity_cmt__Language__c` | `vlocity_ins__Language__c` |\n| Is active | `IsActive` | `vlocity_cmt__IsActive__c` | `vlocity_ins__IsActive__c` |\n| Version | `VersionNumber` | `vlocity_cmt__Version__c` | `vlocity_ins__Version__c` |\n| Element config | `PropertySetConfig` | `vlocity_cmt__PropertySet__c` | `vlocity_ins__PropertySet__c` |\n| Is Integration Procedure | `IsIntegrationProcedure` | `vlocity_cmt__IsIntegrationProcedure__c` | `vlocity_ins__IsIntegrationProcedure__c` |\n| FlexCard data sources | `DataSourceConfig` | `vlocity_cmt__Definition__c` | `vlocity_ins__Definition__c` |\n| FlexCard layout\u002Fstates | `PropertySetConfig` | (same field) | (same field) |\n| DM input object | `InputObjectName` (on Item) | `vlocity_cmt__InterfaceObject__c` | `vlocity_ins__InterfaceObject__c` |\n| DM output object | `OutputObjectName` (on Item) | `vlocity_cmt__TargetFieldObjectType__c` | `vlocity_ins__TargetFieldObjectType__c` |\n\n**See**: [references\u002Fnamespace-guide.md](references\u002Fnamespace-guide.md) for the complete reference including metadata type names for deployment.\n\n---\n\n## CLI Commands Reference\n\n### Namespace Detection\n```bash\n# Probe all three namespaces (run sequentially, first success wins)\nsf data query --query \"SELECT COUNT() FROM OmniProcess\" --target-org myorg --json 2>\u002Fdev\u002Fnull && echo \"CORE\" || \\\nsf data query --query \"SELECT COUNT() FROM vlocity_cmt__OmniScript__c\" --target-org myorg --json 2>\u002Fdev\u002Fnull && echo \"VLOCITY_CMT\" || \\\nsf data query --query \"SELECT COUNT() FROM vlocity_ins__OmniScript__c\" --target-org myorg --json 2>\u002Fdev\u002Fnull && echo \"VLOCITY_INS\" || \\\necho \"NOT_INSTALLED\"\n```\n\n### Component Inventory (Core Namespace)\n```bash\n# Count OmniScripts\nsf data query --query \"SELECT COUNT() FROM OmniProcess WHERE IsIntegrationProcedure = false\" \\\n  --target-org myorg --json\n\n# Count Integration Procedures\nsf data query --query \"SELECT COUNT() FROM OmniProcess WHERE IsIntegrationProcedure = true\" \\\n  --target-org myorg --json\n\n# Count FlexCards\nsf data query --query \"SELECT COUNT() FROM OmniUiCard\" --target-org myorg --json\n\n# Count Data Mappers\nsf data query --query \"SELECT COUNT() FROM OmniDataTransform\" --target-org myorg --json\n```\n\n### Dependency Data Extraction (Core Namespace)\n```bash\n# Get OmniScript elements with their config\nsf data query --query \"SELECT Id, OmniProcessId, Name, Type, PropertySetConfig FROM OmniProcessElement WHERE OmniProcessId = '{process_id}'\" \\\n  --target-org myorg --json\n\n# Get FlexCard data sources (for dependency parsing)\nsf data query --query \"SELECT Id, Name, DataSourceConfig FROM OmniUiCard WHERE IsActive = true\" \\\n  --target-org myorg --json\n\n# Get Data Mapper items (for object dependencies)\nsf data query --query \"SELECT Id, OmniDataTransformationId, InputObjectName, OutputObjectName FROM OmniDataTransformItem\" \\\n  --target-org myorg --json\n```\n\n---\n\n## Cross-Skill Integration\n\n| Skill | Relationship | How This Skill Helps |\n|-------|-------------|---------------------|\n| sf-industry-commoncore-datamapper | Provides namespace and object dependency data | Data Mapper authoring uses detected namespace for correct API names |\n| sf-industry-commoncore-integration-procedure | Provides namespace and IP dependency map | IP authoring uses dependency graph to avoid circular references |\n| sf-industry-commoncore-omniscript | Provides namespace and element dependency data | OmniScript authoring uses namespace-correct field names |\n| sf-industry-commoncore-flexcard | Provides namespace and data source dependency map | FlexCard authoring uses detected IP references for validation |\n| sf-diagram-mermaid | Consumes dependency graph for visualization | This skill generates Mermaid output compatible with sf-diagram-mermaid styling |\n| sf-metadata | Provides sObject metadata for Data Mapper analysis | Object field validation during dependency extraction |\n| sf-deploy | Deployment uses namespace-correct metadata types | This skill provides the correct metadata type names per namespace |\n\n---\n\n## Edge Cases\n\n| Scenario | Handling |\n|----------|---------|\n| Mixed namespace org (migration in progress) | Probe all three namespaces; report if multiple return results. Components may exist under both old and migrated namespaces. |\n| Inactive components with dependencies | Include in dependency graph but mark as inactive. Warn if active component depends on inactive one. |\n| Large orgs (1000+ components) | Use SOQL pagination (LIMIT\u002FOFFSET or queryMore). Process in batches of 200. |\n| PropertySetConfig exceeds SOQL field length | Use Tooling API or REST API to fetch full JSON body for elements with truncated config. |\n| Circular dependency detected | Log the cycle path (A → B → C → A), mark all participating edges, continue traversal for remaining branches. |\n| Components referencing deleted items | Record as \"broken reference\" in output. Flag for cleanup. |\n| Version conflicts (multiple active versions) | Only the highest active version number participates in runtime. Warn if lower versions have unique dependencies. |\n\n---\n\n## Notes\n\n- **Dependencies**: Requires `sf` CLI with org authentication. Optional: sf-diagram-mermaid for styled visualization.\n- **Namespace must be detected first**: All downstream queries depend on knowing the correct object and field API names.\n- **PropertySetConfig is the key**: Nearly all dependency information lives in this JSON field on OmniProcessElement records.\n- **DataSourceConfig for FlexCards**: Data sources are in `DataSourceConfig`, NOT a `Definition` field (which does not exist on `OmniUiCard`). Card layout\u002Fstates are in `PropertySetConfig`.\n- **Data Mapper items contain object references**: InputObjectName and OutputObjectName on OmniDataTransformItem records reveal which sObjects a Data Mapper reads from and writes to. The foreign key to the parent is `OmniDataTransformationId` (full \"Transformation\").\n- **IsIntegrationProcedure is the discriminator**: `OmniProcess` uses a boolean `IsIntegrationProcedure` field, not a `TypeCategory` field (which does not exist). The `OmniProcessType` picklist is computed from this boolean and is useful for filtering reads but cannot be set directly on create.\n- **sf data create record limitations**: The `--values` flag cannot handle JSON strings in textarea fields (e.g., PropertySetConfig). Use `sf api request rest --method POST --body @file.json` instead for records with JSON configuration.\n- **Install related skills**: `\u002Fplugin install github:Jaganpro\u002Fsf-skills\u002Fsf-industry-commoncore-datamapper`, `\u002Fplugin install github:Jaganpro\u002Fsf-skills\u002Fsf-industry-commoncore-integration-procedure`, `\u002Fplugin install github:Jaganpro\u002Fsf-skills\u002Fsf-industry-commoncore-omniscript`, `\u002Fplugin install github:Jaganpro\u002Fsf-skills\u002Fsf-industry-commoncore-flexcard`\n\n---\n\n## License\n\nMIT License.\nCopyright (c) 2026 David Ryan (weytani)\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"David Ryan (weytani)","1.0.0","Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, or requests dependency diagrams. DO NOT TRIGGER when: authoring OmniScripts (use sf-industry-commoncore-omniscript), building FlexCards (use sf-industry-commoncore-flexcard), creating Integration Procedures (use sf-industry-commoncore-integration-procedure), or configuring Data Mappers (use sf-industry-commoncore-datamapper).\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-industry-commoncore-omnistudio-analyze",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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-industry-commoncore-omnistudio-analyze",{"tool":42,"command":43},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-industry-commoncore-omnistudio-analyze",{"tool":45,"command":46},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-industry-commoncore-omnistudio-analyze","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-industry-commoncore-omnistudio-analyze\u002FSkill.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"metadata.json","REFERENCE","参考文档",538,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-industry-commoncore-omnistudio-analyze\u002Fmetadata.json",[57,64,69,76,81,88],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]