Pipeline run
45da740a-a7f9-4335-9bd3-1687b8dcfda8
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-08T10:26:36.081620Z
Updated: 2026-05-08T10:28:38.338970Z
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
The strongest mapped dimension is reporting and dashboard development, which directly links to Data Analyst and is more specific than the weaker business-analysis signals.
0
New skills
0
Skill↔dim saved
0
Role↔dim saved
15
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 |
|---|---|---|---|---|---|---|
| Tableau | in_db |
Reporting and Dashboard Development
reporting-and-dashboard-development
|
— | — | — | TODO: REMOVE AFTER TESTING — api3_writes_enabled=False (writes disabled) |
| Power BI | 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 |
| BI | new |
Business Intelligence Reporting
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 |
| CCBA | new |
Requirements Elicitation and Analysis
d_init_02
|
— | — | — | skill_not_in_db_v3_proposed |
| Excel | new |
Spreadsheet Analysis and Reporting
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
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 Concepts
d_init_01
|
— | — | — | skill_not_in_db_v3_proposed |
| UAT | new |
User Acceptance Testing
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 | BI | type=Domain subtype=business_intelligence nature=CONCEPT 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=Domain subtype=functional_requirements_documents nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | Knowledge | type=Concept subtype=general_knowledge nature=CONCEPT lifespan=EVERGREEN | |
| canonical_skill_proposed | QA | type=SoftSkill subtype=quality_assurance nature=PRACTICE 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_platform nature=PLATFORM lifespan=EVERGREEN | |
| canonical_skill_proposed | Testing | type=Methodology subtype=software_testing_methodology nature=METHODOLOGY 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 Intelligence Reporting | |
| dimension_skill_link_proposed | BI ↔ Business Intelligence Reporting | |
| 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 | Requirements Elicitation and Analysis | |
| dimension_skill_link_proposed | CCBA ↔ Requirements Elicitation and Analysis | |
| dimension_proposed | Spreadsheet Analysis and Reporting | |
| dimension_skill_link_proposed | Excel ↔ Spreadsheet Analysis and Reporting | |
| dimension_proposed | Functional Requirements Documentation | |
| dimension_skill_link_proposed | FRDs ↔ Functional Requirements Documentation | |
| dimension_proposed | Domain Knowledge | |
| dimension_skill_link_proposed | Knowledge ↔ Domain Knowledge | |
| dimension_proposed | Software Delivery Lifecycle | |
| dimension_skill_link_proposed | SDLC ↔ Software Delivery Lifecycle | |
| dimension_proposed | SaaS Product Concepts | |
| dimension_skill_link_proposed | SaaS ↔ SaaS Product Concepts | |
| dimension_proposed | User Acceptance Testing | |
| dimension_skill_link_proposed | UAT ↔ User Acceptance Testing | |
| 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",
"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",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"analysis",
"candidate",
"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",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"work",
"workshops"
],
"final_skills": [
"Tableau",
"Power BI",
"Argo Workflows",
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
],
"initial_skills": [
"Tableau",
"Power BI",
"Argo Workflows"
],
"jd_role_hint": {
"display_name": "Business Analyst",
"rationale": "The excerpt centers on gathering requirements, stakeholder communication, process analysis, and documentation typical of a business analyst role.",
"role_archetype": "Analyzes business needs, documents requirements, and translates them into functional specifications and process improvements.",
"slug": "business-analyst"
},
"llm_non_skills": [
"2\u20135",
"Ability",
"Acceptance",
"Analyst",
"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",
"Title",
"Understanding",
"User",
"Years",
"abilities",
"analysis",
"candidate",
"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",
"software",
"solutions",
"specifications",
"stakeholder",
"stakeholders",
"stories",
"strategies",
"teams",
"tools",
"trends",
"work",
"workshops"
],
"llm_skills": [
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
],
"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": "The strongest mapped dimension is reporting and dashboard development, which directly links to Data Analyst and is more specific than the weaker business-analysis signals.",
"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": "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": "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": "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 and using application programming interfaces to connect systems, exchange data, and expose capabilities. APIs belong here because they define the contract between a business process and the software services that support it.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "APIs",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and consumption of reports, dashboards, and KPI views used to support business decision-making. BI belongs here because, in a business analyst context, it usually refers to reporting, analysis, and insight delivery rather than data engineering.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Business Analysis Certification",
"id": null,
"rationale": "Formal business analysis credentialing and the body of knowledge associated with professional BA practice. CBAP belongs here because it is a certification for experienced business analysts covering requirements, stakeholder analysis, and solution evaluation.",
"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, document, and validate business needs. CCBA fits here because it is a recognized business analysis certification rather than a tool, platform, or technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Requirements Elicitation and Analysis",
"id": null,
"rationale": "Practices for discovering, analyzing, and validating business and functional requirements from stakeholders. CCBA can map here because the certification centers on core business analysis competencies used to define and refine requirements.",
"slug": "d_init_02",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Spreadsheet Analysis and Reporting",
"id": null,
"rationale": "Using Excel for tabular analysis, reporting, and lightweight business modeling. This fits Excel because the skill centers on organizing data, applying formulas, summarizing results, and presenting findings for business decisions.",
"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 requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, 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",
"id": null,
"rationale": "Knowledge of the business domain, processes, rules, and terminology needed to understand requirements and make sound analysis decisions. For a Business Analyst, this is the core subject-matter context that shapes elicitation, gap analysis, and stakeholder communication.",
"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. SDLC belongs here because it refers to the overall lifecycle and governance of how software changes move from idea to production.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SDLC",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "SaaS Product Concepts",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including tenant-based delivery, packaging, pricing, and operational characteristics. SaaS fits here because it refers to the product and delivery model rather than a specific technical implementation skill.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "SaaS",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "User Acceptance Testing",
"id": null,
"rationale": "Covers planning and executing business-facing validation to confirm a solution meets agreed requirements and acceptance criteria. UAT belongs here because it is the formal check that end users or business representatives use before sign-off.",
"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": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to model processes, org structures, and solution diagrams for analysis and documentation.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "Visio",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"Tableau",
"Power BI",
"Argo Workflows",
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
],
"input_llm_skills": [
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
],
"new_aliases_persisted": 0,
"run_id": "45da740a-a7f9-4335-9bd3-1687b8dcfda8",
"skills_detail": [
{
"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": "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": "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 and using application programming interfaces to connect systems, exchange data, and expose capabilities. APIs belong here because they define the contract between a business process and the software services that support it.",
"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 standard, well-scoped 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",
"SDK",
"microservices",
"HTTP"
]
},
"maturity": {
"confidence": 0.98,
"maturity": "well_known",
"reasoning": "APIs are a hiring-pipeline staple across backend, mobile, and platform JDs; REST/GraphQL/OpenAPI appear in large volumes and underpin most modern integrations."
},
"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 and using application programming interfaces to connect systems, exchange data, and expose capabilities. APIs belong here because they define the contract between a business process and the software services that support it.",
"exemplar_skills": [
"APIs",
"REST API design",
"endpoint design",
"API versioning",
"webhooks",
"API documentation"
],
"in_scope": "APIs, REST APIs, endpoint design, request and response formats, API versioning, integration patterns, webhooks, API documentation, service-to-service calls",
"name": "API Design and Integration",
"out_of_scope": "UI design, database schema modeling, test automation for endpoints, authentication session management, infrastructure provisioning",
"overlap_flags": [
{
"reason": "API design often sits inside broader service integration work, but this response uses a new dimension because no exact catalog API dimension exists.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "API implementation and API testing are closely related, but this dimension focuses on designing and consuming APIs rather than validating them.",
"with_dim_id": "api-and-service-test-automation",
"with_dim_name": null,
"with_role": null
}
],
"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": [],
"parent_skills": [],
"related_to": [
"rest-apis",
"grpc",
"http",
"json",
"oauth-2-0"
],
"requires": [],
"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 Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and consumption of reports, dashboards, and KPI views used to support business decision-making. BI belongs here because, in a business analyst context, it usually refers to reporting, analysis, and insight delivery rather than data engineering.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "BI",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "BI",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "business_intelligence",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"business_intelligence"
],
"reasoning": "\"BI\" is a common abbreviation for Business Intelligence, but in JDs it can also be used more broadly or inconsistently; the catalog likely has the full Business Intelligence skill, so an extractor could map this mention there."
},
"context_keywords": {
"context_keywords": [
"dashboarding",
"data warehouse",
"ETL",
"OLAP",
"KPI",
"reporting",
"Tableau",
"Power BI",
"Looker",
"SSRS",
"SQL",
"dimensional modeling",
"star schema",
"data mart",
"ad hoc analysis"
]
},
"maturity": {
"confidence": 0.9,
"maturity": "well_known",
"reasoning": "BI is a common hiring keyword across analytics and data roles; job postings routinely ask for Power BI/Tableau/Looker or BI reporting experience, showing broad market demand."
},
"skill_id": "bi",
"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 the creation and consumption of reports, dashboards, and KPI views used to support business decision-making. BI belongs here because, in a business analyst context, it usually refers to reporting, analysis, and insight delivery rather than data engineering.",
"exemplar_skills": [
"BI",
"dashboard design",
"reporting",
"KPI tracking",
"ad hoc analysis",
"self-service analytics"
],
"in_scope": "BI, dashboards, operational reports, executive scorecards, KPI definitions, ad hoc analysis, self-service reporting, report distribution, drill-down analysis, business metrics",
"name": "Business Intelligence Reporting",
"out_of_scope": "data warehouse modeling, ETL pipeline development, machine learning model training, database administration, spreadsheet-only financial modeling",
"overlap_flags": [
{
"reason": "BI work often depends on shaping source data, but this dimension owns the transformation and joining logic.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Analysts may use notebooks for BI exploration, but that dimension focuses on the analysis workflow rather than reporting outputs.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "BI",
"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": "bi"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"dashboards"
],
"requires": [],
"skill_id": "bi",
"suppress_on_match": []
},
"skill_id": "bi",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.93,
"name": "BI",
"reasoning": "BI is fundamentally a business intelligence problem space and body of knowledge, so it fits the Domain type rather than a tool, framework, or methodology.",
"skill_id": "bi",
"subtype": "business_intelligence",
"type": "Domain"
},
"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 the body of knowledge associated with professional BA practice. CBAP belongs here because it is a certification for experienced business analysts covering requirements, stakeholder analysis, and solution evaluation.",
"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 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",
"traceability matrix",
"workshop facilitation",
"solution assessment",
"functional requirements",
"BRD"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "CBAP appears frequently in business analyst job descriptions and certification requirements, especially in enterprise BA roles; IIBA still actively maintains the credential and exam path."
},
"skill_id": "cbap",
"vendor_license": {
"confidence": 0.97,
"license": null,
"vendor": "International Institute of Business Analysis",
"year_introduced": 2006
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Formal business analysis credentialing and the body of knowledge associated with professional BA practice. CBAP belongs here because it is a certification for experienced business analysts covering requirements, stakeholder analysis, and solution evaluation.",
"exemplar_skills": [
"CBAP",
"BABOK",
"IIBA",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"solution assessment"
],
"in_scope": "CBAP, business analysis certification, IIBA certifications, BABOK knowledge areas, requirements elicitation, stakeholder analysis, process modeling, solution assessment",
"name": "Business Analysis Certification",
"out_of_scope": "Business process improvement methods, project management certification, software testing, data analysis tools, those belong to separate process, PM, QA, or analytics dimensions",
"overlap_flags": [
{
"reason": "Business analysts may support acceptance criteria and test review, but CBAP itself is a professional BA credential rather than a testing skill.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
}
],
"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": [
"risk-based-testing",
"acceptance-criteria-validation",
"acceptance-criteria-checks",
"capacity-planning",
"session-based-testing"
],
"requires": [],
"skill_id": "cbap",
"suppress_on_match": []
},
"skill_id": "cbap",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.98,
"name": "CBAP",
"reasoning": "CBAP is a formal third-party credential, so by the Certification rule it is not a concept or methodology.",
"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, document, and validate business needs. CCBA fits here because it is a recognized business analysis certification rather than a tool, platform, or technical practice.",
"slug": "d_init_01",
"source": "llm"
},
"input_skill": "CCBA",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": null,
"display_name": "Requirements Elicitation and Analysis",
"id": null,
"rationale": "Practices for discovering, analyzing, and validating business and functional requirements from stakeholders. CCBA can map here because the certification centers on core business analysis competencies used to define and refine requirements.",
"slug": "d_init_02",
"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; both are BA credentials from the same domain."
},
"context_keywords": {
"context_keywords": [
"IIBA",
"BABOK",
"business analysis",
"requirements elicitation",
"stakeholder analysis",
"process modeling",
"gap analysis",
"use cases",
"user stories",
"traceability matrix",
"solution assessment",
"elicitation techniques",
"workshop facilitation",
"UAT",
"BRD"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "niche",
"reasoning": "CCBA appears in some business analyst job postings, but JD volume is far below broad staples like PMP/CBAP and it is not a common baseline requirement across the market."
},
"skill_id": "ccba",
"vendor_license": {
"confidence": 0.93,
"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, document, and validate business needs. CCBA fits here because it is a recognized business analysis certification rather than a tool, platform, or technical practice.",
"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, business case analysis, solution assessment",
"name": "Business Analysis Certification",
"out_of_scope": "Software testing execution, project management certification, product management methods, data analysis tooling, platform administration, which belong to separate technical or delivery dimensions",
"overlap_flags": [
{
"reason": "Business analysts may document service interactions, but this dimension is about certification and BA practice rather than system architecture.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_01"
},
{
"description": "Practices for discovering, analyzing, and validating business and functional requirements from stakeholders. CCBA can map here because the certification centers on core business analysis competencies used to define and refine requirements.",
"exemplar_skills": [
"CCBA",
"requirements elicitation",
"requirements analysis",
"stakeholder interviews",
"workshop facilitation",
"use cases",
"acceptance criteria"
],
"in_scope": "CCBA, requirements gathering, requirements elicitation, requirements analysis, stakeholder interviews, workshop facilitation, use cases, user stories, acceptance criteria, business rules",
"name": "Requirements Elicitation and Analysis",
"out_of_scope": "Technical implementation design, test automation, data engineering, UX visual design, and project scheduling, which are owned by other dimensions",
"overlap_flags": [
{
"reason": "Requirements work often informs test cases, but this dimension focuses on analysis and definition rather than manual test execution.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
}
],
"tentative_id": "d_init_02"
}
],
"merge_log": [],
"placed": {
"name": "CCBA",
"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": "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 not 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 Reporting",
"id": null,
"rationale": "Using Excel for tabular analysis, reporting, and lightweight business modeling. This fits Excel because the skill centers on organizing data, applying formulas, summarizing results, and presenting findings for business decisions.",
"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 is a well-known spreadsheet application and, in typical JDs, is unlikely to be confused with a different 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; Microsoft continues active development and it remains a standard spreadsheet tool in hiring pipelines."
},
"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 2007": "Microsoft 365 / Excel 2024",
"Excel 2010": "Microsoft 365 / Excel 2024",
"Excel 2013": "Microsoft 365 / Excel 2024",
"Excel 2016": "Microsoft 365 / Excel 2024",
"Excel 2019": "Microsoft 365 / Excel 2024",
"Excel 2021": "Microsoft 365 / Excel 2024",
"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 for tabular analysis, reporting, and lightweight business modeling. This fits Excel because the skill centers on organizing data, applying formulas, summarizing results, and presenting findings for business decisions.",
"exemplar_skills": [
"Excel",
"Pivot Tables",
"VLOOKUP",
"XLOOKUP",
"Conditional Formatting",
"Charting",
"Spreadsheet Modeling"
],
"in_scope": "Excel, formulas, functions, pivot tables, charts, filters, conditional formatting, lookup formulas, basic dashboards, workbook organization, report generation",
"name": "Spreadsheet Analysis and Reporting",
"out_of_scope": "SQL querying and database design, statistical programming in R or Python, enterprise BI platform administration, data engineering pipelines",
"overlap_flags": [
{
"reason": "Excel is often used to combine and reshape small datasets, but that dimension owns multi-source data wrangling beyond spreadsheet-centric analysis.",
"with_dim_id": "data-preparation-and-blending",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Excel can support analysis workflows, but notebooks own scripted, reproducible analytical computation.",
"with_dim_id": "notebook-and-reproducible-analysis-workflow",
"with_dim_name": null,
"with_role": null
}
],
"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 library 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 requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, 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": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "functional_requirements_documents",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "FRDs is a fairly specific plural abbreviation for functional requirements documents; in JDs it is unlikely to be mistaken for another catalog skill."
},
"context_keywords": {
"context_keywords": [
"BRD",
"PRD",
"use cases",
"user stories",
"acceptance criteria",
"functional specification",
"requirements traceability",
"process flows",
"wireframes",
"stakeholder interviews",
"gap analysis",
"scope definition",
"business rules",
"UAT",
"sign-off"
]
},
"maturity": {
"confidence": 0.78,
"maturity": "well_known",
"reasoning": "Functional requirements documents (FRDs) are a standard artifact in many enterprise and BA/PM job descriptions; they remain a common deliverable in requirements-gathering workflows despite newer agile formats."
},
"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 requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, and acceptance expectations in a structured specification.",
"exemplar_skills": [
"FRDs",
"functional requirements documentation",
"business requirements gathering",
"writing use cases",
"defining acceptance criteria",
"requirements traceability"
],
"in_scope": "FRDs, functional requirements documents, business requirements, scope statements, use cases, user stories, acceptance criteria, process flows, requirement traceability",
"name": "Functional Requirements Documentation",
"out_of_scope": "Technical architecture, API implementation details, test automation, project scheduling, change management, which belong to delivery, engineering, or QA dimensions",
"overlap_flags": [
{
"reason": "FRDs often feed test design, but this dimension focuses on specifying requirements rather than executing tests.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Some FRDs may mention system interactions, but detailed service design belongs to architecture rather than requirements documentation.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"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",
"runbooks",
"contract-tests",
"risk-based-testing",
"rollback-readiness"
],
"requires": [],
"skill_id": "frds",
"suppress_on_match": []
},
"skill_id": "frds",
"split_log": [],
"typed": {
"alternatives_considered": [
"Concept: ruled out \u2014 it is not a single named theory or principle but a documentation artifact/body of practice.",
"Methodology: ruled out \u2014 it does not describe a way of working or process.",
"Format: ruled out \u2014 although documents have structure, FRDs are not primarily a wire/data format."
],
"confidence": 0.72,
"name": "FRDs",
"reasoning": "FRDs are a body of knowledge/documentation used in product and systems work, so by the Concept vs Methodology rule they fit best as a Domain rather than a tool or format.",
"skill_id": "frds",
"subtype": "functional_requirements_documents",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": null,
"display_name": "Domain Knowledge",
"id": null,
"rationale": "Knowledge of the business domain, processes, rules, and terminology needed to understand requirements and make sound analysis decisions. For a Business Analyst, this is the core subject-matter context that shapes elicitation, gap analysis, and stakeholder communication.",
"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 refer to knowledge management, knowledge graphs, or a knowledge base rather than the generic concept."
},
"context_keywords": {
"context_keywords": [
"domain expertise",
"subject matter expert",
"best practices",
"business acumen",
"industry trends",
"regulatory requirements",
"operational knowledge",
"process improvement",
"stakeholder needs",
"cross-functional",
"requirements gathering",
"decision-making",
"knowledge base",
"lessons learned",
"training materials"
]
},
"maturity": {
"confidence": 0.92,
"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": "Knowledge of the business domain, processes, rules, and terminology needed to understand requirements and make sound analysis decisions. For a Business Analyst, this is the core subject-matter context that shapes elicitation, gap analysis, and stakeholder communication.",
"exemplar_skills": [
"Knowledge",
"Business domain knowledge",
"Process knowledge",
"Subject-matter expertise",
"Regulatory knowledge"
],
"in_scope": "Knowledge, business domain understanding, process knowledge, terminology, policies, operating model, regulatory context, stakeholder context, subject-matter familiarity",
"name": "Domain Knowledge",
"out_of_scope": "Technical implementation details, coding, database design, UI design, project scheduling, test execution, which belong to engineering, product, or QA dimensions",
"overlap_flags": [
{
"reason": "Business domain knowledge can overlap with system integration understanding when analysts map business processes to services.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "Domain knowledge may inform migration decisions, but the dimension here is about business context rather than technical transition planning.",
"with_dim_id": "migration-and-modernization-planning",
"with_dim_name": null,
"with_role": null
}
],
"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": [
"Methodology: ruled out \u2014 it describes what one knows, not a process or way of working."
],
"confidence": 0.98,
"name": "Knowledge",
"reasoning": "Knowledge is a named knowledge unit rather than a way of working, so by the Concept vs Methodology rule it is a 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": "SoftSkill",
"skill_nature": "PRACTICE",
"sub_category": "quality_assurance",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"quality_assurance"
],
"reasoning": "\"QA\" is a common abbreviation for quality assurance, but in JDs it can also mean quality analyst or testing-related roles; the catalog likely has the full quality assurance skill, so an extractor could map it there."
},
"context_keywords": {
"context_keywords": [
"test cases",
"test plans",
"regression testing",
"defect tracking",
"bug triage",
"UAT",
"test automation",
"Selenium",
"JIRA",
"traceability matrix",
"acceptance criteria",
"smoke testing",
"sanity testing",
"test scripts"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "QA is a standard hiring requirement across software JDs, with frequent mentions of test planning, defect tracking, and release validation; it remains broadly adopted rather than niche or sunsetted."
},
"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": "Test Case Design and 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 define the same manual QA cluster: designing, reviewing, and executing human-run test cases to validate requirements, acceptance criteria, features, fixes, and regressions. Dim A explicitly includes manual test cases, acceptance testing, regression testing, exploratory testing, defect logging, and UAT support; Dim B says the same core discipline of turning requirements and acceptance criteria into repeatable human-run checks. The exemplar skills in A (manual testing, test case design, regression testing, acceptance testing, defect tracking) all fit B, and B adds no distinct scope.",
"similarity": 0.8613355928435912
}
],
"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",
"defect-retest",
"risk-based-testing",
"cross-browser-testing",
"session-based-testing",
"charter-based-testing"
],
"requires": [],
"skill_id": "qa",
"suppress_on_match": []
},
"skill_id": "qa",
"split_log": [],
"typed": {
"alternatives_considered": [
"Methodology: ruled out \u2014 QA is broader than a specific process like TDD or Scrum and is commonly used as a general capability label.",
"Concept: ruled out \u2014 QA is not primarily a single knowledge unit or principle."
],
"confidence": 0.78,
"name": "QA",
"reasoning": "QA is best treated as a quality-assurance capability rather than a software artifact, and under the Concept vs Methodology rule it fits a way of working more than a technical system.",
"skill_id": "qa",
"subtype": "quality_assurance",
"type": "SoftSkill"
},
"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. SDLC belongs here because it refers to the overall lifecycle and governance of how software changes move from idea to production.",
"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",
"CI/CD",
"Agile",
"Scrum",
"waterfall",
"change management",
"defect tracking"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "SDLC is a standard term in software job descriptions and engineering process docs across companies; it appears broadly in hiring pipelines for developers, QA, and PM roles rather than 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. SDLC belongs here because it refers to the overall lifecycle and governance of how software changes move from idea to production.",
"exemplar_skills": [
"SDLC",
"software development lifecycle",
"release lifecycle management",
"change control",
"requirements-to-release process"
],
"in_scope": "SDLC, software development lifecycle, requirements to release flow, change control, release gates, development phases, maintenance lifecycle, handoff between analysis, build, test, and deployment",
"name": "Software Delivery Lifecycle",
"out_of_scope": "Manual test case writing, which belongs to test-case-design-and-execution, environment setup and access, which belongs to environment-and-access-coordination, deployment mechanics, which belong to environment-provisioning-and-promotion or orchestration-platforms",
"overlap_flags": [
{
"reason": "SDLC often includes testing activities, but the detailed design and execution of test cases is a separate dimension.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SDLC includes release progression, but environment creation and promotion are operational sub-skills with their own cluster.",
"with_dim_id": "environment-provisioning-and-promotion",
"with_dim_name": null,
"with_role": null
}
],
"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": [
"clean-architecture",
"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": [
"Concept: ruled out \u2014 although it is a named term, the disambiguation Concept vs Methodology favors the operational process meaning here.",
"Architecture: ruled out \u2014 it is not a system-shape pattern like microservices or hexagonal architecture."
],
"confidence": 0.88,
"name": "SDLC",
"reasoning": "SDLC is best treated as a Methodology because it describes the process and phases for how software is developed and delivered, not a system shape or a knowledge unit.",
"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 Concepts",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including tenant-based delivery, packaging, pricing, and operational characteristics. SaaS fits here because it refers to the product and delivery model rather than a specific technical implementation skill.",
"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_platform",
"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 platforms; in JDs it is usually not confused with a different catalog skill."
},
"context_keywords": {
"context_keywords": [
"multi-tenant",
"subscription billing",
"tenant isolation",
"self-service onboarding",
"usage-based pricing",
"provisioning",
"SAML",
"SSO",
"RBAC",
"API integrations",
"webhooks",
"SLAs",
"churn",
"customer success",
"feature flags"
]
},
"maturity": {
"confidence": 0.96,
"maturity": "well_known",
"reasoning": "SaaS is a standard deployment model in job postings across product, sales, and engineering roles; major vendors like Salesforce, Microsoft, and Google market SaaS offerings broadly, indicating mainstream adoption."
},
"skill_id": "saas",
"vendor_license": {
"confidence": 0.78,
"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 tenant-based delivery, packaging, pricing, and operational characteristics. SaaS fits here because it refers to the product and delivery model rather than a specific technical implementation skill.",
"exemplar_skills": [
"SaaS",
"software as a service",
"multi-tenant architecture",
"subscription licensing",
"hosted application delivery"
],
"in_scope": "SaaS, software as a service, multi-tenant product delivery, subscription licensing, hosted application delivery, usage tiers, customer onboarding, tenant isolation concepts",
"name": "SaaS Product Concepts",
"out_of_scope": "cloud infrastructure provisioning, container orchestration, API integration, frontend UI design, security hardening, data pipeline operations",
"overlap_flags": [
{
"reason": "SaaS products are often built from services, but this dimension is about the delivery model rather than service decomposition or integration.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
},
{
"reason": "SaaS offerings commonly rely on cloud controls, but security guardrails are a separate operational concern.",
"with_dim_id": "cloud-security-guardrails",
"with_dim_name": null,
"with_role": null
}
],
"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",
"azure-backup",
"cspm",
"policy-as-code",
"cloud-reference-architecture"
],
"requires": [],
"skill_id": "saas",
"suppress_on_match": []
},
"skill_id": "saas",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.9,
"name": "SaaS",
"reasoning": "By the Platform vs Tool rule, SaaS is a hosted multi-tenant environment delivered over APIs and managed services rather than software you run yourself.",
"skill_id": "saas",
"subtype": "software_as_a_service_platform",
"type": "Platform"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [],
"input_skill": "Testing",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Methodology",
"skill_nature": "METHODOLOGY",
"sub_category": "software_testing_methodology",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": true,
"confused_with": [
"unit_testing",
"integration_testing",
"automated_testing",
"qa"
],
"reasoning": "\"Testing\" is very broad in JDs and can refer to specific software testing practices or QA work rather than the general methodology, so extractors could reasonably map it to related testing skills in the catalog."
},
"context_keywords": {
"context_keywords": [
"unit testing",
"integration testing",
"test automation",
"test cases",
"test suite",
"regression testing",
"smoke testing",
"mocking",
"stubs",
"fixtures",
"assertions",
"coverage",
"TDD",
"BDD",
"CI/CD"
]
},
"maturity": {
"confidence": 0.97,
"maturity": "well_known",
"reasoning": "Software testing is a standard requirement in most engineering JDs and appears across QA, SDET, and developer roles; major frameworks and CI pipelines make it a baseline hiring signal rather than a niche specialty."
},
"skill_id": "testing",
"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 cluster: designing, reviewing, and executing human-run tests against requirements, acceptance criteria, features, fixes, and regressions. Dim A\u2019s exemplars (Test Case Design, Test Execution, Regression Testing, Acceptance Testing, User Acceptance Testing) match Dim B\u2019s core description almost exactly. The extra note in A about business-analyst context does not create a separate skill cluster; it is the same discipline framed for a different role.",
"similarity": 0.8229676947886392
},
{
"a_dim_id": "d_init_02",
"a_name": "API and Service Test Automation",
"a_role": "__skill_focal__",
"b_dim_id": "api-and-service-test-automation",
"b_name": "API and Service Test Automation",
"b_role": "Automation Tester",
"into": "d_merge_02",
"into_name": "API and Service Test Automation",
"merged_from": [
"d_init_02",
"api-and-service-test-automation"
],
"pair_kind": "cross_role",
"reasoning": "Both dimensions describe the same testing cluster: automated validation of backend services rather than manual QA or UI testing. Dim A explicitly scopes to \"automated checks against APIs or services\" and lists exemplar skills like API Testing, Service Test Automation, Contract Testing, Integration Testing, Postman, REST Assured, and SoapUI. Dim B uses the same core wording\u2014\"Automated validation of HTTP APIs, service contracts, and backend endpoints\"\u2014and adds the same idea of regression suites verifying behavior below the UI through direct service calls. There is no meaningful distinction in skill content, role, or granularity; the similarity is not just lexical overlap but identical substance.",
"similarity": 0.8240389972456085
},
{
"a_dim_id": "d_init_03",
"a_name": "Testing and Automation Frameworks",
"a_role": "__skill_focal__",
"b_dim_id": "testing-and-automation-frameworks",
"b_name": "Testing and Automation Frameworks",
"b_role": "iOS Engineer",
"into": "d_merge_03",
"into_name": "Automated Testing and Verification Frameworks",
"merged_from": [
"d_init_03",
"testing-and-automation-frameworks"
],
"pair_kind": "cross_role",
"reasoning": "Both dimensions describe the same core cluster: automated software verification using test frameworks across unit, integration, and UI layers. Dim A explicitly includes test automation, unit testing, integration testing, UI automation, and concrete frameworks like XCTest, XCUITest, Appium, Espresso, JUnit, and pytest. Dim B says the same thing but scoped to iOS behavior, emphasizing automated checks for feature correctness and regressions; its implied examples are the same iOS testing tools already named in Dim A (especially XCTest and XCUITest). The cross-role difference is not a substantive skill difference here because the iOS-specific wording in B is just a narrower application of the same framework/automation skill cluster, not a distinct conceptual anchor.",
"similarity": 0.811876678774652
}
],
"placed": {
"name": "Testing",
"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": "testing"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"restore-testing",
"session-based-testing",
"risk-based-testing",
"cross-browser-testing",
"defect-retest",
"test-case-authoring",
"contract-tests",
"charter-based-testing",
"acceptance-criteria-checks",
"smoke-tests",
"smoke-testing",
"fuzzing",
"acceptance-criteria-validation"
],
"requires": [],
"skill_id": "testing",
"suppress_on_match": []
},
"skill_id": "testing",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.91,
"name": "Testing",
"reasoning": "By the Concept vs Methodology rule, Testing is fundamentally a way of working for validating software rather than a single knowledge unit or tool.",
"skill_id": "testing",
"subtype": "software_testing_methodology",
"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": "User Acceptance Testing",
"id": null,
"rationale": "Covers planning and executing business-facing validation to confirm a solution meets agreed requirements and acceptance criteria. UAT belongs here because it is the formal check that end users or business representatives use before sign-off.",
"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",
"acceptance criteria",
"test scripts",
"business users",
"end users",
"sign-off",
"defect triage",
"test plan",
"test scenarios",
"regression testing",
"stakeholder review",
"go-live",
"test execution",
"requirements validation"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "UAT is a standard QA/SDLC practice and appears routinely in job descriptions for QA, BA, and release roles; it is not a sunset technology and remains a common acceptance gate before production."
},
"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 executing business-facing validation to confirm a solution meets agreed requirements and acceptance criteria. UAT belongs here because it is the formal check that end users or business representatives use before sign-off.",
"exemplar_skills": [
"UAT",
"user acceptance testing",
"acceptance criteria validation",
"business scenario testing",
"end-user sign-off",
"defect logging"
],
"in_scope": "UAT, user acceptance testing, acceptance criteria validation, business scenario execution, end-user sign-off testing, test script walkthroughs, defect logging during UAT, stakeholder review of results",
"name": "User Acceptance Testing",
"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 uses test cases and execution discipline, but this dimension is specifically about business acceptance rather than general manual testing.",
"with_dim_id": "test-case-design-and-execution",
"with_dim_name": null,
"with_role": null
},
{
"reason": "UAT often depends on test environment readiness and user access, but that dimension owns the coordination work rather than the validation itself.",
"with_dim_id": "environment-and-access-coordination",
"with_dim_name": null,
"with_role": null
}
],
"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 in which users validate the system before release, so by the Concept vs Methodology rule it is a Methodology.",
"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": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to model processes, org structures, and solution 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": [
"process flow",
"swimlane",
"BPMN",
"UML",
"network diagram",
"org chart",
"floor plan",
"workflow",
"data flow",
"architecture diagram",
"stencil",
"connector",
"shape library",
"SIPOC",
"cross-functional flowchart"
]
},
"maturity": {
"confidence": 0.84,
"maturity": "well_known",
"reasoning": "Common in enterprise JDs for process/network diagrams and Microsoft 365 environments; no vendor sunset, and it remains a standard diagramming tool alongside newer alternatives."
},
"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": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to model processes, org structures, and solution diagrams for analysis and documentation.",
"exemplar_skills": [
"Visio",
"process flow diagramming",
"swimlane diagram creation",
"BPMN modeling",
"org chart design",
"network diagramming"
],
"in_scope": "Visio, process flow diagrams, swimlane diagrams, BPMN sketches, org charts, network diagrams, system context diagrams, UML-style sketches, wireframes, business process mapping",
"name": "Diagramming and Process Modeling",
"out_of_scope": "Hands-on process improvement methods, requirements elicitation, or data analysis; those belong to business analysis or modeling dimensions rather than the drawing tool itself.",
"overlap_flags": [
{
"reason": "Some Visio usage overlaps with service and system architecture diagrams, but the architecture concepts themselves belong to that dimension.",
"with_dim_id": "service-architecture-and-integration",
"with_dim_name": null,
"with_role": null
}
],
"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": [
"navgraph",
"dashboards",
"mvvm",
"threat-modeling",
"session-charters",
"scorecards",
"portal-pages",
"portal-navigation",
"funnel-metric"
],
"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
}
],
"unmatched_skills": [
"APIs",
"BI",
"CBAP",
"CCBA",
"Excel",
"FRDs",
"Knowledge",
"QA",
"SDLC",
"SaaS",
"Testing",
"UAT",
"Visio"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Data Analyst",
"id": 20,
"rationale": "The strongest mapped dimension is reporting and dashboard development, which directly links to Data Analyst and is more specific than the weaker business-analysis signals.",
"role_archetype": null,
"slug": "data-analyst",
"source": "db"
},
"final_input_skills": [
{
"skill": "Tableau",
"tag": "in_db"
},
{
"skill": "Power BI",
"tag": "in_db"
},
{
"skill": "Argo Workflows",
"tag": "in_db"
},
{
"skill": "APIs",
"tag": "new"
},
{
"skill": "BI",
"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": "Testing",
"tag": "new"
},
{
"skill": "UAT",
"tag": "new"
},
{
"skill": "Visio",
"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": "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": "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": "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 and using application programming interfaces to connect systems, exchange data, and expose capabilities. APIs belong here because they define the contract between a business process and the software services that support it.",
"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 Intelligence Reporting",
"id": null,
"rationale": "Covers the creation and consumption of reports, dashboards, and KPI views used to support business decision-making. BI belongs here because, in a business analyst context, it usually refers to reporting, analysis, and insight delivery rather than data engineering.",
"slug": "d_init_01",
"source": "llm"
},
"dimension_id": null,
"input_skill": "BI",
"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 the body of knowledge associated with professional BA practice. CBAP belongs here because it is a certification for experienced business analysts covering requirements, stakeholder analysis, and solution evaluation.",
"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, document, and validate business needs. CCBA fits here because it is a recognized business analysis certification rather than a tool, platform, or technical practice.",
"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": "Requirements Elicitation and Analysis",
"id": null,
"rationale": "Practices for discovering, analyzing, and validating business and functional requirements from stakeholders. CCBA can map here because the certification centers on core business analysis competencies used to define and refine requirements.",
"slug": "d_init_02",
"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 Reporting",
"id": null,
"rationale": "Using Excel for tabular analysis, reporting, and lightweight business modeling. This fits Excel because the skill centers on organizing data, applying formulas, summarizing results, and presenting findings for business decisions.",
"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 requirement documents that define what a product or process must do. FRDs belong here because they capture business needs, scope, rules, 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",
"id": null,
"rationale": "Knowledge of the business domain, processes, rules, and terminology needed to understand requirements and make sound analysis decisions. For a Business Analyst, this is the core subject-matter context that shapes elicitation, gap analysis, and stakeholder communication.",
"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. SDLC belongs here because it refers to the overall lifecycle and governance of how software changes move from idea to production.",
"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 Concepts",
"id": null,
"rationale": "Covers software delivered as a subscription-based hosted service, including tenant-based delivery, packaging, pricing, and operational characteristics. SaaS fits here because it refers to the product and delivery model rather than a specific technical implementation skill.",
"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",
"id": null,
"rationale": "Covers planning and executing business-facing validation to confirm a solution meets agreed requirements and acceptance criteria. UAT belongs here because it is the formal check that end users or business representatives use before sign-off.",
"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": "Creating business and technical diagrams to communicate workflows, systems, and relationships. Visio belongs here because it is commonly used to model processes, org structures, and solution 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": 15
},
"planner_output": null,
"run_id": "45da740a-a7f9-4335-9bd3-1687b8dcfda8"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…