Pipeline run

{
  "final_skills": [
    {
      "is_primary": true,
      "skill_name": "Salesforce"
    },
    {
      "is_primary": true,
      "skill_name": "Apex"
    },
    {
      "is_primary": true,
      "skill_name": "Lightning"
    },
    {
      "is_primary": true,
      "skill_name": "Visualforce"
    },
    {
      "is_primary": true,
      "skill_name": "Aura"
    },
    {
      "is_primary": true,
      "skill_name": "Lightning Web Components"
    },
    {
      "is_primary": true,
      "skill_name": "REST"
    },
    {
      "is_primary": true,
      "skill_name": "SOAP"
    },
    {
      "is_primary": true,
      "skill_name": "GitHub"
    },
    {
      "is_primary": true,
      "skill_name": "Code Review"
    },
    {
      "is_primary": true,
      "skill_name": "CI/CD"
    },
    {
      "is_primary": false,
      "skill_name": "Developer Console"
    },
    {
      "is_primary": false,
      "skill_name": "Workbench"
    },
    {
      "is_primary": false,
      "skill_name": "Salesforce Debug Logs"
    },
    {
      "is_primary": true,
      "skill_name": "SCRUM"
    },
    {
      "is_primary": true,
      "skill_name": "Agile"
    },
    {
      "is_primary": true,
      "skill_name": "Salesforce Sales Cloud"
    },
    {
      "is_primary": false,
      "skill_name": "Salesforce Service Cloud"
    },
    {
      "is_primary": false,
      "skill_name": "Salesforce Experience Cloud"
    },
    {
      "is_primary": true,
      "skill_name": "Salesforce CPQ"
    },
    {
      "is_primary": false,
      "skill_name": "ServiceNow"
    },
    {
      "is_primary": false,
      "skill_name": "Jira"
    },
    {
      "is_primary": false,
      "skill_name": "Copado"
    }
  ],
  "jd_role": {
    "display_name": "Senior Developer",
    "rationale": null,
    "role_aliases": [
      "Software Developer",
      "Salesforce Developer",
      "Salesforce Engineer"
    ],
    "role_archetype": "Engineering",
    "slug": ""
  },
  "nano_parsed": {
    "JD_type": "pass",
    "about_company": null,
    "certifications": [
      "Salesforce Platform Developer I",
      "Salesforce Platform Developer II",
      "Salesforce CPQ certification"
    ],
    "company_name": "Toast",
    "ctc": null,
    "domain": {
      "primary": {
        "aliases": [
          "SaaS",
          "Software Development"
        ],
        "domain": "Software \u0026 SaaS Products"
      },
      "secondary": null
    },
    "education": [
      {
        "level": "Bachelor\u0027s",
        "qualification": "Engineering - Equivalent",
        "raw": "Engineering / Equivalent educational background a must",
        "requirement": "required"
      }
    ],
    "experience": {
      "max": null,
      "min": 3,
      "raw": "3+ years Salesforce development experience"
    },
    "job_locations": [
      {
        "aliases": [],
        "city": null,
        "country": null,
        "state": null,
        "work_mode": "hybrid"
      }
    ],
    "role": "Senior Developer",
    "role_aliases": [
      "Software Developer",
      "Salesforce Developer",
      "Salesforce Engineer"
    ],
    "role_archetype": "Engineering",
    "roles_and_responsibilities": [
      {
        "bullet_count": 24,
        "heading": "Responsibilities",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 Spends majority of their",
          "last_5_words": "to ensure timely delivery."
        },
        "text": "\u2022 Spends majority of their time working on Salesforce related development tasks, requiring a technical expertise, like:\n\u2022 Salesforce platform - Security, Sharing, Visibility, Data Model, Flows etc\n\u2022 APEX- Triggers, Platform Event handlers, batch processes, Async processes, frameworks \u0026 patterns etc\n\u2022 VF pages, Aura and Lightning Web components\n\u2022 Web Services - Rest, SOAP, Authentication, Authorization, Patterns etc\n\u2022 Working alongside team members on their assignments and being a bar raiser.\n\u2022 Experienced with development best practices and understanding of SF design, architecture\n\u2022 Performs code reviews and is actively involved in deployment processes\n\u2022 Experience with GitHub tooling and PR process\n\u2022 Follows appropriate review etiquette\n\u2022 Passion for ensuring we deliver the highest quality code\n\u2022 Actively involved in deployment processes\n\u2022 Identification of affected components\n\u2022 Merging of code with the rest of the code base\n\u2022 Identification and resolution of merge conflicts\n\u2022 Development of adequate tests that cover and validate code\n\u2022 Assists in developing project estimates and plans for self\n\u2022 Accurate sizing of stories based on SCRUM process\n\u2022 On time delivery of work\n\u2022 Timely escalation of blockers\n\u2022 Proficiency troubleshooting issues\n\u2022 Leverage Developer Console, Workbench and other troubleshooting tools\n\u2022 Analyze Salesforce Debug Logs for errors and performance issues\n\u2022 Proactively seeks out and keeps up-to-date on Salesforce technologies, related tools, and best practices\n\u2022 Proactive in highlighting issues, concerns and blocker to ensure timely delivery.",
        "word_count": 284
      },
      {
        "bullet_count": 12,
        "heading": "Requirements",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 3+ years Salesforce development",
          "last_5_words": "adapt and learn quickly."
        },
        "text": "\u2022 3+ years Salesforce development experience (Apex, Lightning, VF) in an Enterprise environment\n\u2022 Advanced experience with sharing, security, visibility, data models, Flows and other Salesforce platform features \u0026 components.\n\u2022 Experience with Salesforce Sales Cloud, (Service Cloud \u0026 Experience Cloud a plus)\n\u2022 Experience with Salesforce CPQ configuration and implementation.\n\u2022 Experience in Salesforce CPQ Products, Features, Options, Configuration Attributes, CPQ Product Rules, Pricing Rules, Lookup Queries, Discounting, contracts, quote templates, and renewals.\n\u2022 Understanding of the Software Development Life cycle and Agile methodologies\n\u2022 Good analytical, problem-solving, and decision-making skills.\n\u2022 Ability to work independently and support other team members as needed.\n\u2022 Salesforce Platform Developer I \u0026 II certifications\n\u2022 Salesforce CPQ certification a plus\n\u2022 Experience in stakeholder management and should be able to communicate effectively.\n\u2022 Ability to adapt and learn quickly.",
        "word_count": 157
      },
      {
        "bullet_count": 4,
        "heading": "Bonus ingredients",
        "heading_was_present": true,
        "source_marker": {
          "first_5_words": "\u2022 Experience using ServiceNow or",
          "last_5_words": "Salesforce CI/CD tools - Copado etc"
        },
        "text": "\u2022 Experience using ServiceNow or similar tool\n\u2022 Experience using Jira or similar\n\u2022 Experience using version control tools (GitHub)\n\u2022 Experience using Salesforce CI/CD tools - Copado etc",
        "word_count": 32
      }
    ],
    "urls": []
  },
  "rejected": false,
  "rejection_reason": null,
  "run_id": "131b7261-8510-416c-913a-12ebb998b1d6",
  "stage3_signals": {
    "alias_found": true,
    "alias_match_roles": [
      {
        "display_name": "Backend Engineer",
        "matched_count": null,
        "role_id": 1,
        "score": 0.5714,
        "slug": "backend-engineer",
        "total_count": null
      },
      {
        "display_name": "AI Engineer",
        "matched_count": null,
        "role_id": 13,
        "score": 0.5,
        "slug": "ai-engineer",
        "total_count": null
      },
      {
        "display_name": "Data Engineer",
        "matched_count": null,
        "role_id": 2,
        "score": 0.4762,
        "slug": "data-engineer",
        "total_count": null
      },
      {
        "display_name": "Ios engineer",
        "matched_count": null,
        "role_id": 6,
        "score": 0.4762,
        "slug": "ios-engineer",
        "total_count": null
      },
      {
        "display_name": "Full Stack Engineer",
        "matched_count": null,
        "role_id": 15,
        "score": 0.4074,
        "slug": "full-stack-engineer",
        "total_count": null
      }
    ],
    "kra_match_roles": [
      {
        "display_name": "DevOps Engineer",
        "matched_count": null,
        "role_id": 10,
        "score": 0.3813,
        "slug": "devops-engineer",
        "total_count": null
      },
      {
        "display_name": "ML Ops Engineer",
        "matched_count": null,
        "role_id": 16,
        "score": 0.3348,
        "slug": "ml-ops-engineer",
        "total_count": null
      },
      {
        "display_name": "Frontend Engineer",
        "matched_count": null,
        "role_id": 7,
        "score": 0.323,
        "slug": "frontend-engineer",
        "total_count": null
      },
      {
        "display_name": "AR/VR Engineer",
        "matched_count": null,
        "role_id": 8,
        "score": 0.3054,
        "slug": "ar-vr-engineer",
        "total_count": null
      },
      {
        "display_name": "Data Engineer",
        "matched_count": null,
        "role_id": 2,
        "score": 0.3,
        "slug": "data-engineer",
        "total_count": null
      }
    ],
    "skill_match_roles": [
      {
        "display_name": "Backend Engineer",
        "matched_count": 2,
        "role_id": 1,
        "score": 0.087,
        "slug": "backend-engineer",
        "total_count": 23
      },
      {
        "display_name": "ML Engineer",
        "matched_count": 2,
        "role_id": 3,
        "score": 0.087,
        "slug": "ml-engineer",
        "total_count": 23
      },
      {
        "display_name": "DevOps Engineer",
        "matched_count": 2,
        "role_id": 10,
        "score": 0.087,
        "slug": "devops-engineer",
        "total_count": 23
      },
      {
        "display_name": "Full Stack Engineer",
        "matched_count": 1,
        "role_id": 15,
        "score": 0.0435,
        "slug": "full-stack-engineer",
        "total_count": 23
      }
    ]
  },
  "stage4_decision": null,
  "stage5_updates": null
}

{
  "alias_matches": [
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 106,
      "existing_alias_text": "REST",
      "input_term": "REST",
      "matched_canonical": {
        "category_id": 10,
        "display_name": "REST",
        "id": 11,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PROTOCOL",
        "slug": "rest",
        "sub_category_id": 48,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 211,
      "existing_alias_text": "SOAP",
      "input_term": "SOAP",
      "matched_canonical": {
        "category_id": 10,
        "display_name": "SOAP",
        "id": 70,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PROTOCOL",
        "slug": "soap",
        "sub_category_id": 54,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 541,
      "existing_alias_text": "GitHub",
      "input_term": "GitHub",
      "matched_canonical": {
        "category_id": 9,
        "display_name": "GitHub",
        "id": 280,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PLATFORM",
        "slug": "github",
        "sub_category_id": 170,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 864,
      "existing_alias_text": "Code Review",
      "input_term": "Code Review",
      "matched_canonical": {
        "category_id": 58,
        "display_name": "Code Review",
        "id": 516,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PRACTICE",
        "slug": "code-review",
        "sub_category_id": 364,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 1826,
      "existing_alias_text": "CI/CD",
      "input_term": "CI/CD",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "CI/CD",
        "id": 1190,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "ci-cd",
        "sub_category_id": 900,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 1851,
      "existing_alias_text": "Scrum",
      "input_term": "SCRUM",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "Scrum",
        "id": 1215,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "scrum",
        "sub_category_id": 921,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    },
    {
      "alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
      "alias_persisted": false,
      "existing_alias_id": 868,
      "existing_alias_text": "Agile",
      "input_term": "Agile",
      "matched_canonical": {
        "category_id": 8,
        "display_name": "Agile",
        "id": 520,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "agile",
        "sub_category_id": 367,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "matched_via": "alias"
    }
  ],
  "candidate_roles": [
    {
      "display_name": "Backend Engineer",
      "id": 1,
      "rationale": null,
      "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
      "slug": "backend-engineer",
      "source": "db"
    },
    {
      "display_name": "Full Stack Engineer",
      "id": 15,
      "rationale": null,
      "role_archetype": null,
      "slug": "full-stack-engineer",
      "source": "db"
    },
    {
      "display_name": "DevOps Engineer",
      "id": 10,
      "rationale": null,
      "role_archetype": null,
      "slug": "devops-engineer",
      "source": "db"
    },
    {
      "display_name": "ML Engineer",
      "id": 3,
      "rationale": null,
      "role_archetype": null,
      "slug": "ml-engineer",
      "source": "db"
    }
  ],
  "chosen_role": {
    "display_name": "Salesforce Developer",
    "id": null,
    "rationale": "The primary skills indicate a strong focus on Salesforce development, including Apex and Lightning, which align with a Salesforce Developer role.",
    "role_archetype": "A Salesforce Developer is responsible for building and customizing applications on the Salesforce platform using various tools and technologies.",
    "slug": "salesforce-developer",
    "source": "llm"
  },
  "dimensions": [
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "API Design and Contracts",
        "id": 3,
        "rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
        "slug": "api-design-and-contracts",
        "source": "db"
      },
      "input_skill": "REST",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Backend Engineer",
          "id": 1,
          "rationale": null,
          "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
          "slug": "backend-engineer",
          "source": "db"
        },
        {
          "display_name": "Full Stack Engineer",
          "id": 15,
          "rationale": null,
          "role_archetype": null,
          "slug": "full-stack-engineer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "External System Integrations",
        "id": 14,
        "rationale": "Connecting backend services to third-party APIs and internal enterprise systems. Covers client libraries, webhooks, retries, data mapping, and integration failure handling.",
        "slug": "external-system-integrations",
        "source": "db"
      },
      "input_skill": "SOAP",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "Backend Engineer",
          "id": 1,
          "rationale": null,
          "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
          "slug": "backend-engineer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "CI/CD Pipeline Platforms",
        "id": 150,
        "rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
        "slug": "ci-cd-pipeline-platforms",
        "source": "db"
      },
      "input_skill": "GitHub",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "DevOps Engineer",
          "id": 10,
          "rationale": null,
          "role_archetype": null,
          "slug": "devops-engineer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "CI/CD for Machine Learning",
        "id": 56,
        "rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
        "slug": "ci-cd-for-machine-learning",
        "source": "db"
      },
      "input_skill": "GitHub",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "ML Engineer",
          "id": 3,
          "rationale": null,
          "role_archetype": null,
          "slug": "ml-engineer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Code Review",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "CI/CD Pipeline Platforms",
        "id": 150,
        "rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
        "slug": "ci-cd-pipeline-platforms",
        "source": "db"
      },
      "input_skill": "CI/CD",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "DevOps Engineer",
          "id": 10,
          "rationale": null,
          "role_archetype": null,
          "slug": "devops-engineer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "CI/CD for Machine Learning",
        "id": 56,
        "rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
        "slug": "ci-cd-for-machine-learning",
        "source": "db"
      },
      "input_skill": "CI/CD",
      "llm_role": null,
      "roles_from_db": [
        {
          "display_name": "ML Engineer",
          "id": 3,
          "rationale": null,
          "role_archetype": null,
          "slug": "ml-engineer",
          "source": "db"
        }
      ]
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "SCRUM",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Agile",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Salesforce",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Lightning",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Visualforce",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Aura",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Systems Programming",
        "id": 166,
        "rationale": "Systems programming covers low-level software development where performance, memory safety, and direct control over resources matter. Rust fits here because it is commonly used for OS-adjacent services, infrastructure components, and other performance-sensitive systems code.",
        "slug": "d_init_02",
        "source": "db"
      },
      "input_skill": "Aura",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Lightning Web Components",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Workbench",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Salesforce Sales Cloud",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Salesforce Service Cloud",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Salesforce Experience Cloud",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "Systems Programming",
        "id": 166,
        "rationale": "Systems programming covers low-level software development where performance, memory safety, and direct control over resources matter. Rust fits here because it is commonly used for OS-adjacent services, infrastructure components, and other performance-sensitive systems code.",
        "slug": "d_init_02",
        "source": "db"
      },
      "input_skill": "Salesforce Experience Cloud",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "ServiceNow",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Jira",
      "llm_role": null,
      "roles_from_db": []
    },
    {
      "dimension": {
        "difficulty_hint": "well_known",
        "display_name": "React Frontend Development",
        "id": 96,
        "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
        "slug": "d_init_01",
        "source": "db"
      },
      "input_skill": "Copado",
      "llm_role": null,
      "roles_from_db": []
    }
  ],
  "input_final_skills": [
    "Salesforce",
    "Apex",
    "Lightning",
    "Visualforce",
    "Aura",
    "Lightning Web Components",
    "REST",
    "SOAP",
    "GitHub",
    "Code Review",
    "CI/CD",
    "Developer Console",
    "Workbench",
    "Salesforce Debug Logs",
    "SCRUM",
    "Agile",
    "Salesforce Sales Cloud",
    "Salesforce Service Cloud",
    "Salesforce Experience Cloud",
    "Salesforce CPQ",
    "ServiceNow",
    "Jira",
    "Copado"
  ],
  "input_llm_skills": [
    "Salesforce",
    "Apex",
    "Lightning",
    "Visualforce",
    "Aura",
    "Lightning Web Components",
    "REST",
    "SOAP",
    "GitHub",
    "Code Review",
    "CI/CD",
    "Developer Console",
    "Workbench",
    "Salesforce Debug Logs",
    "SCRUM",
    "Agile",
    "Salesforce Sales Cloud",
    "Salesforce Service Cloud",
    "Salesforce Experience Cloud",
    "Salesforce CPQ",
    "ServiceNow",
    "Jira",
    "Copado"
  ],
  "new_aliases_persisted": 0,
  "run_id": "131b7261-8510-416c-913a-12ebb998b1d6",
  "skills_detail": [
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Salesforce",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Salesforce",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Platform",
          "skill_nature": "PLATFORM",
          "sub_category": "crm_platform",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "\u201cSalesforce\u201d in JDs typically refers specifically to the Salesforce CRM/Platform, not another distinct catalog skill."
          },
          "context_keywords": {
            "context_keywords": [
              "Apex",
              "Visualforce",
              "Lightning",
              "Sales Cloud",
              "Service Cloud",
              "Trailhead",
              "SOQL",
              "SObject",
              "AppExchange",
              "Einstein Analytics",
              "Workflow Rules",
              "Process Builder",
              "Salesforce DX",
              "Custom Objects",
              "API Integration"
            ]
          },
          "maturity": {
            "confidence": 0.97,
            "maturity": "well_known",
            "reasoning": "Salesforce is a mainstream CRM platform with very high job-posting volume across sales ops, admin, and developer roles; it remains a common enterprise requirement rather than a niche tool."
          },
          "skill_id": "salesforce",
          "vendor_license": {
            "confidence": 0.95,
            "license": "proprietary",
            "vendor": "Salesforce, Inc.",
            "year_introduced": 1999
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Salesforce is a vendor CRM platform used to build and customize sales, service, and workflow applications. This skill belongs here because it centers on configuring and extending the Salesforce ecosystem rather than generic backend or frontend development.",
            "exemplar_skills": [
              "Salesforce",
              "Apex",
              "Visualforce",
              "Lightning Web Components",
              "Salesforce Flow",
              "Salesforce Objects",
              "Salesforce Reports and Dashboards"
            ],
            "in_scope": "Salesforce, Salesforce CRM, Lightning Experience, Salesforce Setup, Apex, Visualforce, Lightning Web Components, Salesforce Flows, Salesforce Objects, Salesforce Reports and Dashboards",
            "name": "Salesforce CRM Platform",
            "out_of_scope": "Generic JavaScript and TypeScript application development, cloud infrastructure provisioning, non-Salesforce CRM systems, database administration outside Salesforce data model",
            "overlap_flags": [
              {
                "reason": "Lightning Web Components use JavaScript/TypeScript-like development patterns, but the primary competency is Salesforce platform customization.",
                "with_dim_id": "javascript-and-typescript",
                "with_dim_name": null,
                "with_role": "Frontend Engineer"
              },
              {
                "reason": "Salesforce implementations often integrate with external APIs, but integration mechanics are secondary to the CRM platform skill.",
                "with_dim_id": "api-integration-and-data-fetching",
                "with_dim_name": null,
                "with_role": "Frontend Engineer, Full Stack Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Salesforce",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "salesforce"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [
            "enterprise-saas"
          ],
          "related_to": [
            "api-integration",
            "analytics",
            "frontend",
            "web-analytics",
            "agentic-systems"
          ],
          "requires": [],
          "skill_id": "salesforce",
          "suppress_on_match": []
        },
        "skill_id": "salesforce",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.98,
          "name": "Salesforce",
          "reasoning": "By the Vendor SaaS = Platform rule, Salesforce is a hosted multi-tenant commercial SaaS environment with APIs, so it is a Platform rather than a Tool or Service.",
          "skill_id": "salesforce",
          "subtype": "crm_platform",
          "type": "Platform"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [],
      "input_skill": "Apex",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Lightning",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Lightning",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Framework",
          "skill_nature": "FRAMEWORK",
          "sub_category": "application_framework",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": true,
            "confused_with": [
              "lightning_ai",
              "lightning_pytorch"
            ],
            "reasoning": "\u201cLightning\u201d in JDs often refers to the PyTorch Lightning ecosystem, not just a generic Lightning framework."
          },
          "context_keywords": {
            "context_keywords": [
              "Aura",
              "LWC",
              "Visualforce",
              "Apex",
              "Salesforce",
              "component-based",
              "event-driven",
              "JavaScript",
              "UI framework",
              "data binding",
              "DOM manipulation",
              "responsive design",
              "single-page application",
              "REST API",
              "custom components"
            ]
          },
          "maturity": {
            "confidence": 0.86,
            "maturity": "niche",
            "reasoning": "JD volume is low and mostly confined to Salesforce ecosystem roles; market signal shows it as a specialized framework rather than a general-purpose hiring staple."
          },
          "skill_id": "lightning",
          "vendor_license": {
            "confidence": 0.9,
            "license": "other_open",
            "vendor": "Salesforce",
            "year_introduced": 2014
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Development with the Lightning framework for structuring training, validation, and inference code in a cleaner, reusable way. This fits the target skill because Lightning is primarily a Python framework used to simplify model training workflows and experiment code.",
            "exemplar_skills": [
              "Lightning",
              "PyTorch Lightning",
              "LightningModule",
              "LightningDataModule",
              "Trainer",
              "Lightning callbacks",
              "checkpointing",
              "training loop abstraction"
            ],
            "in_scope": "Lightning, PyTorch Lightning, LightningModule, LightningDataModule, Trainer, callbacks, checkpoints, logging, training loops, validation hooks",
            "name": "Lightning Framework Development",
            "out_of_scope": "Distributed multi-node training infrastructure, GPU cluster scheduling, model serving infrastructure, workflow orchestration engines, cloud platform setup",
            "overlap_flags": [
              {
                "reason": "Lightning can be used with multi-GPU and multi-node training, but the framework itself is primarily an application-layer training abstraction.",
                "with_dim_id": "distributed-training-systems",
                "with_dim_name": null,
                "with_role": "ML Engineer, ML Ops Engineer"
              },
              {
                "reason": "Lightning often appears in production ML workflows, but lifecycle management and deployment controls are owned by the MLOps dimension.",
                "with_dim_id": "mlops-platforms-and-lifecycle",
                "with_dim_name": null,
                "with_role": "ML Engineer, ML Ops Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Lightning",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "lightning"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "pytorch",
            "deepspeed",
            "ray-train",
            "torchserve",
            "airflow",
            "comet",
            "mlflow",
            "eclipse"
          ],
          "requires": [],
          "skill_id": "lightning",
          "suppress_on_match": []
        },
        "skill_id": "lightning",
        "split_log": [],
        "typed": {
          "alternatives_considered": [
            "Tool: ruled out \u2014 the name is ambiguous and could refer to standalone software, but the most common technical usage is as a build-on framework.",
            "Platform: ruled out \u2014 there is no clear evidence it is a hosted multi-tenant environment with APIs.",
            "Library: ruled out \u2014 it is typically used as an application framework rather than an import-only package."
          ],
          "confidence": 0.62,
          "name": "Lightning",
          "reasoning": "Lightning is best treated as a Framework because it is a structured codebase used to build applications inside rather than software merely operated as a user.",
          "skill_id": "lightning",
          "subtype": "application_framework",
          "type": "Framework"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Visualforce",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Visualforce",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Framework",
          "skill_nature": "FRAMEWORK",
          "sub_category": "web_application_framework",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "Visualforce is a specific Salesforce web framework name; unlikely to be confused with other catalog skills."
          },
          "context_keywords": {
            "context_keywords": [
              "Apex",
              "Salesforce",
              "Lightning",
              "MVC",
              "components",
              "custom controllers",
              "page layouts",
              "data binding",
              "JavaScript",
              "CSS",
              "HTML",
              "Visualforce pages",
              "standard controllers",
              "action functions",
              "UI design"
            ]
          },
          "maturity": {
            "confidence": 0.91,
            "maturity": "niche",
            "reasoning": "Visualforce still appears in Salesforce admin/dev job postings, but most new Salesforce UI work has shifted to Lightning Web Components, making it a legacy niche skill rather than a broad hiring staple."
          },
          "skill_id": "visualforce",
          "vendor_license": {
            "confidence": 0.9,
            "license": "other_open",
            "vendor": "Salesforce",
            "year_introduced": 2007
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Frameworks and page technologies used to build custom user interfaces on the Salesforce platform. Visualforce belongs here because it is Salesforce\u0027s server-rendered UI layer for creating pages, forms, and components within CRM apps.",
            "exemplar_skills": [
              "Visualforce",
              "Visualforce pages",
              "Visualforce components",
              "Apex controllers",
              "Salesforce UI customization"
            ],
            "in_scope": "Visualforce, Visualforce pages, Visualforce components, Apex controllers for Visualforce, standard controllers, custom controllers, Salesforce page rendering, page layouts, Salesforce UI customization",
            "name": "Salesforce UI Frameworks",
            "out_of_scope": "Lightning Web Components, Aura components, Salesforce data model design, Apex business logic not tied to UI, integration middleware, admin configuration, report and dashboard setup",
            "overlap_flags": [
              {
                "reason": "Visualforce pages often call Apex or external services, but the dimension here is the Salesforce UI framework rather than generic client-server integration.",
                "with_dim_id": "api-integration-and-data-fetching",
                "with_dim_name": null,
                "with_role": "Frontend Engineer, Full Stack Engineer"
              },
              {
                "reason": "Visualforce can embed client-side scripting, but JavaScript is a separate general-purpose frontend dimension.",
                "with_dim_id": "javascript-and-typescript",
                "with_dim_name": null,
                "with_role": "Frontend Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Visualforce",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "visualforce"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [
            "frontend",
            "html",
            "xml"
          ],
          "related_to": [
            "responsive-web-development",
            "api",
            "ui-ux",
            "websphere",
            "j2ee",
            "analytics"
          ],
          "requires": [],
          "skill_id": "visualforce",
          "suppress_on_match": []
        },
        "skill_id": "visualforce",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.9,
          "name": "Visualforce",
          "reasoning": "Visualforce is a Salesforce page/component framework used to build application UIs inside the Salesforce platform, so by the Tool vs Framework rule it is a Framework rather than a Tool.",
          "skill_id": "visualforce",
          "subtype": "web_application_framework",
          "type": "Framework"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Aura",
          "llm_role": null,
          "roles_from_db": []
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Systems Programming",
            "id": 166,
            "rationale": "Systems programming covers low-level software development where performance, memory safety, and direct control over resources matter. Rust fits here because it is commonly used for OS-adjacent services, infrastructure components, and other performance-sensitive systems code.",
            "slug": "d_init_02",
            "source": "db"
          },
          "input_skill": "Aura",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Aura",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Concept",
          "skill_nature": "CONCEPT",
          "sub_category": "security_concept",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "\u201cAura\u201d is a specific security concept in this catalog; typical JDs are unlikely to confuse it with other distinct skills."
          },
          "context_keywords": {
            "context_keywords": [
              "authentication",
              "authorization",
              "encryption",
              "access control",
              "security policies",
              "identity management",
              "multi-factor authentication",
              "data protection",
              "threat modeling",
              "compliance",
              "risk assessment",
              "security frameworks",
              "vulnerability management",
              "incident response",
              "security architecture"
            ]
          },
          "maturity": {
            "confidence": 0.78,
            "maturity": "niche",
            "reasoning": "Aura is a niche security concept with limited direct JD volume; market signals are mostly research and vendor docs rather than broad hiring demand, unlike mainstream security stacks."
          },
          "skill_id": "aura",
          "vendor_license": {
            "confidence": 0.95,
            "license": null,
            "vendor": null,
            "year_introduced": null
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Frameworks and SDKs used to build user interfaces for AR/VR and spatial computing apps. Aura fits here if it refers to an immersive app framework or UI layer rather than a general-purpose library.",
            "exemplar_skills": [
              "Aura",
              "AR/VR UI frameworks",
              "spatial computing SDKs",
              "immersive scene composition",
              "3D interface widgets"
            ],
            "in_scope": "Aura, AR/VR UI frameworks, spatial computing SDKs, immersive scene composition, 3D interface widgets, interaction layers, platform UI toolkits",
            "name": "Immersive UI Frameworks",
            "out_of_scope": "Device runtime APIs and sensor access, head tracking and locomotion behavior, low-level rendering engines, general mobile UI frameworks, backend APIs",
            "overlap_flags": [
              {
                "reason": "Immersive frameworks often sit on top of device-specific sensors and runtime capabilities.",
                "with_dim_id": "device-runtime-and-hardware-apis",
                "with_dim_name": null,
                "with_role": "AR/VR Engineer"
              },
              {
                "reason": "Spatial UI frameworks may include comfort and locomotion-aware interaction patterns.",
                "with_dim_id": "head-tracking-and-comfort-ux",
                "with_dim_name": null,
                "with_role": "AR/VR Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          },
          {
            "description": "Application development for augmented reality experiences, including scene setup, interaction design, and device-specific presentation. Aura belongs here if it is an AR development framework or SDK used to build end-user immersive apps.",
            "exemplar_skills": [
              "Aura",
              "augmented reality app development",
              "spatial anchors",
              "AR scene management",
              "gesture interaction"
            ],
            "in_scope": "Aura, augmented reality app development, spatial anchors, overlays, AR scene management, gesture interaction, device camera integration",
            "name": "Augmented Reality Application Development",
            "out_of_scope": "Core computer vision algorithms, low-level graphics rendering pipelines, generic mobile app UI, hardware driver work, backend orchestration",
            "overlap_flags": [
              {
                "reason": "AR apps depend on platform runtime APIs for camera, tracking, and sensors.",
                "with_dim_id": "device-runtime-and-hardware-apis",
                "with_dim_name": null,
                "with_role": "AR/VR Engineer"
              },
              {
                "reason": "If Aura is used for browser-based experiences, some UI adaptation concerns may overlap, but the core skill is immersive AR development.",
                "with_dim_id": "responsive-and-mobile-web-design",
                "with_dim_name": null,
                "with_role": "Frontend Engineer"
              }
            ],
            "tentative_id": "d_init_02"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Aura",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [
            "d_init_02"
          ],
          "skill_id": "aura"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "authentication",
            "api",
            "metrics",
            "analytics",
            "cloud",
            "agentic-systems",
            "evaluation"
          ],
          "requires": [],
          "skill_id": "aura",
          "suppress_on_match": []
        },
        "skill_id": "aura",
        "split_log": [],
        "typed": {
          "alternatives_considered": [
            "Platform: ruled out \u2014 no indication this is a hosted multi-tenant environment with APIs.",
            "Tool: ruled out \u2014 no evidence of user-operated software.",
            "Standard: ruled out \u2014 Aura is not clearly an industry-defined specification."
          ],
          "confidence": 0.62,
          "name": "Aura",
          "reasoning": "Aura is most plausibly a named security/identity knowledge unit rather than software, so under the Concept vs Methodology rule it fits Concept best.",
          "skill_id": "aura",
          "subtype": "security_concept",
          "type": "Concept"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Lightning Web Components",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Lightning Web Components",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Framework",
          "skill_nature": "FRAMEWORK",
          "sub_category": "web_component_framework",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "Lightning Web Components is a specific Salesforce web component framework; unlikely to be confused with other generic web component frameworks."
          },
          "context_keywords": {
            "context_keywords": [
              "Aura",
              "Salesforce",
              "JavaScript",
              "HTML",
              "CSS",
              "LWC",
              "Web Components",
              "ES6",
              "Lightning App Builder",
              "SLDS",
              "Apex",
              "Event Handling",
              "Data Binding",
              "Custom Elements",
              "Shadow DOM"
            ]
          },
          "maturity": {
            "confidence": 0.88,
            "maturity": "well_known",
            "reasoning": "Common in Salesforce job postings and official Salesforce docs position LWC as the standard replacement for Aura in new UI development, indicating broad hiring demand within the Salesforce ecosystem."
          },
          "skill_id": "lightning-web-components",
          "vendor_license": {
            "confidence": 0.95,
            "license": "apache_2",
            "vendor": "Salesforce",
            "year_introduced": 2019
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Building reusable UI components and page logic on the Salesforce platform. Lightning Web Components belongs here because it is Salesforce\u0027s modern component model for creating interactive, platform-native front-end experiences.",
            "exemplar_skills": [
              "Lightning Web Components",
              "LWC",
              "Salesforce component development",
              "Lightning App Builder",
              "LWC lifecycle hooks",
              "Salesforce UI development"
            ],
            "in_scope": "Lightning Web Components, LWC templates, component lifecycle, decorators, Salesforce UI composition, event handling in LWC, component communication, Lightning App Builder components, Salesforce platform front-end development",
            "name": "Salesforce Component Development",
            "out_of_scope": "Apex server-side business logic, Salesforce data modeling, Flow automation, Visualforce pages, org administration, generic JavaScript frameworks outside Salesforce",
            "overlap_flags": [
              {
                "reason": "LWC uses JavaScript heavily for component logic, but this dimension is specifically about Salesforce component architecture rather than the language itself.",
                "with_dim_id": "javascript-and-typescript",
                "with_dim_name": null,
                "with_role": "Frontend Engineer"
              },
              {
                "reason": "LWC interfaces may need responsive behavior, but layout and device adaptation are owned by the web design dimension.",
                "with_dim_id": "responsive-and-mobile-web-design",
                "with_dim_name": null,
                "with_role": "Frontend Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Lightning Web Components",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "lightning-web-components"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "frontend",
            "html",
            "xml",
            "responsive-web-development",
            "cross-browser-compatibility",
            "widget-testing",
            "ui-ux",
            "node-js"
          ],
          "requires": [],
          "skill_id": "lightning-web-components",
          "suppress_on_match": []
        },
        "skill_id": "lightning-web-components",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.93,
          "name": "Lightning Web Components",
          "reasoning": "By the Tool vs Framework rule, Lightning Web Components is a structured UI codebase you build applications inside, not a standalone user-operated tool.",
          "skill_id": "lightning-web-components",
          "subtype": "web_component_framework",
          "type": "Framework"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "REST",
          "alias_type": "CANONICAL",
          "id": 106,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 10,
        "display_name": "REST",
        "id": 11,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PROTOCOL",
        "slug": "rest",
        "sub_category_id": 48,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "API Design and Contracts",
            "id": 3,
            "rationale": "Designing request/response shapes and the rules that govern client-server interaction. This cluster is coherent because full stack engineers often own the contract between UI behavior and backend implementation.",
            "slug": "api-design-and-contracts",
            "source": "db"
          },
          "input_skill": "REST",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Backend Engineer",
              "id": 1,
              "rationale": null,
              "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
              "slug": "backend-engineer",
              "source": "db"
            },
            {
              "display_name": "Full Stack Engineer",
              "id": 15,
              "rationale": null,
              "role_archetype": null,
              "slug": "full-stack-engineer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "REST",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "SOAP",
          "alias_type": "CANONICAL",
          "id": 211,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 10,
        "display_name": "SOAP",
        "id": 70,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PROTOCOL",
        "slug": "soap",
        "sub_category_id": 54,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "External System Integrations",
            "id": 14,
            "rationale": "Connecting backend services to third-party APIs and internal enterprise systems. Covers client libraries, webhooks, retries, data mapping, and integration failure handling.",
            "slug": "external-system-integrations",
            "source": "db"
          },
          "input_skill": "SOAP",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "Backend Engineer",
              "id": 1,
              "rationale": null,
              "role_archetype": "A Backend Engineer designs, builds, and maintains the server-side logic and data handling that power applications and services. They focus on implementing reliable business functionality, integrating with other systems, and ensuring the backend is scalable, maintainable, and observable.",
              "slug": "backend-engineer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "SOAP",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "GitHub",
          "alias_type": "CANONICAL",
          "id": 541,
          "is_primary": true,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 9,
        "display_name": "GitHub",
        "id": 280,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PLATFORM",
        "slug": "github",
        "sub_category_id": 170,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "CI/CD Pipeline Platforms",
            "id": 150,
            "rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
            "slug": "ci-cd-pipeline-platforms",
            "source": "db"
          },
          "input_skill": "GitHub",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "DevOps Engineer",
              "id": 10,
              "rationale": null,
              "role_archetype": null,
              "slug": "devops-engineer",
              "source": "db"
            }
          ]
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "CI/CD for Machine Learning",
            "id": 56,
            "rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
            "slug": "ci-cd-for-machine-learning",
            "source": "db"
          },
          "input_skill": "GitHub",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "ML Engineer",
              "id": 3,
              "rationale": null,
              "role_archetype": null,
              "slug": "ml-engineer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "GitHub",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "Code Review",
          "alias_type": "CANONICAL",
          "id": 864,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 58,
        "display_name": "Code Review",
        "id": 516,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "PRACTICE",
        "slug": "code-review",
        "sub_category_id": 364,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Code Review",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Code Review",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "CI/CD",
          "alias_type": "CANONICAL",
          "id": 1826,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "CI/CD",
        "id": 1190,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "ci-cd",
        "sub_category_id": 900,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "CI/CD Pipeline Platforms",
            "id": 150,
            "rationale": "Systems used to define, run, and maintain automated build and deployment workflows. This cluster is coherent because the role owns delivery automation end to end, including pipeline reliability and promotion logic.",
            "slug": "ci-cd-pipeline-platforms",
            "source": "db"
          },
          "input_skill": "CI/CD",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "DevOps Engineer",
              "id": 10,
              "rationale": null,
              "role_archetype": null,
              "slug": "devops-engineer",
              "source": "db"
            }
          ]
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "CI/CD for Machine Learning",
            "id": 56,
            "rationale": "Tools and platforms for automating ML model integration, testing, and deployment pipelines.",
            "slug": "ci-cd-for-machine-learning",
            "source": "db"
          },
          "input_skill": "CI/CD",
          "llm_role": null,
          "roles_from_db": [
            {
              "display_name": "ML Engineer",
              "id": 3,
              "rationale": null,
              "role_archetype": null,
              "slug": "ml-engineer",
              "source": "db"
            }
          ]
        }
      ],
      "input_skill": "CI/CD",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [],
      "input_skill": "Developer Console",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Workbench",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Workbench",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Tool",
          "skill_nature": "TOOL",
          "sub_category": "development_workbench",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "\u201cWorkbench\u201d is a generic term but in typical JDs it\u2019s unlikely to be confused with another specific catalog skill."
          },
          "context_keywords": {
            "context_keywords": [
              "IDE",
              "debugging",
              "version control",
              "plugin",
              "scripting",
              "build automation",
              "configuration management",
              "code analysis",
              "user interface",
              "project management",
              "integration",
              "customization",
              "workflow",
              "collaboration",
              "deployment"
            ]
          },
          "maturity": {
            "confidence": 0.72,
            "maturity": "niche",
            "reasoning": "\u201cWorkbench\u201d is a generic IDE/workbench label with low, inconsistent JD volume; market signals are fragmented and it\u2019s usually replaced by mainstream IDEs like VS Code or IntelliJ in postings."
          },
          "skill_id": "workbench",
          "vendor_license": {
            "confidence": 0.9,
            "license": "proprietary",
            "vendor": "JetBrains",
            "year_introduced": 2010
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Integrated tools and environments used by developers to write, run, inspect, and debug code. This skill fits here when \"Workbench\" refers to a developer-facing IDE, console, or productivity environment rather than a domain-specific platform.",
            "exemplar_skills": [
              "Workbench",
              "Visual Studio Code",
              "IntelliJ IDEA",
              "Eclipse",
              "debugging",
              "code navigation",
              "refactoring"
            ],
            "in_scope": "Workbench, IDE workbenches, code editors, debugging consoles, local run environments, project navigation, refactoring aids, developer productivity plugins",
            "name": "Development Workbench Tools",
            "out_of_scope": "cloud IDE hosting, CI/CD pipelines, database administration consoles, ML experiment tracking UIs, end-user business dashboards",
            "overlap_flags": [
              {
                "reason": "Workbench may be the primary editor used for JavaScript/TypeScript development, but the dimension here is the tool environment rather than the language itself.",
                "with_dim_id": "javascript-and-typescript",
                "with_dim_name": null,
                "with_role": "Frontend Engineer"
              },
              {
                "reason": "Some workbenches are cloud-hosted developer environments, but cloud infrastructure ownership belongs to the platform dimension.",
                "with_dim_id": "cloud-platforms",
                "with_dim_name": null,
                "with_role": "Backend Engineer, Cybersecurity Engineer, Data Engineer, DevOps Engineer, Full Stack Engineer, ML Engineer, ML Ops Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Workbench",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "workbench"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "agent-tooling",
            "sagemaker",
            "widget-testing",
            "evaluation",
            "metrics",
            "artifact-logging",
            "runbooks",
            "technical-writing"
          ],
          "requires": [],
          "skill_id": "workbench",
          "suppress_on_match": []
        },
        "skill_id": "workbench",
        "split_log": [],
        "typed": {
          "alternatives_considered": [
            "Framework: ruled out \u2014 the name does not clearly indicate a codebase you build applications within.",
            "Platform: ruled out \u2014 there is no evidence it is a hosted multi-tenant environment with APIs."
          ],
          "confidence": 0.67,
          "name": "Workbench",
          "reasoning": "Workbench is best treated as a user-operated software environment rather than something you build applications inside, so the Tool vs Framework rule points to Tool.",
          "skill_id": "workbench",
          "subtype": "development_workbench",
          "type": "Tool"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [],
      "input_skill": "Salesforce Debug Logs",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "Scrum",
          "alias_type": "CANONICAL",
          "id": 1851,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "Scrum",
        "id": 1215,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "scrum",
        "sub_category_id": 921,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "SCRUM",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "SCRUM",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [
        {
          "alias_text": "Agile",
          "alias_type": "CANONICAL",
          "id": 868,
          "is_primary": false,
          "match_strategy": "CASE_INSENSITIVE"
        }
      ],
      "canonical": {
        "category_id": 8,
        "display_name": "Agile",
        "id": 520,
        "is_also_category": false,
        "is_extractable": true,
        "skill_nature": "METHODOLOGY",
        "slug": "agile",
        "sub_category_id": 367,
        "typical_lifespan": "EVERGREEN",
        "volatility": "STABLE"
      },
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Agile",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Agile",
      "matched_via": "alias",
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "db",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Salesforce Sales Cloud",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Salesforce Sales Cloud",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Platform",
          "skill_nature": "PLATFORM",
          "sub_category": "crm_platform",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": true,
            "confused_with": [
              "salesforce-service-cloud"
            ],
            "reasoning": "\u201cSalesforce\u201d CRM suite items are often mentioned generically; \u201cSales Cloud\u201d can be confused with other Salesforce clouds like Service Cloud in JDs."
          },
          "context_keywords": {
            "context_keywords": [
              "Salesforce Lightning",
              "Apex",
              "Visualforce",
              "Sales Cloud Console",
              "Einstein Analytics",
              "Salesforce CPQ",
              "Lead Management",
              "Opportunity Management",
              "Salesforce AppExchange",
              "Workflow Rules",
              "Process Builder",
              "Reports and Dashboards",
              "Data Import Wizard",
              "Salesforce Mobile",
              "Custom Objects"
            ]
          },
          "maturity": {
            "confidence": 0.93,
            "maturity": "well_known",
            "reasoning": "Commonly listed in CRM/admin and RevOps job descriptions across enterprises; Salesforce\u2019s own ecosystem and AppExchange indicate broad market adoption rather than niche use."
          },
          "skill_id": "salesforce-sales-cloud",
          "vendor_license": {
            "confidence": 0.95,
            "license": "other_open",
            "vendor": "Salesforce",
            "year_introduced": 2000
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Configuration and administration of Salesforce Sales Cloud for managing leads, accounts, contacts, opportunities, and sales processes. This skill belongs here because it refers to the core CRM product used to support sales operations and pipeline management.",
            "exemplar_skills": [
              "Salesforce Sales Cloud",
              "Salesforce CRM administration",
              "Lead management in Salesforce",
              "Opportunity management",
              "Salesforce reports and dashboards",
              "Sales process configuration"
            ],
            "in_scope": "Salesforce Sales Cloud, leads and lead assignment rules, accounts and contacts, opportunities and stages, sales processes and record types, page layouts and Lightning record pages, reports and dashboards, sales automation, approval processes, territory management",
            "name": "Salesforce Sales Cloud Administration",
            "out_of_scope": "Salesforce Service Cloud, Marketing Cloud, Apex custom development, Salesforce integration architecture, general CRM strategy outside the Sales Cloud product",
            "overlap_flags": [
              {
                "reason": "Salesforce org access, profiles, roles, and permission sets can overlap with broader identity administration, but the core skill here is Sales Cloud configuration.",
                "with_dim_id": "identity-and-access-management-products",
                "with_dim_name": null,
                "with_role": "Cybersecurity Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Salesforce Sales Cloud",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "salesforce-sales-cloud"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "enterprise-saas",
            "api-integration",
            "analytics",
            "push-notifications",
            "frontend",
            "web-analytics"
          ],
          "requires": [],
          "skill_id": "salesforce-sales-cloud",
          "suppress_on_match": []
        },
        "skill_id": "salesforce-sales-cloud",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.98,
          "name": "Salesforce Sales Cloud",
          "reasoning": "By the Platform vs Tool rule, Salesforce Sales Cloud is a hosted multi-tenant SaaS environment with APIs and managed capabilities, so it is a Platform rather than a Tool.",
          "skill_id": "salesforce-sales-cloud",
          "subtype": "crm_platform",
          "type": "Platform"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Salesforce Service Cloud",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Salesforce Service Cloud",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Platform",
          "skill_nature": "PLATFORM",
          "sub_category": "customer_service_saas_platform",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": true,
            "confused_with": [
              "salesforce-sales-cloud",
              "salesforce-marketing-cloud"
            ],
            "reasoning": "\u201cSalesforce\u201d suite terms are often used loosely; Service Cloud can be confused with other Salesforce clouds like Sales Cloud or Marketing Cloud in JDs."
          },
          "context_keywords": {
            "context_keywords": [
              "Omni-Channel",
              "Service Console",
              "Knowledge Base",
              "Case Management",
              "Live Agent",
              "Einstein AI",
              "Workflow Rules",
              "Service Level Agreements",
              "Chatbots",
              "Customer Journeys",
              "Field Service",
              "Reports and Dashboards",
              "Community Cloud",
              "Integration",
              "Automation"
            ]
          },
          "maturity": {
            "confidence": 0.93,
            "maturity": "well_known",
            "reasoning": "Commonly listed in customer support/admin job descriptions and Salesforce partner roles; Salesforce continues active product investment and Service Cloud remains a core CRM suite offering, not a sunset product."
          },
          "skill_id": "salesforce-service-cloud",
          "vendor_license": {
            "confidence": 0.95,
            "license": "proprietary",
            "vendor": "Salesforce",
            "year_introduced": 2011
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Configuration and administration of Salesforce Service Cloud for customer support operations. This includes case management, service processes, agent productivity, and service console setup, which are the core capabilities represented by the target skill.",
            "exemplar_skills": [
              "Salesforce Service Cloud",
              "case management",
              "service console configuration",
              "omni-channel routing",
              "entitlement management",
              "escalation rules",
              "Salesforce Knowledge",
              "agent workspace setup"
            ],
            "in_scope": "Salesforce Service Cloud, case management, service console, assignment rules, escalation rules, queues, macros, quick text, service processes, entitlements, milestones, knowledge base setup, omni-channel routing, service analytics",
            "name": "Salesforce Service Cloud Administration",
            "out_of_scope": "Salesforce Sales Cloud sales automation, Apex custom development, Lightning Web Components UI coding, Marketing Cloud campaigns, MuleSoft integrations, which belong to other Salesforce or application-development dimensions",
            "overlap_flags": [
              {
                "reason": "Service Cloud implementations often integrate with external ticketing, telephony, and CRM systems, but the integration mechanics are a separate concern.",
                "with_dim_id": "api-integration-and-data-fetching",
                "with_dim_name": null,
                "with_role": "Frontend Engineer, Full Stack Engineer"
              },
              {
                "reason": "Service Cloud deployments may involve role, profile, and permission design, but broader identity architecture is owned elsewhere.",
                "with_dim_id": "identity-and-access-architecture",
                "with_dim_name": null,
                "with_role": "Cloud Architect"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Salesforce Service Cloud",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "salesforce-service-cloud"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [
            "enterprise-saas",
            "cloud"
          ],
          "related_to": [
            "api-integration",
            "analytics",
            "frontend",
            "responsive-web-development",
            "agentic-systems",
            "sdlc"
          ],
          "requires": [],
          "skill_id": "salesforce-service-cloud",
          "suppress_on_match": []
        },
        "skill_id": "salesforce-service-cloud",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.98,
          "name": "Salesforce Service Cloud",
          "reasoning": "By the Vendor SaaS = Platform rule, Salesforce Service Cloud is a hosted multi-tenant SaaS environment with APIs and managed capabilities, so it is a Platform rather than a Tool or Service.",
          "skill_id": "salesforce-service-cloud",
          "subtype": "customer_service_saas_platform",
          "type": "Platform"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Salesforce Experience Cloud",
          "llm_role": null,
          "roles_from_db": []
        },
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "Systems Programming",
            "id": 166,
            "rationale": "Systems programming covers low-level software development where performance, memory safety, and direct control over resources matter. Rust fits here because it is commonly used for OS-adjacent services, infrastructure components, and other performance-sensitive systems code.",
            "slug": "d_init_02",
            "source": "db"
          },
          "input_skill": "Salesforce Experience Cloud",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Salesforce Experience Cloud",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Platform",
          "skill_nature": "PLATFORM",
          "sub_category": "customer_experience_platform",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "\u201cSalesforce Experience Cloud\u201d is a specific Salesforce product name; typical JDs won\u2019t confuse it with other Salesforce clouds like Sales/Service/Marketing."
          },
          "context_keywords": {
            "context_keywords": [
              "Community Builder",
              "Lightning Components",
              "CMS",
              "Experience Cloud Sites",
              "Salesforce Communities",
              "Personalization",
              "User Engagement",
              "Content Management",
              "Branding",
              "Templates",
              "Site Management",
              "User Experience",
              "Analytics",
              "Mobile Optimization",
              "Integration"
            ]
          },
          "maturity": {
            "confidence": 0.84,
            "maturity": "well_known",
            "reasoning": "Commonly listed in Salesforce admin/dev JDs for portals and communities; Salesforce continues active product investment and documentation, indicating broad market adoption rather than niche use."
          },
          "skill_id": "salesforce-experience-cloud",
          "vendor_license": {
            "confidence": 0.9,
            "license": "other_open",
            "vendor": "Salesforce",
            "year_introduced": 2021
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Builds and customizes Salesforce Experience Cloud sites, portals, and communities for external users. This skill fits here because it centers on configuring branded digital experiences, access patterns, and page behavior within the Salesforce platform.",
            "exemplar_skills": [
              "Salesforce Experience Cloud",
              "Experience Builder",
              "Salesforce Communities",
              "Lightning Web Components for Experience Cloud",
              "Experience Cloud site configuration"
            ],
            "in_scope": "Salesforce Experience Cloud, Experience Builder, Lightning pages for communities, branded portals, customer and partner sites, audience targeting, site templates, CMS content delivery, navigation and page composition, guest user experience, community branding",
            "name": "Salesforce Experience Cloud Development",
            "out_of_scope": "Core CRM object modeling and sales workflows, Apex business logic for internal apps, generic web frontend frameworks outside Salesforce, identity platform design beyond site-level access",
            "overlap_flags": [
              {
                "reason": "Experience Cloud sites often require authentication, sharing, and external user access design, which can overlap with broader identity architecture.",
                "with_dim_id": "identity-and-access-architecture",
                "with_dim_name": null,
                "with_role": "Cloud Architect"
              },
              {
                "reason": "Experience Cloud pages are web experiences and may involve responsive layout work, but the Salesforce-specific site platform is the primary concern.",
                "with_dim_id": "responsive-and-mobile-web-design",
                "with_dim_name": null,
                "with_role": "Frontend Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          },
          {
            "description": "Covers the access-control and user-experience aspects of Salesforce external portals, including login flows, permissions, and audience segmentation. This belongs here when the skill is used to manage who can see and do what inside an Experience Cloud site.",
            "exemplar_skills": [
              "Salesforce Experience Cloud",
              "Experience Cloud access control",
              "Salesforce community user permissions",
              "sharing sets",
              "guest user permissions"
            ],
            "in_scope": "external user access, partner portal permissions, customer portal login, sharing sets, profiles and permission sets for sites, guest user access, audience rules, authentication entry points, site visibility controls, Salesforce Experience Cloud",
            "name": "Salesforce Portal Access Management",
            "out_of_scope": "Enterprise IAM products and federation architecture, internal Salesforce admin tasks unrelated to external sites, general application authentication libraries, non-Salesforce web portal frameworks",
            "overlap_flags": [
              {
                "reason": "Login and session behavior for Experience Cloud can resemble general auth flows, but this dimension is specifically about Salesforce portal access.",
                "with_dim_id": "authentication-and-session-handling",
                "with_dim_name": null,
                "with_role": "Android Engineer, Frontend Engineer, Full Stack Engineer, Hybrid Mobile Developer, Ios engineer"
              },
              {
                "reason": "External portal identity features may touch vendor IAM tools, though the Salesforce site access model is the main focus here.",
                "with_dim_id": "identity-and-access-management-products",
                "with_dim_name": null,
                "with_role": "Cybersecurity Engineer"
              }
            ],
            "tentative_id": "d_init_02"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Salesforce Experience Cloud",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 2 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [
            "d_init_02"
          ],
          "skill_id": "salesforce-experience-cloud"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "enterprise-saas",
            "cloud",
            "frontend",
            "responsive-web-development",
            "api-integration",
            "analytics",
            "ui-ux",
            "agentic-systems"
          ],
          "requires": [],
          "skill_id": "salesforce-experience-cloud",
          "suppress_on_match": []
        },
        "skill_id": "salesforce-experience-cloud",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.97,
          "name": "Salesforce Experience Cloud",
          "reasoning": "By the Vendor SaaS = Platform rule, Salesforce Experience Cloud is a hosted multi-tenant Salesforce offering with APIs and managed services, so it is fundamentally a Platform rather than a Tool or Service.",
          "skill_id": "salesforce-experience-cloud",
          "subtype": "customer_experience_platform",
          "type": "Platform"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [],
      "input_skill": "Salesforce CPQ",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": null,
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "ServiceNow",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "ServiceNow",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Platform",
          "skill_nature": "PLATFORM",
          "sub_category": "it_service_management_platform",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "ServiceNow is a specific ITSM platform name; typical JDs won\u2019t confuse it with other distinct ITSM tools."
          },
          "context_keywords": {
            "context_keywords": [
              "ITSM",
              "workflow automation",
              "incident management",
              "change management",
              "service catalog",
              "CMDB",
              "Orchestration",
              "Service Portal",
              "Knowledge Management",
              "Performance Analytics",
              "Scripting",
              "REST API",
              "IntegrationHub",
              "Virtual Agent",
              "Discovery"
            ]
          },
          "maturity": {
            "confidence": 0.94,
            "maturity": "well_known",
            "reasoning": "ServiceNow appears in many enterprise ITSM/ITOM job descriptions and is a common platform in large orgs; its vendor ecosystem and certification pipeline signal broad hiring demand."
          },
          "skill_id": "servicenow",
          "vendor_license": {
            "confidence": 0.95,
            "license": "proprietary",
            "vendor": "ServiceNow, Inc.",
            "year_introduced": 2004
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Vendor platforms used to manage IT service workflows, incidents, requests, changes, and asset records. ServiceNow belongs here because it is a core enterprise system for service desk automation and operational process management.",
            "exemplar_skills": [
              "ServiceNow",
              "ITSM",
              "incident management",
              "change management",
              "service catalog",
              "CMDB",
              "asset management",
              "workflow automation"
            ],
            "in_scope": "ServiceNow, incident management, service catalog, request fulfillment, change management, problem management, CMDB, asset management, workflow automation, approvals, SLA tracking, ITSM modules",
            "name": "IT Service Management Platforms",
            "out_of_scope": "Cloud infrastructure provisioning, application code frameworks, identity provider administration, observability tooling, generic ticketing concepts without a platform focus",
            "overlap_flags": [
              {
                "reason": "ServiceNow workflows can participate in release approvals and change windows, but that dimension owns deployment execution mechanics.",
                "with_dim_id": "deployment-automation-and-rollouts",
                "with_dim_name": null,
                "with_role": "DevOps Engineer"
              },
              {
                "reason": "ServiceNow is often used during incident handling, but that dimension covers the operational response process rather than the platform itself.",
                "with_dim_id": "incident-response-support",
                "with_dim_name": null,
                "with_role": "ML Ops Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "ServiceNow",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "servicenow"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "enterprise-saas",
            "api-integration",
            "api",
            "site-reliability-engineering",
            "runbooks",
            "automation-scripts"
          ],
          "requires": [],
          "skill_id": "servicenow",
          "suppress_on_match": []
        },
        "skill_id": "servicenow",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.96,
          "name": "ServiceNow",
          "reasoning": "By the Vendor SaaS = Platform rule, ServiceNow is a hosted multi-tenant SaaS environment with APIs and managed capabilities, not software you run yourself.",
          "skill_id": "servicenow",
          "subtype": "it_service_management_platform",
          "type": "Platform"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Jira",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Jira",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Tool",
          "skill_nature": "TOOL",
          "sub_category": "issue_tracking_tool",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "\u201cJira\u201d is a specific, widely recognized issue-tracking tool; unlikely to be confused with other catalog skills."
          },
          "context_keywords": {
            "context_keywords": [
              "Agile",
              "Scrum",
              "Kanban",
              "backlog",
              "sprint",
              "issue tracking",
              "workflow",
              "epics",
              "user stories",
              "sprint planning",
              "JQL",
              "dashboard",
              "plugins",
              "integration",
              "reporting"
            ]
          },
          "maturity": {
            "confidence": 0.97,
            "maturity": "well_known",
            "reasoning": "Jira appears in a large share of software job descriptions for issue tracking/agile workflows and remains Atlassian\u2019s flagship product with strong enterprise adoption."
          },
          "skill_id": "jira",
          "vendor_license": {
            "confidence": 0.95,
            "license": "other_open",
            "vendor": "Atlassian",
            "year_introduced": 2002
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Tools and practices for planning, tracking, and coordinating engineering work through issues, boards, workflows, and release tasks. Jira belongs here because it is a primary system for backlog management, sprint execution, and cross-team work visibility.",
            "exemplar_skills": [
              "Jira",
              "issue tracking",
              "backlog management",
              "sprint planning",
              "workflow configuration",
              "agile board management"
            ],
            "in_scope": "Jira, issue creation and triage, backlog grooming, sprint boards, workflow states, epics and stories, task assignment, status transitions, release tracking, custom fields, filters and dashboards",
            "name": "Work Tracking and Issue Management",
            "out_of_scope": "Source control hosting, CI/CD automation, test execution, and incident paging, which belong to code management, deployment, quality, and operations dimensions",
            "overlap_flags": [
              {
                "reason": "Jira is often used to coordinate release tasks, but the release process itself belongs to runbooks and operational documentation.",
                "with_dim_id": "release-documentation-and-runbooks",
                "with_dim_name": null,
                "with_role": "DevOps Engineer"
              },
              {
                "reason": "Jira may track rollout approvals and deployment tickets, but automated promotion and rollback mechanisms are a separate dimension.",
                "with_dim_id": "deployment-automation-and-rollouts",
                "with_dim_name": null,
                "with_role": "DevOps Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Jira",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "jira"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "api",
            "eclipse",
            "spring",
            "tomcat",
            "elk",
            "wireguard"
          ],
          "requires": [],
          "skill_id": "jira",
          "suppress_on_match": []
        },
        "skill_id": "jira",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.98,
          "name": "Jira",
          "reasoning": "Jira is software you operate as a user for issue tracking and project management, so by the Tool vs Framework rule it is a Tool rather than a hosted platform or a library/framework.",
          "skill_id": "jira",
          "subtype": "issue_tracking_tool",
          "type": "Tool"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    },
    {
      "aliases_in_db": [],
      "canonical": null,
      "dimensions": [
        {
          "dimension": {
            "difficulty_hint": "well_known",
            "display_name": "React Frontend Development",
            "id": 96,
            "rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
            "slug": "d_init_01",
            "source": "db"
          },
          "input_skill": "Copado",
          "llm_role": null,
          "roles_from_db": []
        }
      ],
      "input_skill": "Copado",
      "matched_via": null,
      "new_alias_persisted": false,
      "new_alias_text": null,
      "new_skill_meta": {
        "derived": {
          "category": "Platform",
          "skill_nature": "PLATFORM",
          "sub_category": "devops_platform",
          "typical_lifespan": "EVERGREEN",
          "version_strategy": "NOT_APPLICABLE",
          "volatility": "STABLE"
        },
        "enrichment": {
          "ambiguity": {
            "ambiguity_flag": false,
            "confused_with": [],
            "reasoning": "Copado is a specific DevOps/CI-CD platform name; unlikely to be confused with other catalog skills."
          },
          "context_keywords": {
            "context_keywords": [
              "CI/CD",
              "Salesforce",
              "release management",
              "DevOps",
              "automation",
              "version control",
              "pipeline",
              "integration",
              "test automation",
              "deployment",
              "Git",
              "environment management",
              "monitoring",
              "rollback",
              "collaboration"
            ]
          },
          "maturity": {
            "confidence": 0.88,
            "maturity": "niche",
            "reasoning": "Copado appears in Salesforce-focused DevOps job postings, but JD volume is far below mainstream CI/CD tools like GitHub Actions or Jenkins; market demand is concentrated in the Salesforce ecosystem."
          },
          "skill_id": "copado",
          "vendor_license": {
            "confidence": 0.9,
            "license": "other_open",
            "vendor": "Copado",
            "year_introduced": 2013
          },
          "versioning": {
            "current_version": null,
            "version_aliases": {},
            "versioned": false
          }
        },
        "keep_log": [],
        "locked_dimensions": [
          {
            "description": "Tools and practices for automating Salesforce deployments, change promotion, and release governance across orgs and environments. Copado belongs here because it is a Salesforce-focused DevOps platform used to manage metadata movement, approvals, and CI/CD for Salesforce teams.",
            "exemplar_skills": [
              "Copado",
              "Salesforce deployment automation",
              "Salesforce CI/CD",
              "metadata deployment",
              "org-to-org promotion",
              "sandbox to production release"
            ],
            "in_scope": "Copado, Salesforce metadata deployment, org-to-org promotion, release pipelines for Salesforce, change sets automation, sandbox to production releases, approval gates, rollback support, Salesforce CI/CD, environment management, release governance",
            "name": "Salesforce Release Automation",
            "out_of_scope": "Generic cloud infrastructure provisioning, non-Salesforce application deployment, source control concepts without Salesforce release context, test automation unrelated to release promotion, ITSM ticketing workflows",
            "overlap_flags": [
              {
                "reason": "Copado is a specialized deployment automation tool, but this dimension is broader and not Salesforce-specific.",
                "with_dim_id": "deployment-automation-and-rollouts",
                "with_dim_name": null,
                "with_role": "DevOps Engineer"
              },
              {
                "reason": "Copado release processes often rely on runbooks and release notes, but documentation is not the primary skill cluster.",
                "with_dim_id": "release-documentation-and-runbooks",
                "with_dim_name": null,
                "with_role": "DevOps Engineer"
              }
            ],
            "tentative_id": "d_init_01"
          }
        ],
        "merge_log": [],
        "placed": {
          "name": "Copado",
          "placement_confidence": 0.92,
          "primary_dimension": "d_init_01",
          "reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
          "secondary_dimensions": [],
          "skill_id": "copado"
        },
        "relationships": {
          "child_skills": [],
          "parent_skills": [],
          "related_to": [
            "prefect",
            "pachyderm",
            "containers",
            "eclipse",
            "tomcat",
            "gcp",
            "android",
            "ios"
          ],
          "requires": [],
          "skill_id": "copado",
          "suppress_on_match": []
        },
        "skill_id": "copado",
        "split_log": [],
        "typed": {
          "alternatives_considered": [],
          "confidence": 0.88,
          "name": "Copado",
          "reasoning": "Copado is best classified as a Platform because it is a commercial SaaS DevOps environment with hosted capabilities and APIs rather than software users run themselves, matching the Vendor SaaS = Platform rule.",
          "skill_id": "copado",
          "subtype": "devops_platform",
          "type": "Platform"
        },
        "warnings": []
      },
      "source_tag": "llm",
      "was_in_llm_skills": true
    }
  ],
  "unmatched_skills": [
    "Salesforce",
    "Apex",
    "Lightning",
    "Visualforce",
    "Aura",
    "Lightning Web Components",
    "Developer Console",
    "Workbench",
    "Salesforce Debug Logs",
    "Salesforce Sales Cloud",
    "Salesforce Service Cloud",
    "Salesforce Experience Cloud",
    "Salesforce CPQ",
    "ServiceNow",
    "Jira",
    "Copado"
  ]
}

{}