Lockedin Render Resume En (Grade A)Security-tested data-ai skill for Claude AI. Grade A. Writes an English resume from the user's experience, tuned to one of 10 built-in personas. Metric-first XYZ/CAR bullets, two-turn writer/reviewer

How it works?

1. Your experience gets structured. Drop a resume, answer a few short interview questions, or capture a moment from your current work. LockedIn organizes it into 15 typed markdown files in ~/Documents/LockedIn/. 2. Every claim is bound to a real entity. The writer turn cites companies, projects, and metrics as [[type/slug]] references pointing at specific vault files. Slugs are swapped for natural language right before you see the output. If no matching entity backs a claim, the slug stays in place and LockedIn asks you whether to add the entity rather than fabricating one. There is no opening for a new fact to slip in. 3. Two Claudes grade. Once the writer turn finishes, a separate reviewer turn reads RUBRIC.md fresh from disk and scores. Each artifact has its own 5 dimensions (for the English resume: metric density, action verb quality, structure, banned phrases, persona fit). You get a JSON alongside the markdown with per-dimension scores 0–5, a total, cited-entity recall, and any banned-phrase hits. If any dimension lands below 4, LockedIn auto-refines once before you see the result. 4. Your experience and your conversation stay in sync. If you edited a markdown file by hand, or said something in chat that conflicts with what's already there, LockedIn notices first and asks one focused question to reconcile. This is possible because your experience is stored as typed entities, not free-form text. The AI compares only the changed fields instead of re-reading everything.

Asked by Marcus Bell · Nov 10, 2025

Why it exists?

Most tools for organizing experience want you to leave your work, log in somewhere else, and remember everything that mattered. By then, half of it is already gone from your head. Other tools sit outside your work. LockedIn sits inside it. The moment you merge a line of code, lock in a meeting decision, or settle on a new design choice gets saved as structured experience. The flow doesn't break. Once saved, your experience connects to your outputs. Six months later when you need a resume, the six months of real work is right there. Stacked as markdown in your filesystem, not in someone else's database. Carry it to any tool, reuse it for any artifact.

Asked by Carlos Mendoza · Oct 20, 2025

How you use it?

No commands to memorize, no extra tab to open. Just start naturally inside Claude Code. To start fresh, build your experience from zero: "start organizing my experience" "interview me about my work history" "absorb my resume.pdf" While you're working, capture moments as they happen: "save this commit as a project highlight" "this meeting just wrapped, log it" "I just learned how to use X, track it" When you need to produce something: "make me an English resume" "I'm applying to company X for role Y, write the answer to question Z" "audit this resume PDF" LockedIn asks one question at a time when it needs more from you, and it stops when it has enough.

Asked by Damian Wysocki · Sep 14, 2025