793 skills · sorted by relevance
Set up a commercial contracts assistant around your team's review standards and approval rules. The interview creates an editable practice profile and can compare stated negotiation positions with terms found in signed agreements.
Answer Python questions and write code using examples fetched from pythonsheets.com. Find patterns for syntax, asynchronous tasks, networking, databases, machine learning, and distributed computing, or use topic-based questions to prepare for Python interviews.
Build a threat model that identifies valuable assets, attack entry points, potential threats, and mitigation priorities. Use source code and past vulnerabilities, an interview with the application owner, or a combination of both.
Analyze public reviews, app stores, and forums to identify unmet customer needs, competitor weaknesses, and reasons for switching products. Receive short customer quotes with source links, recurring themes, and hypotheses to validate in interviews.
Build a company research brief from public sources, covering executive statements, product strategy, organizational practices, and transformation initiatives. Use dated sources to prepare for interviews, understand competitors, assess potential partners, or explore market entry.
Guide a product team from a problem hypothesis through customer interviews, research synthesis, and solution experiments. Use six structured phases to gather evidence, compare options, and decide whether to build, change direction, or stop.
Work through the move from product manager to Director with questions tailored to your stage. Get practical recommendations for promotion preparation, interviews, early leadership challenges, or persistent difficulties in the role.
Register and search existing Git repositories and worktrees, then choose which projects Ouroboros interviews use as context. You can also generate a configuration containing verified build, test, and other check commands for the evaluation workflow.
Turn a vague development idea into clear goals, constraints, and acceptance criteria through a guided interview. It checks unresolved decisions and confirms the agreed goal before moving toward a Seed, the requirements document used by Ouroboros.
Structured conversational interview to formalise a research idea or extension into a concrete specification with hypotheses and empirical strategy. This skill should be used when asked to "interview me", "help me think through an idea", "formalise this idea", or "start fresh" on a new research direction.
The English summary is being prepared. Showing the original description.
[omh] Vague, underspecified request: one-question-at-a-time clarification. Use when the user says: deep-interview, interview me, clarify, feature shaping, ambiguous product request, one question, 要件を詰めて, 曖昧な要求.
The English summary is being prepared. Showing the original description.
SUPERSEDED by /claudex-loop (formerly /crucible; adds a Phase 0 research/recon pass + rebuilt interview) — prefer that skill unless you explicitly want this one. Two-act plan hardening. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan or design, one question at a time, recommending an answer for each and exploring the codebase when it can answer itself, until every branch of the decision tree is resolved. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-me-codex", "grill me then have codex review", "grill me and stress-test the plan", "interview me about this plan then get a second model on it", or is about to build something high-stakes (auth, schema, concurrency, migrations, payments) and wants both alignment AND a cross-model sanity check before implementation. Builds on Matt Pocock's grill-me (MIT). For the docs-aware variant use /grill-with-docs-codex; if you already have a plan and want only the Codex review use /codex-review. NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.
The English summary is being prepared. Showing the original description.
Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.
The English summary is being prepared. Showing the original description.
Mock interview preparation tool for residency Match interviews. Generates.
The English summary is being prepared. Showing the original description.
Curated bank of interview problems organized by company, pattern, and difficulty. Provides problem recommendations, coverage tracking, weak area identification, and premium problem alternatives for FAANG interview preparation.
The English summary is being prepared. Showing the original description.
Interactive interview that formalizes a fuzzy research idea into a structured spec (RQ, hypotheses, identification, data needs, empirical strategy). Use when user says "interview me", "help me think through this idea", "I have a half-baked idea", "formalize this into a project", "walk me through framing a study". Multi-turn Q&A; saves spec to disk. NOT for lit review (`/lit-review`) or ideation from scratch (`/research-ideation`).
The English summary is being prepared. Showing the original description.
Use when asked 帮我准备大厂技术面试, 八股文怎么背, 模拟一面二面, 系统设计面试题, 项目深挖怎么答, 手撕算法, or run a mock technical interview for a Chinese internet company. Produces a preparation plan for the interview rounds Chinese tech companies run (笔试, 技术一面二面, 交叉面, HR 面), a 八股 question bank by stack with answer points, a system design walkthrough, a project deep-dive script, and a mock round asked one question at a time with follow-ups (追问) and scores.
The English summary is being prepared. Showing the original description.
Turn interview notes into a structured candidate scorecard and hire recommendation. Use when asked to write an interview scorecard, a candidate evaluation, an interview debrief, or to summarize feedback into a hire/no-hire call. Produces a per-competency assessment with evidence and ratings, an overall recommendation with confidence, and the open questions for the next round — evidence-based, bias-aware, and decision-ready.
The English summary is being prepared. Showing the original description.
Talent acquisition across recruiting strategy, sourcing, interviews, and hiring analytics. Use when writing job descriptions, designing interview scorecards, analyzing hiring funnels, or improving offer acceptance rates.
The English summary is being prepared. Showing the original description.
Mathematically rigorous Socratic interview system that drives ambiguity below 20% before any code is written. One question per message, weighted ambiguity scoring, brownfield-aware, outputs a complete PRD. Replaces discovery-interview with a stricter protocol.
The English summary is being prepared. Showing the original description.
Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.
The English summary is being prepared. Showing the original description.
Use when validating product assumptions before building, discovering unmet user needs, understanding customer problems and workflows, testing concepts or positioning, researching target markets, identifying jobs-to-be-done and hiring triggers, uncovering pain points and workarounds, or when users mention user research, customer interviews, surveys, discovery interviews, validation studies, or voice of customer.
The English summary is being prepared. Showing the original description.
Async Interview integration. Manage data, records, and automate workflows. Use when the user wants to interact with Async Interview data.
The English summary is being prepared. Showing the original description.
Your first 10 hires determine your company culture. Your first 50 determine your execution capacity. Hiring is the most leveraged activity a founder does, and the most common source of expensive mistakes. This skill covers when to hire, who to hire first, how to sequence roles, compensation and equity, interviewing and closing, and the many ways hiring goes wrong at startups. Use when "hiring, first hire, when to hire, who to hire, compensation, equity, salary, recruiting, interview process, offer negotiation, team building, engineer hire, sales hire, founding team, hiring, team, compensation, equity, recruiting, interviews, offers, startups, founding-team" mentioned.
The English summary is being prepared. Showing the original description.