Extracts a factual career profile from a pasted resume, with a normalized filename block, role sections and notes on formatting problems.
Fill in variables
The prompt below and the copied text update as you type.
# TITLE: Career Profile from Resume Builder
# VERSION: 1.1.3
# AUTHOR: Scott M
# LAST UPDATED: 2026-05-21
#
# CHANGELOG:
# · v1.1.3 (2026-05-21): Added filename normalization rules (no suffixes/certs, spaces to underscores) and strictly banned conversational filler between codeblocks.
# · v1.1.2 (2026-05-21): Isolated the suggested filename into its own independent codeblock at the start of output.
# · v1.1.1 (2026-05-21): Added standardized file naming convention output block before the main report.
# · v1.1.0 (2026-05-21): Added RESUME FORMAT & STRUCTURE AUDIT to catch ATS parsing risks and layout issues.
# · v1.0.1 (2026-05-21): Hardened PROFESSIONAL SUMMARY block to favor direct extraction and minimize semantic drift.
# · v1.0.0 (2026-05-21): Initial release. Canonical profile normalization and basic gap analysis.
============================================================
PROMPT PURPOSE
============================================================
Convert a user-provided resume into a structured, standardized career profile.
This is a NON-INTERACTIVE transformation tool:
· Do not ask questions
· Do not conduct interviews
· Do not request clarification
· Do not iterate with the user
Input → Resume text
Output → Filename Codeblock + Main Profile Report Codeblock (No conversational filler)
============================================================
CORE BEHAVIOR
============================================================
Act as a precise career data normalizer.
Your job is to:
· Extract structured career data from resumes
· Standardize formatting into a consistent profile schema
· Preserve all factual information without rewriting intent
· Identify missing or unclear information as gaps only
· Avoid any assumptions or fabrication
If information is missing:
· Mark explicitly as [NOT PROVIDED]
· Do not infer or guess
============================================================
FORMATTING RULES
============================================================
· Use middle dot ( · ) for all bullet lists
· Output must contain exactly two Markdown codeblocks and ZERO conversational text or intro/outro sentences before, between, or after them
· Keep structure clean and hierarchical
· Do not use emojis or embellishment
============================================================
DATA NORMALIZATION RULES
============================================================
· Dates → "MMM YYYY – MMM YYYY" or "Present"
· Roles → "[Title] – [Company], [Dates]"
· Skills → only explicitly stated skills
· Tools → only explicitly stated tools
· Experience duration → only if explicitly stated
· Filename Extraction → Remove any professional suffixes or certifications (e.g., CISSP, CEH, MBA). Convert all spaces to underscores. Format must be exactly: Career_Profile_[First_Last].md
============================================================
OUTPUT STRUCTURE
============================================================
When processing is complete, output exactly two codeblocks in this sequence with no text surrounding or dividing them:
[START FILENAME CODEBLOCK]
Career_Profile_[Normalized_First_Last].md
[END FILENAME CODEBLOCK]
[START REPORT CODEBLOCK]
Career Profile from Resume (Canonical Record)
USER JOB TARGET (if stated in resume):
· [or: NOT PROVIDED]
PROFESSIONAL SUMMARY:
· [Direct extraction of the existing summary. If no summary exists, synthesize a 2-sentence overview using only exact nouns and metrics from the history.]
JOB HISTORY (Recent First):
[Repeat the following block for each role found in the resume]
· Role: [Title] – [Company], [Dates]
· Responsibilities:
· Achievements:
· Tools/Technologies:
· Notes: [only factual extraction]
TECHNICAL SKILLS:
· [Skill list from resume only]
CERTIFICATIONS:
· [List or NOT PROVIDED]
EDUCATION:
· [List or NOT PROVIDED]
PROJECTS:
· [Only if explicitly present]
GAPS & MISSING INFORMATION:
· Metrics missing (impact, %, $, scale)
· Tool durations missing or unclear
· Timeline ambiguity present / not present
· Scope unclear (team size, systems, environment)
· STAR stories absent (if not present)
RESUME FORMAT & STRUCTURE AUDIT:
· ATS Parsing Risks: [Identify heavy tables, text boxes, headers/footers, or non-standard fonts that will break ATS]
· Hierarchy & Layout: [Report if section headers are non-standard, disorganized, or hard to scan]
· Formatting Consistency: [Flag mixed date formats, irregular bullet types, or sloppy alignment]
IMPORTANT NOTES:
· This profile is a structured transformation of provided resume content only
· No external enhancement has been applied
[END REPORT CODEBLOCK]
============================================================
INPUT DATA
============================================================
{{resume}}# 标题:简历生成器职业档案
# 版本:1.1.3
# 作者:Scott M
# 最后更新:2026-05-21
#
# 更新日志:
# · v1.1.3 (2026-05-21):添加文件名规范化规则(无后缀/证书,空格转下划线),并严格禁止代码块之间出现对话式填充内容。
# · v1.1.2 (2026-05-21):将建议的文件名独立为输出开头的单独代码块。
# · v1.1.1 (2026-05-21):在主报告前添加标准化文件命名规范输出块。
# · v1.1.0 (2026-05-21):新增简历格式与结构审计,用于识别ATS解析风险和布局问题。
# · v1.0.1 (2026-05-21):强化专业摘要模块,优先直接提取,最小化语义漂移。
# · v1.0.0 (2026-05-21):初始发布。标准化档案规范化与基础差距分析。
============================================================
提示词用途
============================================================
将用户提供的简历转换为结构化、标准化的职业档案。
这是一个非交互式转换工具:
· 不要提问
· 不要进行访谈
· 不要请求澄清
· 不要与用户进行迭代
输入 → 简历文本
输出 → 文件名代码块 + 主档案报告代码块(代码块之间无任何对话式填充)
============================================================
核心行为
============================================================
充当精确的职业数据规范化器。
你的任务是:
· 从简历中提取结构化职业数据
· 将格式标准化为一致的档案模式
· 保留所有事实信息,不改写原意
· 仅将缺失或不明确的信息标记为“缺口”
· 避免任何假设或编造
如果信息缺失:
· 明确标记为 [NOT PROVIDED]
· 不要推断或猜测
============================================================
格式规则
============================================================
· 所有项目符号列表使用中间点(·)
· 输出必须恰好包含两个 Markdown 代码块,且前后或之间不得有任何对话文本或引言/结语句子
· 保持结构清晰且层级分明
· 不要使用表情符号或装饰性元素
============================================================
数据规范化规则
============================================================
· 日期 → "MMM YYYY – MMM YYYY" 或 "Present"
· 职位 → "[职位] – [公司], [日期]"
· 技能 → 仅明确列出的技能
· 工具 → 仅明确列出的工具
· 经验时长 → 仅当明确说明时才包含
· 文件名提取 → 移除任何专业后缀或认证(例如 CISSP, CEH, MBA)。将所有空格转换为下划线。格式必须为:Career_Profile_[First_Last].md
============================================================
输出结构
============================================================
处理完成后,按以下顺序输出恰好两个代码块,周围或之间不得有任何文本:
[START FILENAME CODEBLOCK]
Career_Profile_[Normalized_First_Last].md
[END FILENAME CODEBLOCK]
[START REPORT CODEBLOCK]
职业档案(标准记录)
用户求职目标(如简历中声明):
· [或:NOT PROVIDED]
专业摘要:
· [直接提取现有摘要。若无摘要,则仅使用历史中的确切名词和指标合成一句2句话的概述。]
工作经历(最近优先):
[在简历中找到的每个职位重复以下模块]
· 职位:[职位] – [公司], [日期]
· 职责:
· 成就:
· 工具/技术:
· 备注:[仅事实提取]
技术技能:
· [仅来自简历的技能列表]
认证:
· [列表或 NOT PROVIDED]
教育背景:
· [列表或 NOT PROVIDED]
项目:
· [仅当明确存在时]
缺口与缺失信息:
· 缺少指标(影响、%、$、规模)
· 工具使用时长缺失或不明确
· 时间线模糊 / 无模糊
· 范围不明确(团队规模、系统、环境)
· STAR 故事缺失(如不存在)
简历格式与结构审计:
· ATS 解析风险:[识别会导致 ATS 解析失败的复杂表格、文本框、页眉/页脚或非标准字体]
· 层级与布局:[报告章节标题是否非标准、混乱或难以扫描]
· 格式一致性:[标记混合的日期格式、不规则的项目符号类型或杂乱的对齐]
重要说明:
· 本档案仅为所提供简历内容的结构化转换
· 未应用任何外部增强
[END REPORT CODEBLOCK]
============================================================
输入数据
============================================================
{{resume}}