LockedIn

English | 한국어 | 简体中文

Before Linked In, get Locked In.

Drop a resume into Claude Code or answer a handful of questions to structure your experience once. After that, you just ask. English résumés, Korean cover letters, interview answers, and new project ideas all come out of calibrated skills.

Install

Inside Claude Code, run three commands.

/plugin marketplace add daypunk/LockedIn
/plugin install lockedin@lockedin
/lockedin:setup

The third command runs a one-time wizard. It wires the heads-up display, picks your default interview language, and chooses where to save your experience.

How you use it

LockedIn activates when you talk to Claude Code about your experience. There are no commands to memorize.

When you want to capture experience:

• "start organizing my experience"
• "log today's meeting with the design team"
• "absorb my resume.pdf"
• "add what I learned this week from a paper"

When you want to produce something from what is already captured:

• "make me an English resume"
• "I'm applying to company X for role Y, write the answer to question Z"
• "summarize last quarter's decisions"

LockedIn asks one question at a time when it needs more from you, and it stops when it has enough.

Why it exists

Most career tools regenerate every artifact from scratch. The artifact is the point, the source evaporates. LockedIn treats the source as the point. Your structured experience accumulates at ~/Documents/LockedIn/ as plain markdown files that you own and can carry to other tools. Resumes, cover letters, and meeting notes are artifacts of that memory, not the memory itself.

Features

• Natural-language activation. Talk to Claude Code the way you already do.
• One vault, four artifacts. Resumes, cover letters, interview answers, and project ideas all come from the same source.
• Quality guard built in. Drafting and scoring run as two separate Claude turns and every artifact ships with a JSON rubric score.
• Subscription, not API keys. Everything runs on your existing Claude Code subscription.

How it works

Your experiences are stored as plain markdown files with frontmatter. Every entity becomes one file. There are fifteen entity types covering people, companies, roles, projects, achievements, skills, education, certificates, publications, volunteer work, languages, documents, meetings, decisions, and topics. Relationships between entities are stored as links inside frontmatter, and the schema enforces which type can connect to which.

When you ask for a render, LockedIn queries the vault, drafts the output in one Claude turn, and then reviews the draft against a calibrated rubric in a separate Claude turn. The split prevents self-evaluation bias. When the same Claude call both writes and scores, it tends to be lenient with itself by about one point. The reviewer turn runs separately and reloads the rubric from scratch, which removes the inflation.

A master file EXPERIENCE.md is automatically maintained at the vault root (~/Documents/LockedIn/). Your entries live in per-type subfolders (person, company, role, project, and so on); instead of opening each folder, you can open this one file to scan the whole vault at a glance. If you edited markdown by hand and the master view feels stale, lockedin refresh rebuilds it.

LockedIn runs on your existing Claude Code subscription. It does not require an Anthropic API key, and it does not phone home.

Skills

Documentation

License

MIT. See LICENSE.