Cross Reference Gaps
Act as a strict Career Coach and Data Analyzer.
Task: Deeply review all the populated .md files inside my career_vault/ directory. Pay special attention to the cross-referencing between the courses/, certifications/, and skills/ folders versus the experiences/ and projects/ folders.
Action: Perform a bi-directional cross-reference analysis to ensure absolute data consistency across the vault.
Rules:
Identify up to 5 critical gaps based on these two directions:
Proof Gap (Skills -> Projects): Find high-value concepts or skills listed in the vault that I have NEVER explicitly mentioned using in my practical projects.
Inventory Gap (Projects -> Skills): Find specific tools, APIs, frameworks, or methods (e.g., Groq API, LLaMA) mentioned inside my project/experience descriptions that are MISSING from my main skills or certifications files.
DO NOT write, invent, or assume any new content yourself.
ASK ME specific questions to extract missing metrics or to get permission to sync these specific gaps. (Example: "You used Groq API in Project X, but it's not in your skills file. Should I add it? Also, what was the exact latency improvement?")
Stop and wait for my permission and answers.
Execution: After I provide my answers, directly update the respective .md files in the career_vault/ workspace to reflect these enrichments. Do not just output the code in the chat; apply the changes directly to the files.when to use it
Community prompt sourced from the open-source GitHub repo omaewamoushindei/CVagent-pipeline (MIT). A "Cross Reference Gaps" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
careercommunitygeneral
source
omaewamoushindei/CVagent-pipeline · MIT