interviewing-you
Skill0 starsChanged 35 days agoMITView on GitHub
How to get usable material out of the applicant without exhausting them. Use for /intake, /gaps, /picks, and any time you need information from the person.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- application-typesSkill
- application-writingSkill
- honesty-guardSkill
- mock-interviewSkill
- no-slop-writingSkill
- org-researchSkill
- reader-povSkill
- unasked-questionsSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Never ask what is already answered: Read you/PROFILE.md, you/STORY-BANK.md, you/VOICE.md, you/uploads/, and the relevant applications/ file …
- Distinctive: line 23
Lead with the blocking question: If one answer unblocks three applications, say that out loud.
- Distinctive: line 30
Never ask permission to do work they already asked for: Do it, then report.
- Distinctive: line 58
Every option must come from something they actually told you.
- Distinctive: line 59
Always end with "none of these, here is mine."
- Distinctive: line 86
When an answer is thin, the follow-ups that work:
- Distinctive: line 99
If they give you a resume, past essays, or writing samples, mine them before asking anything.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Getting material out of a person
The bottleneck was never writing. It is that nobody ever asked this person the right question about their own life. Most of the value in this kit is here.
Rules
Never ask what is already answered. Read you/PROFILE.md, you/STORY-BANK.md,
you/VOICE.md, you/uploads/, and the relevant applications/ file first. Asking
someone to repeat themselves is how these tools lose people.
Three to five questions at a time. Numbered. Never twenty.
Say fragments are fine, explicitly. They will write paragraphs otherwise, badly, and then be tired. Tell them: fragments, bullet points, one line, voice-memo transcripts, all fine. Prose is your job.
Lead with the blocking question. If one answer unblocks three applications, say that out loud. "Answer number 2 and I can write 180DC, RISE, and BTG tonight."
Ask for facts and opinions, not writing. "What would you actually do with the $10,000" gets you material. "Write about your community" gets you a bad paragraph you then have to undo.
Never ask permission to do work they already asked for. Do it, then report.
The pick-list move
This is the one that changes outcomes. When someone is tired, stuck, or facing a question about themselves they have never articulated, stop asking open questions and give them multiple choice built from their own material.
## 12. Your life as a TV show (BTG, 50 words)
**12a. Genre**
- **A.** Sports drama that turns into a tech drama.
- **B.** Coming-of-age comedy with an unreasonably high-stakes B plot.
- **C.** Docuseries where the guy keeps announcing a new plan and the narrator
gets tired.
**12b. Season one cliffhanger**
- **A.** She finally declares a major. Cut to black before she says which one.
- **B.** The app gets approved. The phone buzzes. She is asleep.They answer "A, C" and you have a real answer. Four minutes of their time.
Rules for pick lists:
- Every option must come from something they actually told you. No inventing a life.
- Always end with "none of these, here is mine."
- Make the options genuinely different, not three shades of the same answer.
- It is fine for one option to be funny. It is not fine for all of them to be safe.
- Number them continuously across the whole file so they can answer "14a, 15c, 16b" in one line.
Intake specifically
You are building a story bank, not a form. Go in this order:
- Inventory. What have you done. Fast, listy, no depth yet. Ten minutes.
- Pick the three that have a scene in them. A scene means a moment with a time, a place, and something at stake. Most people's best material is the thing they almost did not mention.
- Dig on those three. What went wrong. What did it cost. What did you do at the worst point. What number can you put on it. Who else was there.
- The thesis question. What do you believe that people around you do not? This is the highest-yield question in intake and most people have never been asked it.
- The reversal question. What did you believe two years ago that you no longer believe? Half of all application prompts are secretly this question.
- Numbers pass. For every claim, get the defensible figure and where it comes from. Write it in PROFILE.md once. It goes in every document unchanged.
- The boundaries pass. Is there anything you do not want in any application? Write
it in
you/DISCLOSURE.mdand honor it without relitigating.
Digging
When an answer is thin, the follow-ups that work:
- "What was the worst moment of that?"
- "What did you actually do, hour by hour?"
- "What did it cost you?"
- "Who else was in the room?"
- "What would have happened if you had done nothing?"
- "What is the part of that story you usually leave out?"
The last one is the best question in the list. Use it once per session, not more.
Reading their uploads
If they give you a resume, past essays, or writing samples, mine them before asking anything. Resumes especially: every bullet is a story compressed to one line, and "what happened behind this bullet" is a better prompt than anything you would invent.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

