career-coaching
Review resumes, LinkedIn profiles, and job applications.
- License 许可
- Unlicense
- 最近更新
- 2026-11-03
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- career-coaching
- tags
- [ "career", "resume", "linkedin", "interview", "star", "job-search" ]
- description
- Review resumes, LinkedIn profiles, and job applications.
02 资源文件 6
- 参考文档references/assessment-interpretation.md3.5 KB
- 参考文档references/interview-prep-fill-review.md4.0 KB
- 参考文档references/interview-prep-vault.md4.0 KB
- 参考文档references/linkedin-audit-checklist.md6.9 KB
- 参考文档references/resume-review-checklist.md5.2 KB
- 参考文档references/thai-market.md6.7 KB
03 SKILL.md 正文
Career Coaching Workflow
Comprehensive workflow for job seekers: resume review → LinkedIn audit → master profile → STAR stories → tailored applications.
When to Use
- User asks for resume/CV review or rewrite
- User asks for LinkedIn profile audit or optimization
- User wants to build a "master profile" for job applications
- User needs STAR stories extracted for behavioral interviews
- User is preparing cover letters or job applications
The Master Profile Pattern
Build ONE master profile (Obsidian note) that serves as the single source of truth for all job artifacts. Structure:
8-Block Master Profile Framework
- Core Identity — Name, contact, location, languages, LinkedIn URL
- Professional Narrative — 50-word story: who you are, where you've been, where you're going
- Experience Database — Each job with: company, dates, role, metrics, tech stack, achievements
- Education & Credentials — Degree, GPA, honors, certifications, test scores, TA experience
- Skills Inventory — Categorized by proficiency (Expert/Proficient/Familiar)
- Projects Portfolio — Curated list with descriptions, tech, impact, links
- STAR Stories — 8-12 reusable stories covering leadership, conflict, failure, ambiguity, influence, judgment
- Job Search Parameters — Target roles, industries, salary range, location preferences, deal-breakers
Artifact Generation Order
- Master profile (source of truth)
- Resume (ATS-optimized, quantified)
- LinkedIn (keyword-rich, discoverable)
- Cover letter template (tailored per application)
- STAR story portfolio (extracted via
/grill-me)
Resume Review Checklist
See references/resume-review-checklist.md for the full scoring rubric.
Critical checks:
- ATS compatibility (single-column, standard headings, no tables/graphics in headers)
- Quantification (every bullet has metrics: %, time, users, revenue)
- Action verbs (Led, Built, Migrated, Reduced — not "Responsible for")
- Professional summary (50 words, keyword-rich, achievement-focused)
- Skills section (categorized, specific technologies, not vague categories)
- Contact info (includes LinkedIn URL, language proficiency for Thai market)
LinkedIn Audit Checklist
See references/linkedin-audit-checklist.md for the full audit framework.
Critical checks:
- Headline (keyword-rich, 220 chars max, includes role + top 4 tech + architecture keywords)
- About section (first 3 lines are critical — show before "see more" click)
- Experience detail (same quantification as resume, but expanded)
- Language levels (Thai = Native/bilingual, English = Professional working for B2+)
- Open to Work (enabled — ASK the user which visibility they use: public green frame vs Recruiters-only. The headline must match: with a public frame, drop redundant "Open to New Opportunities" phrasing and spend those characters on keywords; with Recruiters-only, keep availability text in the headline but never the green frame)
- Projects (curate to 2-4 strong projects, remove trivial learning exercises)
- Certifications (relevant to target roles)
STAR Story Extraction
Use /grill-me skill to extract stories. Run 3 sessions minimum:
Session 1: Technical Leadership
- Biggest technical project or migration
- Focus: problem-solving, technical judgment, impact
Session 2: People/Influence
- Mentoring, teaching, or leading without authority
- Focus: communication, influence, team dynamics
Session 3: Initiative/Ownership
- Stepping up in ambiguity, taking ownership
- Focus: decision-making, accountability, learning from failure
Each session produces one polished STAR story. Add to Block 7 of master profile.
Personality & Values Assessment Coaching
When the user takes, brings, or asks about personality/values tests — their own or employer-mandated:
- Recommendation tier list: IPIP Big Five (OCEAN) = the only tier worth trusting for self-insight; Moral Foundations = values layer, recommend as the follow-up after OCEAN; MBTI / DISC / political-compass family = entertainment tier — vocabulary, never verdicts.
- Hard privacy rule: assessment results never enter resume, LinkedIn, cover letters, or interview answers. Values data stays private entirely (Thai market conservatism makes signaling costly).
- Interpret from behavioral evidence, not percentiles: cross-check each trait against the master profile; when behavior contradicts a score, state which reading to trust and why. Full protocol + vault layout:
references/assessment-interpretation.md. - High-stability narrators need injected stakes: very high emotional stability produces failure/pressure STAR stories with zero emotional texture, which interviewers read as evasive; coach one honest stakes sentence (what was at risk, what was felt) before the Action section.
- Every spike trait gets a shadow row: shadow + countermeasure in the analysis AND in the improvement tracker (e.g., stability spike → silent overload → weekly external load gauge).
- Verify test-site URLs live before recommending (
curl -s -o /dev/null -w "%{http_code}" <url>): assessment hosts and mirror paths rot without notice; never hand the user an unverified link. - Company-mandated tests: coach answer-honestly-but-consistently (these instruments carry lie scales; faking badly scores worse than ordinary), treat the hiring process as the culture signal rather than the test result, and give the flip question to ask in interviews: "how does the team actually use these results?"
Improvement TODO Tracker
Maintain one living tracker at the career-folder root (00-Improvement-TODO.md) — career-level facts about the user, per the vault rule in career-artifact-prep:
- Horizon bands: 🔴 Now (dated window) / 🟡 current-role window (probation, first months) / 🟢 long-horizon / ✅ Done.
- Done = artifact or evidence link, never intention. Every open item wikilinks to the real vault artifact it will modify (STAR file, study base, relocation plan, assessment summary); no dangling TODOs.
- Standing hygiene item: diff the master profile against reality each review (story counts, stale "to be developed" markers, last-updated dates) — the profile drifts after every prep session.
- Cadence: weekly review (doubles as the load gauge) + monthly deep review; scheduled retests go in 🟢 with a target month.
Thai Market Specifics
See references/thai-market.md for salary ranges, job platforms, and conventions.
Quick reference:
- Mid-level SWE Bangkok: 40,000–70,000 THB/month
- Remote/international: 60,000–100,000+ THB/month
- Key platforms: JobsDB Thailand, LinkedIn, Blognone
- Always include language proficiency (Thai + English)
- Indicate relocation willingness if applying to Bangkok from provinces
Fact Verification Pass (mandatory on EVERY review)
Agent drafts accumulate fabrication over time — details carried from earlier drafts, wrong guesses, and plausible-sounding specifics survive rewrites. Run this pass before approving any artifact:
- Primary-source check — re-read the user's own resume PDF / official documents; never trust details carried from earlier drafts. (Real cases that had to be removed: an NSTDA job entry, a KMUTNB degree/award for a CMU graduate, a Node upgrade attributed to an intern instead of the user.)
- Official-name check — web-search official names of tests, certifications, institutions before writing them. (Real case: CMU's English exit test is officially CMU-eGrad per reg.cmu.ac.th — guessed acronyms like "CMU TEP/TEGS" were wrong twice in a row.)
- URL check — HTTP-check every GitHub/portfolio URL in the artifact (
curl -s -o /dev/null -w "%{http_code}" <url>); 404 = remove the link or mark "none yet". A 404 under a personal account does NOT prove the repo doesn't exist — university/team projects often live under a GitHub organization account. Before deleting a link, probehttps://api.github.com/orgs/<Org>/reposor ask the user where the repo lives. (Real case: Transmatter lived under github.com/Transmatter org; it was nearly cut because probes only hit personal accounts.) - Cross-file contradiction scan — after ANY fact correction, grep ALL artifact files (resume, LinkedIn, master profile, STAR stories) for the old value and fix every occurrence, including memory. Verify clean with a final grep.
- Same-file consistency scan — look for numeric contradictions within one file (e.g., "50-person team" in About vs "20+ developers" in Experience).
- Attribution check — for every achievement claim, confirm who actually did the work (user vs intern vs team). Misattributed work collapses under interview probing. When two claims LOOK contradictory (e.g., "user upgraded Node 12→24" AND "intern upgraded Node 12→24"), do NOT assume one is wrong and flip the attribution — ask about project structure first. Real case: one legacy project had 4 modules (3 API + 1 web); user did the 3 API modules (0→90%+ tests), the intern independently did the web module (Babel→Vite, 100%). Both claims were true and both belong on the resume — module-level ownership questions resolve these. Split-ownership stories are STRONGER: one bullet shows technical execution, the parallel intern result shows mentoring.
- Planned-but-never-used tech — users often list tech they plan to learn. Confirm "did you use this in production?" — learning plans never go on resume/LinkedIn.
- Log corrections — append a numbered "Review Notes (date)" section to the vault note documenting every correction and why, so future sessions don't reintroduce errors. Save durable corrections to memory too.
When unsure about a fact, ask the user in ONE batched question (2–4 items) before rewriting — don't guess.
English Certification → Fluency Level (honest mapping)
| Certification | LinkedIn/resume fluency |
|---|---|
| TOEIC < 600 / A2–B1 | Limited Working Proficiency |
| TOEIC 600–780 / B2 (e.g., CMU-eGrad B2) | Professional Working Proficiency |
| TOEIC 785–900 / C1 | Full Professional Proficiency |
| TOEIC 900+ / C2 | Native or Bilingual Proficiency |
Never claim "Full Professional" on a B2 cert — interviewers probe English live and the mismatch reads as dishonesty. Keep resume and LinkedIn fluency identical.
Pitfalls
- Never invent metrics — estimate and mark
[CONFIRM], let user verify - Company names must be consistent across artifacts — use full legal names everywhere (e.g., "Agoda Services Co., Ltd.", not "Agoda" in one artifact and the full name in another). Ask the user for the registered name if unknown.
- Headline vs discretion conflict — "Open to New Opportunities" in a public headline contradicts a Recruiters-only Open to Work strategy (which hides the search from the current employer). Flag it; let the user choose.
- Every skills keyword must be evidenced — only list skills backed by an experience bullet or project; cut the rest (they invite interview questions the user can't answer).
- Always show before/after rewrites — suggestions alone are not actionable
- Test ATS compatibility by extracting PDF — if text is jumbled, ATS will reject it
- LinkedIn language levels are often wrong — native speakers underrate themselves
- Curate LinkedIn projects — 10 projects dilutes the strong ones; keep 2-4
- Don't skip market research — Thai conventions differ from US/EU conventions
Related Skills
grill-me— Use for STAR story extraction sessionsgrill-with-docs— Use when grilling also needs domain modeling
04 同仓库更多 Skills
project-spec-docs
Fill/update project_spec docs (templates, MM handoffs).
penpot-mcp
Penpot MCP: connect, verify, and fix streaming via nginx.
nginx-streaming-proxy
Configure nginx for streaming endpoints (SSE, MCP, WS).
branding-ci
Use for brand/CI identity, style guides, and brand docs.
yuanbao
Yuanbao (元宝) groups: @mention users, query info/members.
slidev
Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.