interview
Skill2 starsChanged 53 days agoMITView on GitHub
Extract your actual thinking on a chosen content spike. Optionally runs a research brief first, then a panel of six interviewer personas questions you one at a time until there's enough specific material to draft from. Produces the interview transcript that becomes the ONLY source corpus for drafting. Trigger phrases include "interview me", "run the panel", "/interview".
94 other projects use a version of this.
Adopted by
Most recently taken up by
- chrisdesmondSML/chris-skillstheir own version, first seen Nov 8, 2026
- Firzus/agent-skillstheir own version, first seen Nov 8, 2026
- claude-code-hardened/claude-code-hardenedtheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- yuri-xyz/skillstheir own version, first seen Nov 8, 2026
- codewhale-hq/codewhale-plugin-marketplacetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use fetch-library-docs, contributor and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Rehan-Ul-HaqSkillfetch-library-docs
Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.
Also in 4 projects that use this
NimbleBrainIncSkillcontributor
Get started contributing to NimbleBrain open source — find an integration to build, set up your environment, propose an idea, or check on your work. Use when onboarding as a contributor. Triggers include "I'm a new contributor", "what should I build", "show me open issues", "file an issue".
Also in 3 projects that use this
mjunaidcaSkillbrowsing-with-playwright
Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use when tasks require web browsing, form submission, web scraping, UI testing, or any browser interaction. NOT when only fetching static content (use curl/wget instead).
Also in 4 projects that use this
qa-amanSkillteach-me
Teach a topic, video, article, codebase change, spec, or transcript until the user demonstrably understands it, using staged instruction, a running checklist doc, and quizzes. Use whenever the user says "teach me", "explain this in detail", "help me understand X", "/teach-me", "walk me through this", "I want to learn X", "understand this deeply", or pastes a YouTube URL, article, paper, PR, or spec and asks to understand it rather than summarize it. Also use when the user wants study notes or raw material from a source they are learning. Do NOT use for a quick factual lookup, a summary request, or when the user just wants the answer.
Also in 8 projects that use this
trebaudSkillfind-unknowns
Workflow for surfacing a task's unknowns before, during, and after implementation — blind spot pass, brainstorm/prototype, interview, references, implementation plan, deviation notes, quiz. Use when starting work in an unfamiliar domain or codebase, when a task feels underspecified, when the user says "find my unknowns", "blindspot pass", "what am I missing", "help me scope this", or when a long task came back wrong.
Also in 3 projects that use this
donatassimkusSkilloffer
Offer design, pricing strategy, and business model architecture. Invoke when asked about making an offer better, pricing a product or service, naming an offer, raising prices, generating fast cash, increasing lifetime value, finding the right customer, qualifying buyers, or designing a business model where customers pay for their own acquisition. Use when someone says their offer isn't converting, they need to charge more, they want to add bonuses or guarantees, or they need a money model for their business.
Also in 3 projects that use this
Other versions94 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 94
- claude-code-best/claude-code★ 23ksame name
- Q00/ouroboros★ 6.3ksame name
- Hisn00w/ASu-skills★ 6.1ksame name
- boshu2/agentops★ 453same name
- genkovich/sdd★ 187same name
- jvm-skills/jvm-skills★ 140same name
- kv0906/pm-kit★ 138same name
- tobieapb/claude-interactive-documentation-workflow★ 105same name
- panaversity/claude-code-skills-lab★ 57same name
- roman01la/skills-agents★ 48same name
84 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- content-machineSkill
- content-setupSkill
- draftSkill
- lessonsSkill
- oracleSkill
- repurposeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 80 edited versions we read keep these.
2
Distinctive
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 10
Read first: reference/interviewer-personas.md.
- Distinctive: line 20
If the spike involves external claims or a public debate the user hasn't fully tracked, offer a research brief before questioning:
- Distinctive: line 44
Stop-condition checklist (story / position / 2+ specifics) passes — state the three items explicitly.
“Common” is measured: kept by at least 6 in 10 of the 80 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interview — the panel extracts, the transcript becomes law
Read first: reference/interviewer-personas.md. Personal folder resolution: ~/.content-machine/redirect.md first line if present, else ~/.content-machine/.
Why this step exists: the machine's anti-slop guarantee is that drafts may only use words you said here (hook and closing excepted). Thin interview → thin piece. As Alex Lieberman put it: when the machine produces slop, that's an indictment of the interview answers, not the AI.
Step 1 — Confirm the spike
Take the spike the user picked (from /oracle or stated directly). Restate it in one line.
Step 2 — Research brief (optional, offer it)
If the spike involves external claims or a public debate the user hasn't fully tracked, offer a research brief before questioning:
- What the principals actually said (quotes, links)
- The strongest version of each side
- Potential contrarian or novel angles nobody has taken
- Open questions the user could be the one to answer
Skip for pure lived-experience spikes — the user already has the material.
Step 3 — The panel
Run per the shared rules in reference/interviewer-personas.md. Ask one question at a time. Rotate personas, and label each question with its persona. Ask ~5 questions total. Build every follow-up on the previous answer. Always chase specificity. Encourage voice-to-text answers — speed produces unguarded phrasing, and unguarded phrasing is voice.
Stop condition: you have (a) at least one lived story with specifics, (b) a falsifiable position, (c) at least two concrete details (names/numbers/quotes). If 5 questions haven't produced these, say which is missing and ask up to 3 more — don't draft from a corpus that fails this bar.
❌ Panel malpractice: "It sounds like you're saying deployment expertise matters more than model quality — is that right?" (feeds the subject its own phrasing; contaminates the corpus) ✅ "Larry King: In one or two sentences — what are Levie and Mollick both missing?"
Step 4 — Write the transcript
Save verbatim Q&A to transcripts/YYYY-MM-DD-<spike-slug>.md in the personal folder, with the spike statement and research-brief pointer at top. Do not clean up the user's phrasing — the "mess" is the voice.
Gate before handing to /draft
- Transcript file exists and contains the user's words verbatim.
- Stop-condition checklist (story / position / 2+ specifics) passes — state the three items explicitly.
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.