Skills Hub

Finds 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.

Creates a staged learning plan from a topic, course page, or documentation set with goals, practice tasks, and checkpoints. Use when the user wants a "study plan", "learning roadmap", "curriculum", "syllabus", "learning path", or asks "how do I learn X" or "help me learn X in N weeks".

Explains a repository's purpose, structure, setup and run commands, key scripts, and the first files worth opening. Use when the user wants to understand a new repo or codebase — "what does this project do", "how do I get started", "give me a codebase overview", "onboard me to this repo".

Breaks a regular expression down into plain-language parts with examples of what it matches and what it rejects. Use when the user asks to explain, decode, or understand a regex, regexp, or pattern — "what does this regex match", "explain this pattern", a .match/.test call.

Explains how to pronounce and naturally use a selected word or phrase, with register, meaning, collocations, and example sentences. Use when the user asks "how do you pronounce / how do you say this", "what does X mean", or wants vocabulary and usage help for a foreign-language word or phrase.

Evaluates whether a portfolio project, side project, or resume project idea is worth building to land a target role, scoring role signal, uniqueness, demo ability, metrics, time to a working version, and interview-story potential. Use when the user asks if a project idea is worth building, wants to evaluate side projects for a job search, or wants to pick a project that signals to hiring managers.

Explains 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.

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.

Explains selected or visible content in plain language, including the core idea, jargon, and background, while researching further when the page falls short and staying evidence-backed. Use when the user says "explain this", "what does this mean", "simplify", "break this down", "ELI5", or "help me understand" about highlighted text, code, or on-screen content.

Evaluates whether a specific course, certification, bootcamp, or training is worth the time and money for the user's stated career goal, weighing recruiter signal, time and opportunity cost, risks, and the artifact it produces. Use when the user asks whether a course, certification, bootcamp, or training is worth it, or when evaluating training ROI against a career goal.

Converts a code snippet from one programming language to another while preserving behavior and flagging library, runtime, and type-system differences. Use when the user asks to translate, port, rewrite, or convert code between languages — "port this to Python", "rewrite in Rust", "convert Java to Go".

Translates selected text and explains the idioms, cultural nuance, key terms, and phrasing that should not be read literally. Use when the user says "translate this", "in Spanish/French/Japanese/etc.", "what does this mean", "explain this phrase", or wants foreign-language text rendered with the context behind it.

Turns REST API documentation into a runnable curl, fetch, or code example with required headers, request body, and placeholders for secrets. Use when the user wants to generate a request from API docs, an endpoint, or a Swagger/OpenAPI spec — "give me a curl for this", "show a fetch example", "how do I call this API".

Answers a question grounded in the selected text or visible page, researching further when the page falls short, always evidence-backed and never invented. Use when the user highlights a passage or is on a page and asks "what does this mean", "answer this", "where does it say", or any who/what/why/how question about that content.

High-rigor interview coaching skill for job seekers. Use when someone wants structured prep, transcript analysis, practice drills, storybank management, or performance tracking. Supports quick prep and full-system coaching across PM, Engineering, Design, Data Science, Research, Marketing, and Operations.

When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.

Search and analyze academic literature. Find papers, understand research methodologies, and synthesize academic findings for research projects.