Prepares for a specific company and role by mapping likely interview rounds, audience-specific questions, proof points, STAR story gaps, and questions to ask back. Use when the user mentions interview prep, preparing for a job interview, a mock interview, behavioral questions, or practicing for an upcoming round.
Prepare the user for an interview at a specific company and role using their selected text, the visible page, a pasted job description, or details they provide. Work only from sourced facts and the user's own background; never attribute an interview question to a source that didn't report it, and label job-description-derived questions as inferred. Use web search or browser tools for current interview-process, product, compensation, and culture signals when available. Adapted from santifer/career-ops interview-prep and deep modes.
Return concise headings, including these when they fit: Process overview, Audience map, Likely questions and answer angles, Story map, Technical or case prep, Company signals, Questions to ask, Prep priorities. Cite sources, say "unknown" when evidence is thin, and never invent questions, ratings, compensation, or interview statistics. Don't tell the user to lie about compensation, competing offers, authorization, notice period, or availability. If they give an interview date, add a short countdown based prep plan.
Request (job description on screen + a note):
Senior Product Manager at Northwind. Recruiter phone screen next week, then a hiring-manager round. JD stresses 0→1 launches and cross-functional leadership. My note: I led a payments launch but haven't written it up.
Prep:
Audience map
- Recruiter screen: motivation, timeline, location and comp fit — lead with why Northwind.
- Hiring manager: scope and first-90-days plan; tie your payments launch to their 0→1 mandate.
Likely questions and answer angles
- "Walk me through a 0→1 product you launched." (inferred from the job description) → STAR on the payments launch, result first.
Story map
- Missing detail: your payments launch has no outcome yet. What was the result — adoption, revenue, time-to-ship? Share one number and I'll build the headline.
Questions to ask
- "What does the first 0→1 win look like for this role over the next two quarters?"
Expect a comp question on the recruiter call — if you don't have a competing offer, defer: "I'm calibrating to market for this level; can you share the band?"
Approved by Chrome Web Store, Firefox Add-ons, and Apple App Store
Paper Reader
surfmindExplains academic papers, abstracts, PDFs, and technical articles by laying out their method, findings, limitations, and implications. Use when the user says "explain this paper", "summarize this study", "read this paper", "break down this research", or asks what a paper or abstract means.
Term Explainer
surfmindFinds the technical terms, acronyms, and domain phrases on the current page and defines each in plain language, with why it matters in this context. Use when the user says "explain the jargon", "define these terms", "what does X mean here", "build a glossary", or asks about acronyms, abbreviations, or unfamiliar terminology on the page.
Academic Search
claude-office-skillsSearch and analyze academic literature. Find papers, understand research methodologies, and synthesize academic findings for research projects.