Converts a learner’s career background into a structured CareerGraph plan as graph-safe JSON for Neo4j. Use when the user shares their skills, experience, or background and asks what to learn next, how to break into a new role, what skills they are missing, or how to plan a career transition. Also use when asked to map skills to a target career, identify learning paths, suggest projects to build, or recommend resources. Do NOT use for generic career advice, resume writing, or job searching — only when the goal is to produce a structured skill graph plan.
95
93%
Does it follow best practices?
Impact
97%
1.83xAverage score across 3 eval scenarios
Passed
No known issues
JSON output format and evidence phrasing for career switcher
JSON only output
100%
100%
Observable action phrasing
0%
83%
Concrete work over self-report
50%
100%
MissingSkills not already proven
30%
100%
MissingSkills career-relevant
75%
100%
helpPersona targets current blocker
0%
100%
helpPersonas cover current blockers
0%
100%
nextBestSkill in missingSkills
0%
100%
nextBestSkill is a foundational skill
0%
100%
Required top-level fields present
0%
100%
Sparse profile conservative plan without fabrication
No fabricated credentials
100%
100%
Small plan for sparse profile
50%
100%
knownEvidence reflects only stated info
100%
100%
Projects prove multiple missing skills
100%
100%
Resources target next skill or prerequisite
40%
53%
nextBestSkill is a foundational prerequisite
50%
100%
nextBestSkill in missingSkills
0%
100%
JSON only output
100%
100%
Graph relationship rules and prerequisite chains
Concrete work vs self-report
57%
100%
graph_audit.md present
100%
100%
Graph relationship types in audit
80%
100%
Prerequisites form a chain
100%
100%
Prerequisites link blockers to goal
100%
100%
Projects prove multiple missing skills
50%
100%
Resources target next skill or prerequisite
50%
100%
nextBestSkill is a prerequisite blocker
0%
100%
nextBestSkill in missingSkills
0%
100%
JSON only in plan file
100%
100%
bdcf2c1
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.