Pipeline run
23f7a1f2-04df-4eea-a7be-6a787c95c6a3
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionNature of work
no kras
Vague JD — no KRAs present to derive a specific nature of work.
Tech stack maturity
Mainstream Modern
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (0)
Skill cluster (0 dimension groups, role-scoped)
Status:
completed
Created: 2026-05-08T11:06:04.317307Z
Updated: 2026-05-08T11:08:11.501413Z
API 3 duration: 889 ms
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
Data Analyst
slug: data-analyst · id: 20 · source: db
Most evidence points to reporting and dashboard development, and Data Analyst is the only DB candidate directly tied to that largest dimension.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
13
Skipped
Job description
Business Analyst Job Description Job Title: Business Analyst Experience: 2–5 Years Location: Remote / Hybrid / On-site About the Role We are looking for a Business Analyst to bridge the gap between business needs and technical solutions. The ideal candidate will work closely with stakeholders, product teams, and developers to gather requirements, analyze business processes, and support successful project delivery. Key Responsibilities Gather, analyze, and document business requirements from stakeholders Translate business needs into functional specifications and user stories Work with cross-functional teams including developers, QA, and product managers Conduct requirement workshops, stakeholder meetings, and process analysis Create BRDs, FRDs, workflows, process diagrams, and reports Analyze data to identify trends, opportunities, and business insights Support UAT (User Acceptance Testing) and validate delivered solutions Monitor project progress and help manage risks and dependencies Improve existing business processes and recommend optimization strategies Ensure solutions align with business goals and operational needs Required Skills Strong understanding of business analysis methodologies Experience with requirement gathering and documentation Knowledge of Agile/Scrum methodologies Excellent communication and stakeholder management skills Strong analytical and problem-solving abilities Experience with tools like JIRA, Confluence, Excel, Visio, or Power BI Ability to create reports, dashboards, and process flows Understanding of SDLC and software development processes Preferred Qualifications Bachelor’s degree in Business, Computer Science, IT, or related field Experience working with technical and non-technical teams Familiarity with SQL, data analysis, or reporting tools is a plus Certification such as CBAP, CCBA, or Agile certification is preferred Nice to Have Experience in fintech, healthcare, e-commerce, or SaaS domains Exposure to BI tools like Tableau or Power BI Basic understanding of APIs and databases Benefits Competitive salary Flexible work environment Health insurance Learning and development opportunities Career growth and mentorship Paid leaves and company benefits
history_view bundle (older API). Showing raw API payloads below.
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| Power BI | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Tableau | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Argo Workflows | in_db |
Workflow Orchestration Systems
workflow-orchestration-systems
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| APIs | new |
API Design and Integration
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CBAP | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| CCBA | new |
Business Analysis Certification
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| FRDs | new |
Functional Requirements Documentation
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Knowledge | new |
Domain Knowledge and Business Context
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SDLC | new |
Software Delivery Lifecycle
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| SaaS | new |
SaaS Product Model
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| UAT | new |
User Acceptance Testing Execution
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| Visio | new |
Diagramming and Process Modeling
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_proposed | APIs | type=Protocol subtype=application_programming_interfaces nature=PROTOCOL lifespan=EVERGREEN | |
| canonical_skill_proposed | CBAP | type=Certification subtype=business_analysis_professional_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | CCBA | type=Certification subtype=business_analysis_certification nature=CREDENTIAL lifespan=EVERGREEN | |
| canonical_skill_proposed | Excel | type=Tool subtype=spreadsheet_software nature=TOOL lifespan=EVERGREEN | |
| canonical_skill_proposed | FRDs | type=Concept subtype=functional_requirements_document nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Knowledge | type=Concept subtype=general_knowledge nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | QA | type=Methodology subtype=quality_assurance nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | SDLC | type=Methodology subtype=software_development_lifecycle nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | SaaS | type=Platform subtype=software_as_a_service nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | UAT | type=Methodology subtype=user_acceptance_testing nature=METHODOLOGY lifespan=EVERGREEN | |
| canonical_skill_proposed | Visio | type=Tool subtype=diagramming_tool nature=TOOL lifespan=EVERGREEN | |
| dimension_proposed | API Design and Integration | |
| dimension_skill_link_proposed | APIs ↔ API Design and Integration | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CBAP ↔ Business Analysis Certification | |
| dimension_proposed | Business Analysis Certification | |
| dimension_skill_link_proposed | CCBA ↔ Business Analysis Certification | |
| dimension_proposed | Spreadsheet Analysis and Modeling | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Modeling | |
| dimension_proposed | Functional Requirements Documentation | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documentation | |
| dimension_proposed | Domain Knowledge and Business Context | |
| dimension_skill_link_proposed | Knowledge ↔ Domain Knowledge and Business Context | |
| dimension_proposed | Software Delivery Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Delivery Lifecycle | |
| dimension_proposed | SaaS Product Model | |
| dimension_skill_link_proposed | SaaS ↔ SaaS Product Model | |
| dimension_proposed | User Acceptance Testing Execution | |
| dimension_skill_link_proposed | UAT ↔ User Acceptance Testing Execution | |
| dimension_proposed | Diagramming and Process Modeling | |
| dimension_skill_link_proposed | Visio ↔ Diagramming and Process Modeling |
API 1 — extract-from-jd click to toggle
{
"filtered_unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
],
"final_non_skills": [
"2\u20135",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"requirements",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"teams",
"work"
],
"final_skills": [
"Power BI",
"Tableau",
"Argo Workflows",
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"software",
"specifications",
"stories",
"tools",
"trends",
"workshops"
],
"initial_skills": [
"Power BI",
"Tableau",
"Argo Workflows"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt explicitly titles the role as Business Analyst and emphasizes requirements, process analysis, and stakeholder coordination.",
"role_archetype": "Business analysis professional focused on requirements gathering, stakeholder communication, process analysis, and solution specification.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Experience",
"Exposure",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"candidate",
"commerce",
"company",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"domains",
"environment",
"field",
"gap",
"gathering",
"goals",
"growth",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"needs",
"opportunities",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"requirement",
"requirements",
"risks",
"salary",
"site",
"solutions",
"stakeholder",
"stakeholders",
"teams",
"work"
],
"llm_skills": [
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"software",
"specifications",
"stories",
"tools",
"trends",
"workshops"
],
"run_id": null,
"unknown_words": [
"2\u20135",
"APIs",
"Ability",
"Acceptance",
"Analyst",
"BI",
"BRDs",
"Bachelor",
"Benefits",
"Business",
"CBAP",
"CCBA",
"Career",
"Certification",
"Computer",
"Conduct",
"Description",
"Ensure",
"Excel",
"Experience",
"Exposure",
"FRDs",
"Familiarity",
"Gather",
"Health",
"Hybrid",
"Job",
"Key",
"Knowledge",
"Learning",
"Location",
"Monitor",
"Power",
"Preferred",
"QA",
"Qualifications",
"Remote",
"Required",
"Responsibilities",
"Role",
"SDLC",
"SaaS",
"Science",
"Skills",
"Support",
"Testing",
"Title",
"UAT",
"Understanding",
"User",
"Visio",
"Years",
"abilities",
"analysis",
"benefits",
"business",
"candidate",
"certification",
"commerce",
"communication",
"company",
"data",
"databases",
"degree",
"delivery",
"dependencies",
"developers",
"development",
"diagrams",
"document",
"documentation",
"domains",
"environment",
"field",
"fintech",
"gap",
"gathering",
"goals",
"growth",
"healthcare",
"insights",
"insurance",
"leaves",
"management",
"managers",
"meetings",
"methodologies",
"needs",
"opportunities",
"optimization",
"problem",
"process",
"processes",
"product",
"progress",
"project",
"reporting",
"requirement",
"requirements",
"risks",
"salary",
"site",
"skills",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"understanding",
"user",
"work",
"workshops"
]
}
API 2 — extract-details
{
"alias_matches": [],
"candidate_roles": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "Most evidence points to reporting and dashboard development, and Data Analyst is the only DB candidate directly tied to that largest dimension.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Tableau",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing how systems expose capabilities through APIs and how those APIs are consumed across applications and services. This fits the target skill because APIs are the core interface for structured system integration and data exchange.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including requirements elicitation, stakeholder analysis, solution assessment, and business process modeling. CBAP belongs here because it is a business analysis credential rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts who elicit requirements, model processes, and support solution delivery. CCBA belongs here because it is an industry-recognized certification for business analysts rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using Excel to organize, analyze, and model business data for reporting and decision support. This fits a Business Analyst role because Excel is often the primary tool for ad hoc analysis, calculations, and lightweight scenario modeling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirements documents that define what a product or system must do. FRDs fit here because they capture business needs, scope, behaviors, and acceptance expectations in a structured specification.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Understanding the business domain, processes, terminology, and constraints needed to interpret requirements and make sound analysis decisions. This fits a Business Analyst because the skill is about knowing the subject matter well enough to translate needs into clear, actionable work.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software products. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Model",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including how the product is packaged, priced, provisioned, and consumed by customers. SaaS fits here because it refers to the delivery and business model rather than a specific technical implementation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing Execution",
"id": null,
"rationale": "Covers planning and running user acceptance tests to confirm a feature meets business requirements and is ready for sign-off. UAT belongs here because it is a manual, requirement-driven validation step focused on stakeholder acceptance rather than technical test automation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, org charts, swimlanes, and architecture diagrams for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Power BI",
"Tableau",
"Argo Workflows",
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"software",
"specifications",
"stories",
"tools",
"trends",
"workshops"
],
"input_llm_skills": [
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio",
"analysis",
"communication",
"data",
"databases",
"documentation",
"fintech",
"healthcare",
"insights",
"methodologies",
"optimization",
"reporting",
"software",
"specifications",
"stories",
"tools",
"trends",
"workshops"
],
"new_aliases_persisted": 0,
"run_id": "23f7a1f2-04df-4eea-a7be-6a787c95c6a3",
"skills_detail": [
{
"aliases_in_db": [
{
"alias_text": "Power BI",
"alias_type": "CANONICAL",
"id": 2535,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Power BI",
"id": 1884,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "power-bi",
"sub_category_id": 1618,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Power BI",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
}
],
"input_skill": "Power BI",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Tableau",
"alias_type": "CANONICAL",
"id": 2534,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Tableau",
"id": 1883,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "tableau",
"sub_category_id": 1618,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"input_skill": "Tableau",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
]
}
],
"input_skill": "Tableau",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [
{
"alias_text": "Argo Workflows",
"alias_type": "CANONICAL",
"id": 595,
"is_primary": true,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 11,
"display_name": "Argo Workflows",
"id": 380,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "TOOL",
"slug": "argo-workflows",
"sub_category_id": 335,
"typical_lifespan": "EVERGREEN",
"volatility": "EMERGING"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"input_skill": "Argo Workflows",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
]
}
],
"input_skill": "Argo Workflows",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": false
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing how systems expose capabilities through APIs and how those APIs are consumed across applications and services. This fits the target skill because APIs are the core interface for structured system integration and data exchange.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "APIs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Protocol",
"skill_nature": "PROTOCOL",
"sub_category": "application_programming_interfaces",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "APIs is a common, well-scoped engineering term in JDs and usually refers to application programming interfaces; it is not typically confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"REST",
"GraphQL",
"OpenAPI",
"Swagger",
"JSON",
"XML",
"OAuth 2.0",
"API gateway",
"endpoint",
"webhooks",
"rate limiting",
"versioning",
"microservices",
"SDK",
"Postman"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/API design appears in large volumes of job postings and is foundational in cloud vendor docs and SDK ecosystems."
},
"skill_id": "apis",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Designing how systems expose capabilities through APIs and how those APIs are consumed across applications and services. This fits the target skill because APIs are the core interface for structured system integration and data exchange.",
"exemplar_skills": [
"APIs",
"REST APIs",
"API design",
"endpoint design",
"webhooks",
"API versioning"
],
"in_scope": "APIs, REST APIs, endpoint design, request and response payloads, versioning, pagination, error handling, authentication for API access, webhook design",
"name": "API Design and Integration",
"out_of_scope": "Automated API test execution, UI behavior, database schema modeling, infrastructure provisioning, which belong to other dimensions",
"overlap_flags": [
{
"reason": "API design overlaps with endpoint verification, but that dimension owns automated testing rather than interface definition.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": "Automation Tester"
},
{
"reason": "Service integration and API design are closely related, but this dimension is narrower and centered on the API interface itself.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "APIs",
"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": "apis"
},
"relationships": {
"child_skills": [
"rest-apis",
"scripted-rest-api",
"outbound-rest-messages"
],
"parent_skills": [],
"related_to": [
"private-endpoints",
"acls",
"portal-pages",
"expressroute",
"aks",
"aws-iam",
"repository-pattern",
"deep-links",
"angularjs",
"refresh-tokens",
"aws-cdk",
"mock-servers",
"policy-as-code"
],
"requires": [
"http",
"json",
"grpc",
"oauth-2-0"
],
"skill_id": "apis",
"suppress_on_match": []
},
"skill_id": "apis",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "APIs",
"reasoning": "APIs are a communication interface standard between software systems, so by the Protocol rule they fit best as a protocol-like interface rather than a tool or platform.",
"skill_id": "apis",
"subtype": "application_programming_interfaces",
"type": "Protocol"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including requirements elicitation, stakeholder analysis, solution assessment, and business process modeling. CBAP belongs here because it is a business analysis credential rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CBAP",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CBAP",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_professional_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "CBAP is a specific certification acronym (Certified Business Analysis Professional) and is unlikely to be reasonably confused with another catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process improvement",
"UML",
"SWOT analysis",
"RACI",
"traceability matrix",
"workshops",
"facilitation",
"solution assessment"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CBAP is a widely recognized business analysis certification and appears in many BA job descriptions as a preferred credential, especially in enterprise and consulting roles."
},
"skill_id": "cbap",
"vendor_license": {
"confidence": 0.95,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2006
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Professional certification knowledge for business analysts, including requirements elicitation, stakeholder analysis, solution assessment, and business process modeling. CBAP belongs here because it is a business analysis credential rather than a technical implementation skill.",
"exemplar_skills": [
"CBAP",
"CCBA",
"business analysis certification",
"requirements elicitation",
"stakeholder analysis",
"business process modeling",
"solution assessment"
],
"in_scope": "CBAP, CCBA, business analysis certification, requirements elicitation, stakeholder analysis, business process modeling, solution assessment, business case analysis, BABOK knowledge areas",
"name": "Business Analysis Certification",
"out_of_scope": "Software development, project management certification, data analysis tooling, QA test execution, product design; those belong to engineering, delivery, or analytics dimensions",
"overlap_flags": [],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CBAP",
"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": "cbap"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"risk-based-testing",
"capacity-planning"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.99,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is not a concept or methodology but a certification.",
"skill_id": "cbap",
"subtype": "business_analysis_professional_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts who elicit requirements, model processes, and support solution delivery. CCBA belongs here because it is an industry-recognized certification for business analysts rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "CCBA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Certification",
"skill_nature": "CREDENTIAL",
"sub_category": "business_analysis_certification",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"cbap"
],
"reasoning": "CCBA is a business analysis certification acronym and can be mistaken for the closely related CBAP certification in job descriptions, especially when abbreviations are used loosely."
},
"context_keywords": {
"context_keywords": [
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"use cases",
"user stories",
"gap analysis",
"business process mapping",
"solution assessment",
"traceability matrix",
"SWOT analysis",
"MoSCoW",
"UML",
"workshop facilitation"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CCBA is a widely recognized business analysis certification; it appears in many job descriptions for BA roles and is offered by IIBA as a mainstream credential alongside CBAP."
},
"skill_id": "ccba",
"vendor_license": {
"confidence": 0.94,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2008
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and professional standards for analysts who elicit requirements, model processes, and support solution delivery. CCBA belongs here because it is an industry-recognized certification for business analysts rather than a technical implementation skill.",
"exemplar_skills": [
"CCBA",
"CBAP",
"ECBA",
"IIBA certification",
"requirements elicitation",
"stakeholder analysis",
"process modeling"
],
"in_scope": "CCBA, CBAP, ECBA, business analysis certification, IIBA certification, requirements elicitation, stakeholder analysis, process modeling, solution assessment",
"name": "Business Analysis Certification",
"out_of_scope": "Software engineering implementation, project management certification, UX research methods, data analysis tooling, which belong to other dimensions",
"overlap_flags": [
{
"reason": "Business analysts may work with service boundaries and integrations, but CCBA itself is a professional BA credential rather than an architecture skill.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "CCBA",
"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": "ccba"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"scorecards",
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"risk-based-testing",
"charter-based-testing",
"session-based-testing"
],
"requires": [],
"skill_id": "ccba",
"suppress_on_match": []
},
"skill_id": "ccba",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CCBA",
"reasoning": "CCBA is a formal third-party credential, so by the Certification rule it is a Certification rather than a concept or methodology.",
"skill_id": "ccba",
"subtype": "business_analysis_certification",
"type": "Certification"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using Excel to organize, analyze, and model business data for reporting and decision support. This fits a Business Analyst role because Excel is often the primary tool for ad hoc analysis, calculations, and lightweight scenario modeling.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Excel",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Excel",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "spreadsheet_software",
"typical_lifespan": "EVERGREEN",
"version_strategy": "SEPARATE_ENTITY",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Excel in JDs almost always refers to Microsoft Excel spreadsheet software; the name is specific and not typically confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"pivot tables",
"VLOOKUP",
"XLOOKUP",
"INDEX MATCH",
"macros",
"VBA",
"Power Query",
"Power Pivot",
"data validation",
"conditional formatting",
"SUMIFS",
"COUNTIFS",
"charts",
"dashboards",
"CSV"
]
},
"maturity": {
"confidence": 0.99,
"maturity": "well_known",
"reasoning": "Excel appears in a very large share of business, finance, ops, and analyst job descriptions and remains a default spreadsheet tool across Microsoft 365 deployments."
},
"skill_id": "excel",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1985
},
"versioning": {
"current_version": "Microsoft 365 / Excel 2024",
"version_aliases": {
"Excel 2003": "Excel 2003",
"Excel 2007": "Excel 2007",
"Excel 2010": "Excel 2010",
"Excel 2013": "Excel 2013",
"Excel 2016": "Excel 2016",
"Excel 2019": "Excel 2019",
"Excel 2021": "Excel 2021",
"Excel 2024": "Microsoft 365 / Excel 2024",
"Excel 365": "Microsoft 365 / Excel 2024",
"Microsoft 365 Excel": "Microsoft 365 / Excel 2024"
},
"versioned": true
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Using Excel to organize, analyze, and model business data for reporting and decision support. This fits a Business Analyst role because Excel is often the primary tool for ad hoc analysis, calculations, and lightweight scenario modeling.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"SUMIFS",
"IF formulas",
"What-If Analysis",
"Data Validation"
],
"in_scope": "Excel, formulas, functions, pivot tables, charts, conditional formatting, data validation, lookup functions, what-if analysis, basic financial models, ad hoc business analysis",
"name": "Spreadsheet Analysis and Modeling",
"out_of_scope": "SQL-based data warehousing, statistical programming in R or Python, enterprise BI dashboard development, ETL pipeline engineering, presentation design in PowerPoint",
"overlap_flags": [
{
"reason": "Excel is often used to combine and reshape source tables, but that dimension owns the broader data-wrangling workflow.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": "Data Analyst"
},
{
"reason": "Excel can support analysis workflows, but notebooks own reproducible scripted analysis rather than spreadsheet-based work.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": "Data Scientist"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Excel",
"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": "excel"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards",
"summary-statistics",
"scorecards",
"runbooks"
],
"requires": [],
"skill_id": "excel",
"suppress_on_match": []
},
"skill_id": "excel",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Excel",
"reasoning": "Excel is software you operate directly as a user, so by the Tool vs Framework rule it is a Tool rather than a framework or platform.",
"skill_id": "excel",
"subtype": "spreadsheet_software",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirements documents that define what a product or system must do. FRDs fit here because they capture business needs, scope, behaviors, and acceptance expectations in a structured specification.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "FRDs",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "FRDs",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "functional_requirements_document",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "FRDs is a fairly specific requirements-document acronym; in typical JDs it would be read as functional requirements documents, not a common overloaded term with a close catalog alternative."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"requirements traceability",
"functional specification",
"business requirements",
"scope definition",
"process flows",
"wireframes",
"stakeholder review",
"sign-off",
"change requests",
"non-functional requirements"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "Functional requirements documents are a standard artifact in software and systems JDs/SDLCs, commonly requested alongside BRDs/PRDs and used across enterprise delivery teams."
},
"skill_id": "frds",
"vendor_license": {
"confidence": 0.98,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers writing and maintaining functional requirements documents that define what a product or system must do. FRDs fit here because they capture business needs, scope, behaviors, and acceptance expectations in a structured specification.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"requirements gathering",
"business requirements analysis",
"scope definition",
"acceptance criteria writing"
],
"in_scope": "FRDs, functional requirements documents, business requirements translation, scope definition, feature behavior specification, acceptance criteria, requirements traceability",
"name": "Functional Requirements Documentation",
"out_of_scope": "technical architecture design, code implementation, test automation, UX visual design, project scheduling, operational runbooks",
"overlap_flags": [
{
"reason": "FRDs often inform test cases, but this dimension owns the actual test design and execution work.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "Some FRDs describe service interactions, but architecture and integration design belong to the backend architecture dimension.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "FRDs",
"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": "frds"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"change-requests",
"contract-tests",
"risk-based-testing",
"runbooks",
"rollback-readiness"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 it is not a way of working or process.",
"Format: ruled out \u2014 although documents have structure, FRDs fundamentally denote a requirements artifact, not a wire/data format."
],
"confidence": 0.78,
"name": "FRDs",
"reasoning": "FRDs are a named knowledge artifact describing requirements, so under the Concept vs Methodology rule they fit best as a concept rather than a process or tool.",
"skill_id": "frds",
"subtype": "functional_requirements_document",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Understanding the business domain, processes, terminology, and constraints needed to interpret requirements and make sound analysis decisions. This fits a Business Analyst because the skill is about knowing the subject matter well enough to translate needs into clear, actionable work.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Knowledge",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Knowledge",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Concept",
"skill_nature": "CONCEPT",
"sub_category": "general_knowledge",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"knowledge_management",
"knowledge_graph",
"knowledge_base"
],
"reasoning": "\"Knowledge\" is a very broad concept and in JDs could easily mean knowledge management, knowledge graph, or knowledge base work rather than the generic concept."
},
"context_keywords": {
"context_keywords": [
"domain expertise",
"subject matter expert",
"institutional knowledge",
"knowledge base",
"knowledge management",
"knowledge transfer",
"lessons learned",
"best practices",
"documentation",
"taxonomy",
"ontology",
"information architecture",
"data governance",
"expertise mapping"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "niche",
"reasoning": "\u201cKnowledge\u201d is a generic concept, not a specific engineering skill; it rarely appears as a standalone requirement in job descriptions compared with concrete tools or languages."
},
"skill_id": "knowledge",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Understanding the business domain, processes, terminology, and constraints needed to interpret requirements and make sound analysis decisions. This fits a Business Analyst because the skill is about knowing the subject matter well enough to translate needs into clear, actionable work.",
"exemplar_skills": [
"Knowledge",
"Business domain knowledge",
"Process knowledge",
"Industry knowledge",
"Product knowledge",
"Regulatory knowledge"
],
"in_scope": "Knowledge, business domain understanding, process knowledge, terminology, policies, regulations, stakeholder context, product knowledge, industry concepts",
"name": "Domain Knowledge and Business Context",
"out_of_scope": "Data modeling and analysis techniques, requirements elicitation methods, test case design, technical implementation details, project scheduling",
"overlap_flags": [],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Knowledge",
"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": "knowledge"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "knowledge",
"suppress_on_match": []
},
"skill_id": "knowledge",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Knowledge",
"reasoning": "This is a named knowledge unit rather than a way of working or a system shape, so by the Concept vs Methodology and Architecture rules it fits Concept.",
"skill_id": "knowledge",
"subtype": "general_knowledge",
"type": "Concept"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "QA",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "quality_assurance",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"quality_control",
"test_automation"
],
"reasoning": "\"QA\" is a common abbreviation for quality assurance, but in JDs it can also be used loosely for quality control or testing/automation roles, so an extractor could confuse it with nearby catalog skills."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plan",
"test strategy",
"regression testing",
"smoke testing",
"UAT",
"defect tracking",
"bug triage",
"test automation",
"Selenium",
"JIRA",
"manual testing",
"acceptance criteria",
"traceability matrix",
"test coverage"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "QA appears in a large share of software job descriptions and is a standard hiring-pipeline requirement; market listings commonly pair it with test automation and CI/CD rather than treating it as niche."
},
"skill_id": "qa",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [],
"merge_log": [
{
"a_dim_id": "d_init_01",
"a_name": "Manual Test Case Execution",
"a_role": "__skill_focal__",
"b_dim_id": "test-case-design-and-execution",
"b_name": "Test Case Design and Execution",
"b_role": "Manual Tester",
"into": "d_merge_01",
"into_name": "Manual Test Case Design and Execution",
"merged_from": [
"d_init_01",
"test-case-design-and-execution"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same manual QA activity: creating and running human-executed tests from requirements/acceptance criteria, then checking results and regressions. Dim A includes designing and running manual tests, acceptance criteria validation, defect reproduction, and exploratory testing; Dim B says designing, reviewing, and executing manual test cases for features, fixes, and regressions. The exemplar skills also overlap heavily (QA, manual testing, test case design/execution, regression testing, exploratory testing).",
"similarity": 0.775171067538063
},
{
"a_dim_id": "d_init_02",
"a_name": "Data Quality Assessment",
"a_role": "__skill_focal__",
"b_dim_id": "data-quality-assessment",
"b_name": "Data Quality Assessment",
"b_role": "Data Analyst",
"into": "d_merge_02",
"into_name": "Analytical Data Quality Assessment",
"merged_from": [
"d_init_02",
"data-quality-assessment"
],
"pair_kind": "cross_role",
"reasoning": "Both dims describe the same analyst-facing data-quality work: checking completeness, consistency, accuracy, and bias risk to judge whether data is fit for analysis/reporting. Dim A\u2019s QA, data validation, report reconciliation, and source-to-target verification are concrete forms of the same activity Dim B describes as assessing datasets for analytical suitability and interpretation risk. The wording differs, but the skill cluster is identical.",
"similarity": 0.7370295387192431
}
],
"placed": {
"name": "QA",
"placement_confidence": 0.0,
"primary_dimension": "d_init_00",
"reasoning": "Stub placement: no locked_dimensions after Stage 2/3; downstream containment and enrichment use placeholders only.",
"secondary_dimensions": [],
"skill_id": "qa"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"test-case-authoring",
"risk-based-testing",
"cross-browser-testing",
"session-based-testing",
"charter-based-testing",
"defect-retest",
"health-checks"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.88,
"name": "QA",
"reasoning": "QA is best treated as a methodology because it refers to the process and practices of assuring quality rather than a specific tool, framework, or standard.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "Methodology"
},
"warnings": [
"placement_stub_no_locked_dimensions"
]
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software products. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SDLC",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_development_lifecycle",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SDLC is a standard, well-known acronym for software development lifecycle and is usually unambiguous in job descriptions."
},
"context_keywords": {
"context_keywords": [
"requirements gathering",
"design review",
"implementation",
"code review",
"testing",
"QA",
"UAT",
"deployment",
"release management",
"change management",
"Agile",
"Scrum",
"waterfall",
"CI/CD",
"DevOps"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and enterprise process docs; it appears broadly across hiring pipelines and vendor training, not as a niche specialty."
},
"skill_id": "sdlc",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software products. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical practice.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"release management",
"change control",
"requirements analysis",
"defect triage"
],
"in_scope": "SDLC, requirements analysis, design, implementation, testing, release management, maintenance, change control, defect triage, iterative delivery, waterfall, agile delivery",
"name": "Software Delivery Lifecycle",
"out_of_scope": "Unit testing frameworks, API test automation, environment provisioning, deployment tooling, project portfolio management, which belong to more specific engineering or delivery dimensions",
"overlap_flags": [
{
"reason": "SDLC includes testing activities, but that catalog dimension owns the specific practice of designing and executing test cases.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "SDLC often touches environment flow, but that dimension owns the concrete provisioning and promotion work.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": "DevOps Engineer"
},
{
"reason": "SDLC can include design and implementation phases, but architecture and integration are a separate technical specialty.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SDLC",
"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": "sdlc"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"acceptance-criteria-validation",
"defect-retest",
"dependency-mapping",
"dashboards",
"scorecards"
],
"requires": [],
"skill_id": "sdlc",
"suppress_on_match": []
},
"skill_id": "sdlc",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "SDLC",
"reasoning": "By the Concept vs Methodology rule, SDLC is a way of working that describes the process of building software rather than a single knowledge unit or system shape.",
"skill_id": "sdlc",
"subtype": "software_development_lifecycle",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Model",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including how the product is packaged, priced, provisioned, and consumed by customers. SaaS fits here because it refers to the delivery and business model rather than a specific technical implementation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SaaS",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Platform",
"skill_nature": "PLATFORM",
"sub_category": "software_as_a_service",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "SaaS is a standard, well-scoped term for software as a service and is unlikely to be confused with a different catalog skill in typical job descriptions."
},
"context_keywords": {
"context_keywords": [
"multi-tenant",
"subscription billing",
"tenant isolation",
"self-service onboarding",
"usage-based pricing",
"provisioning",
"SSO",
"SCIM",
"API integrations",
"admin console",
"feature flags",
"entitlements",
"customer portal",
"SLAs",
"churn"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "SaaS is a standard cloud delivery model; job postings routinely ask for SaaS product, sales, and ops experience, and major vendors (Salesforce, Microsoft, Google) center offerings on it."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.88,
"license": "proprietary",
"vendor": "Salesforce",
"year_introduced": 1999
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers software delivered as a subscription-based hosted service, including how the product is packaged, priced, provisioned, and consumed by customers. SaaS fits here because it refers to the delivery and business model rather than a specific technical implementation.",
"exemplar_skills": [
"SaaS",
"subscription software",
"multi-tenant product design",
"hosted software delivery",
"recurring revenue model"
],
"in_scope": "SaaS, subscription software, hosted application delivery, multi-tenant product model, customer provisioning, usage-based access, recurring billing concepts, trial-to-paid conversion",
"name": "SaaS Product Model",
"out_of_scope": "cloud infrastructure operations, application security controls, API integration, mobile app development, on-premises licensing, data warehousing",
"overlap_flags": [
{
"reason": "SaaS products are often built as services, but this dimension is about the commercial delivery model rather than backend service decomposition.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "SaaS is sometimes a target state in modernization work, but that dimension focuses on migration strategy rather than the SaaS model itself.",
"with_dim_id": "migration-and-modernization-planning",
"with_dim_name": null,
"with_role": "Cloud Architect"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "SaaS",
"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": "saas"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"cloud-run",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed by the provider, so it is fundamentally a Platform.",
"skill_id": "saas",
"subtype": "software_as_a_service",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing Execution",
"id": null,
"rationale": "Covers planning and running user acceptance tests to confirm a feature meets business requirements and is ready for sign-off. UAT belongs here because it is a manual, requirement-driven validation step focused on stakeholder acceptance rather than technical test automation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "UAT",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "UAT",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "user_acceptance_testing",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "UAT in JDs almost always means User Acceptance Testing; the acronym is standard and unlikely to be mistaken for another catalog skill in typical hiring context."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test scripts",
"acceptance criteria",
"business users",
"end users",
"sign-off",
"test scenarios",
"defect triage",
"test plan",
"regression testing",
"stakeholder review",
"go-live",
"pilot testing",
"requirements validation",
"smoke testing"
]
},
"maturity": {
"confidence": 0.86,
"maturity": "well_known",
"reasoning": "UAT appears in many QA/test analyst and product roles as a standard pre-release signoff step; it is a common hiring-pipeline term rather than a niche tool or sunset practice."
},
"skill_id": "uat",
"vendor_license": {
"confidence": 0.99,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers planning and running user acceptance tests to confirm a feature meets business requirements and is ready for sign-off. UAT belongs here because it is a manual, requirement-driven validation step focused on stakeholder acceptance rather than technical test automation.",
"exemplar_skills": [
"UAT",
"user acceptance testing",
"acceptance testing",
"manual test execution",
"stakeholder sign-off",
"business requirement validation"
],
"in_scope": "UAT, user acceptance testing, acceptance test execution, business requirement validation, stakeholder sign-off testing, manual end-to-end scenario checks, defect logging from acceptance runs",
"name": "User Acceptance Testing Execution",
"out_of_scope": "Unit testing, API automation, performance testing, production monitoring, these belong to engineering test or operations dimensions rather than business acceptance validation",
"overlap_flags": [
{
"reason": "UAT is a specialized form of manual test execution, but this dimension is broader and owns general test case design and execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": "Manual Tester"
},
{
"reason": "UAT often depends on test environment readiness and access, but that dimension owns the coordination work rather than the acceptance testing itself.",
"with_dim_id": "environment-and-access-coordination",
"with_dim_name": null,
"with_role": "Cloud Migration Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "UAT",
"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": "uat"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"acceptance-criteria-checks",
"session-based-testing",
"test-case-authoring"
],
"requires": [],
"skill_id": "uat",
"suppress_on_match": []
},
"skill_id": "uat",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "UAT",
"reasoning": "UAT is a way of working for validating software with end users, so by the Concept vs Methodology rule it is a Methodology rather than a tool or concept.",
"skill_id": "uat",
"subtype": "user_acceptance_testing",
"type": "Methodology"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, org charts, swimlanes, and architecture diagrams for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Visio",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Tool",
"skill_nature": "TOOL",
"sub_category": "diagramming_tool",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "Visio is a specific Microsoft diagramming tool; in typical JDs it is unlikely to be confused with another catalog skill."
},
"context_keywords": {
"context_keywords": [
"flowchart",
"swimlane",
"process map",
"BPMN",
"UML",
"network diagram",
"org chart",
"wireframe",
"data flow diagram",
"ERD",
"business process",
"SIPOC",
"value stream map",
"cross-functional",
"blueprint"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "Microsoft Visio still appears in many enterprise job descriptions for process/network diagramming and is bundled in Microsoft 365/Office ecosystems, indicating broad ongoing use rather than sunset."
},
"skill_id": "visio",
"vendor_license": {
"confidence": 0.99,
"license": "proprietary",
"vendor": "Microsoft",
"year_introduced": 1992
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Covers creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, org charts, swimlanes, and architecture diagrams for analysis and documentation.",
"exemplar_skills": [
"Visio",
"process mapping",
"swimlane diagramming",
"org chart creation",
"workflow diagramming",
"UML diagramming"
],
"in_scope": "Visio, process flow diagrams, swimlane diagrams, org charts, UML sketches, network diagrams, system context diagrams, business process modeling, workflow mapping, diagram templates",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Requirements elicitation, stakeholder interviews, and solution design decisions, spreadsheet-based analysis and reporting, code-based diagram generation and infrastructure-as-code visuals",
"overlap_flags": [
{
"reason": "Architecture diagrams can overlap with service design, but this dimension focuses on the act of diagramming rather than backend integration patterns.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": "Backend Engineer"
},
{
"reason": "Visio may be used to document current-state and target-state migration views, but the planning and sequencing belong elsewhere.",
"with_dim_id": "migration-and-modernization-planning",
"with_dim_name": null,
"with_role": "Cloud Architect"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "Visio",
"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": "visio"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [],
"requires": [],
"skill_id": "visio",
"suppress_on_match": []
},
"skill_id": "visio",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "Visio",
"reasoning": "Visio is software you operate to create diagrams, so by the Tool vs Framework rule it is a Tool rather than something you build applications inside.",
"skill_id": "visio",
"subtype": "diagramming_tool",
"type": "Tool"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "analysis",
"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": [],
"input_skill": "communication",
"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": [],
"input_skill": "data",
"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": [],
"input_skill": "databases",
"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": [],
"input_skill": "documentation",
"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": [],
"input_skill": "fintech",
"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": [],
"input_skill": "healthcare",
"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": [],
"input_skill": "insights",
"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": [],
"input_skill": "methodologies",
"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": [],
"input_skill": "optimization",
"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": [],
"input_skill": "reporting",
"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": [],
"input_skill": "software",
"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": [],
"input_skill": "specifications",
"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": [],
"input_skill": "stories",
"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": [],
"input_skill": "tools",
"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": [],
"input_skill": "trends",
"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": [],
"input_skill": "workshops",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "llm",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"APIs",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"UAT",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "Most evidence points to reporting and dashboard development, and Data Analyst is the only DB candidate directly tied to that largest dimension.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"final_input_skills": [
{
"skill": "Power BI",
"tag": "in_db"
},
{
"skill": "Tableau",
"tag": "in_db"
},
{
"skill": "Argo Workflows",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "CBAP",
"tag": "new"
},
{
"skill": "CCBA",
"tag": "new"
},
{
"skill": "Excel",
"tag": "new"
},
{
"skill": "FRDs",
"tag": "new"
},
{
"skill": "Knowledge",
"tag": "new"
},
{
"skill": "QA",
"tag": "new"
},
{
"skill": "SDLC",
"tag": "new"
},
{
"skill": "SaaS",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Visio",
"tag": "new"
},
{
"skill": "analysis",
"tag": "new"
},
{
"skill": "communication",
"tag": "new"
},
{
"skill": "data",
"tag": "new"
},
{
"skill": "databases",
"tag": "new"
},
{
"skill": "documentation",
"tag": "new"
},
{
"skill": "fintech",
"tag": "new"
},
{
"skill": "healthcare",
"tag": "new"
},
{
"skill": "insights",
"tag": "new"
},
{
"skill": "methodologies",
"tag": "new"
},
{
"skill": "optimization",
"tag": "new"
},
{
"skill": "reporting",
"tag": "new"
},
{
"skill": "software",
"tag": "new"
},
{
"skill": "specifications",
"tag": "new"
},
{
"skill": "stories",
"tag": "new"
},
{
"skill": "tools",
"tag": "new"
},
{
"skill": "trends",
"tag": "new"
},
{
"skill": "workshops",
"tag": "new"
}
],
"persistence": {
"items": [
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Power BI",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1884,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Reporting and Dashboard Development",
"id": 295,
"rationale": "Building recurring reports and dashboards that track performance over time and across segments. This is a distinct cluster because the analyst must package metrics into reusable views for stakeholders.",
"slug": "reporting-and-dashboard-development",
"source": "db"
},
"dimension_id": 295,
"input_skill": "Tableau",
"llm_role": null,
"matched_chosen_role": true,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Analyst",
"id": 20,
"rationale": null,
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 1883,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "Workflow Orchestration Systems",
"id": 64,
"rationale": "Operational orchestration of ML jobs, dependencies, and handoffs across training, validation, deployment, and retraining. This is a useful split from training pipelines because it emphasizes the scheduler and control plane.",
"slug": "workflow-orchestration-systems",
"source": "db"
},
"dimension_id": 64,
"input_skill": "Argo Workflows",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [
{
"display_name": "Data Engineer",
"id": 6,
"rationale": null,
"role_archetype": null,
"slug": "data-engineer",
"source": "db"
},
{
"display_name": "MLOps Engineer",
"id": 5,
"rationale": null,
"role_archetype": null,
"slug": "mlops-engineer",
"source": "db"
}
],
"skill_dimension_saved": false,
"skill_id": 380,
"skill_tag": "in_db",
"skipped_reason": "TODO: REMOVE AFTER TESTING \u2014 api3_writes_enabled=False (writes disabled)"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "API Design and Integration",
"id": null,
"rationale": "Designing how systems expose capabilities through APIs and how those APIs are consumed across applications and services. This fits the target skill because APIs are the core interface for structured system integration and data exchange.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "APIs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Professional certification knowledge for business analysts, including requirements elicitation, stakeholder analysis, solution assessment, and business process modeling. CBAP belongs here because it is a business analysis credential rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CBAP",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and professional standards for analysts who elicit requirements, model processes, and support solution delivery. CCBA belongs here because it is an industry-recognized certification for business analysts rather than a technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "CCBA",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Modeling",
"id": null,
"rationale": "Using Excel to organize, analyze, and model business data for reporting and decision support. This fits a Business Analyst role because Excel is often the primary tool for ad hoc analysis, calculations, and lightweight scenario modeling.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Excel",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Functional Requirements Documentation",
"id": null,
"rationale": "Covers writing and maintaining functional requirements documents that define what a product or system must do. FRDs fit here because they capture business needs, scope, behaviors, and acceptance expectations in a structured specification.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "FRDs",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge and Business Context",
"id": null,
"rationale": "Understanding the business domain, processes, terminology, and constraints needed to interpret requirements and make sound analysis decisions. This fits a Business Analyst because the skill is about knowing the subject matter well enough to translate needs into clear, actionable work.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Knowledge",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Software Delivery Lifecycle",
"id": null,
"rationale": "Covers the end-to-end process of planning, building, testing, releasing, and maintaining software products. SDLC belongs here because it refers to the overall lifecycle framework rather than a single technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SDLC",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Model",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including how the product is packaged, priced, provisioned, and consumed by customers. SaaS fits here because it refers to the delivery and business model rather than a specific technical implementation.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "SaaS",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing Execution",
"id": null,
"rationale": "Covers planning and running user acceptance tests to confirm a feature meets business requirements and is ready for sign-off. UAT belongs here because it is a manual, requirement-driven validation step focused on stakeholder acceptance rather than technical test automation.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "UAT",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
},
{
"chosen_role_id": 20,
"dimension": {
"difficulty_hint": null,
"display_name": "Diagramming and Process Modeling",
"id": null,
"rationale": "Covers creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to draw process maps, org charts, swimlanes, and architecture diagrams for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "Visio",
"llm_role": null,
"matched_chosen_role": false,
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": false,
"skill_id": null,
"skill_tag": "new",
"skipped_reason": "skill_not_in_db_v3_proposed"
}
],
"new_skills_created": 0,
"role_dimension_saved": 0,
"skill_dimension_saved": 0,
"skipped": 13
},
"planner_output": null,
"run_id": "23f7a1f2-04df-4eea-a7be-6a787c95c6a3"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…