787 skills · sorted by relevance
Manage recruiting in Ashby with natural language requests from Claude Code. Create and update candidates, create jobs and applications, review interview schedules and candidate notes, and combine records to report on hiring progress.
Plan user research, prepare interview guides, and organize findings into themes and recommendations. Choose methods suited to the question, such as interviews, surveys, or usability tests that examine how people use a design.
Set up regulatory monitoring by identifying which regulators to follow, what changes deserve attention, and where company policies are stored. The interview builds a watchlist, indexes policies, and checks which external connections actually respond.
Set up product legal workflows through an interview about company context, review practices, and approval routes. Past launch reviews help establish which risks block release, while connector checks record which tracking and document services actually respond.
Add documents, interview notes, or observations to an open investigation. Process batches against documented selection criteria, surface significant items, and log everything reviewed so the team can verify coverage and update its source checklist.
Write fictional short video interviews that place historical figures in a modern talk show. Combine historical traits with internet humor, then produce titles, host introductions, questions and answers, visual cues, and closing prompts for audience interaction.
Convert agreed goals, constraints, and success criteria into a Seed specification an agent can execute and verify. A quality review checks consistency and testable outcomes, with any suggested refinements left for the user to approve.
Interview the user for the raw material their posts are made of. Builds a lasting Story Bank of roles, numbers, turning points, scars and positions, or runs a focused interview that turns one topic into a post spine. Use when a draft has nothing concrete to draw on, or the user says interview me. Not for learning how they write (use linkedin-humanizer --mode profile).
The English summary is being prepared. Showing the original description.
Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use `summarize-interview`.
The English summary is being prepared. Showing the original description.
Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself. Use this to open a role, write a job description or scorecard, design an interview process, prepare interview questions, calibrate a hiring decision, or diagnose why a hiring process produces poor outcomes.
The English summary is being prepared. Showing the original description.
Prepare for recruitment at a Chinese state-owned enterprise (国企 / 央企), including its written test and interview: what these employers assess, the typical stages, answers that show fit and stability, and the questions to ask about the role. Use when asked 国企面试怎么准备, 央企校招, 国企笔试考什么, 国企和互联网怎么选, 国企面试问题, or prepare for a state-owned enterprise interview in China. Produces a stage map to confirm against the recruitment notice, a written-test preparation plan, a question bank with answer points, a mock interview with feedback, and a comparison with private-sector offers.
The English summary is being prepared. Showing the original description.
Plan and execute user research including research planning, recruiting, interview design, qualitative synthesis, and translating findings into product decisions. Use this skill whenever the user wants to plan user research, design interviews, recruit participants, conduct discovery, run formative research, or synthesize qualitative findings. Triggers on user research, UX research, user interviews, discovery research, generative research, formative research, qualitative research, user insights, research synthesis, recruitment, interview guide, jobs to be done. Also triggers when product decisions are being made without user input and the user wants to fix that.
The English summary is being prepared. Showing the original description.
Design calibrated interview loops, competency-based question banks, and hiring calibration. Use when designing interview processes, creating hiring pipelines, generating scoring rubrics, analyzing interviewer bias, or building question banks.
The English summary is being prepared. Showing the original description.
When the user needs to design an interview process, create interview questions, build scorecards, calibrate interviewers, or evaluate candidates for a role.
The English summary is being prepared. Showing the original description.
Use when users want to practice or simulate Java, C++, Go, Golang, mixed-stack, or general backend technical interviews, including resume-based and job-description-based interview preparation.
The English summary is being prepared. Showing the original description.
Use when the user says "run customer discovery", "help me interview customers", "write customer interview questions", "validate my assumption", "talk to users", "synthesize customer interviews", "what are my customers saying", "user research for my startup", "mom test interview", "are we solving a real problem", or wants to extract real insight from conversations with potential or existing customers.
The English summary is being prepared. Showing the original description.
Designs candidate-controlled mock interview practice across voice, text, code, and whiteboards. Use for session configuration, observable-evidence feedback, and adaptive practice plans. NOT for hiring decisions, emotion inference, gaze or integrity monitoring, or ranking candidates.
The English summary is being prepared. Showing the original description.
Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).
The English summary is being prepared. Showing the original description.
採用・人材戦略の専門スキル。職務記述書（JD）作成、採用計画策定、コンピテンシーモデル設計、 面接評価基準設計、オンボーディング計画をサポート。採用要件の明確化から内定後のフォローまで 一貫した人材獲得プロセスを支援。日英両言語のテンプレートを提供し、グローバル採用にも対応。 Use when: creating job descriptions, designing competency models, planning recruitment strategies, developing interview evaluation criteria, or creating onboarding plans. Triggers: "JD作成", "採用計画", "面接評価", "オンボーディング", "コンピテンシー", "人材獲得", "job description", "recruitment plan", "interview evaluation", "hiring", "talent acquisition"
The English summary is being prepared. Showing the original description.
Go through an interview that has just finished and sort out what happened: the questions asked and how fully they were answered, which of them were prepared for and which came from the submitted documents, the reverse questions still unanswered, what the employer said about conditions and whether any of it was in writing, and when a result was promised. Use when a user has just come out of an interview and wants to record it while it is fresh or to work out what to fix before the next round; do not use to judge how it went, to estimate whether they will pass, or to read anything into the interviewer's manner.
The English summary is being prepared. Showing the original description.
Prepare for a Japanese job interview by working from the documents already submitted: find where an interviewer will dig in (claims the applicant cannot back up, work described in the first person plural, outcomes with no measure, gaps or overlaps in the employment history, must-have requirements the documents never answer), and turn them into questions to prepare evidence for. Use when a user has an interview scheduled and wants to know what will be asked and what to have ready, or wants to prepare reverse questions from earlier company research; do not use to predict whether they will pass, to write answers containing experience they did not report, or to schedule or contact anyone.
The English summary is being prepared. Showing the original description.
The quick interview that captures a Domain's or major Feature's minimal (go-live) and final vision verbatim into its VISION.md. Use when a node shows VISION MISSING, a registry domain is ratified without a vision, gap analysis lacks a go-live bar, or on /domain-vision-interview <domain>.
The English summary is being prepared. Showing the original description.
Refine a plan or design through a persistent interview that asks probing questions. This skill starts the conversation by invoking the related grilling skill, providing an entry point for examining and sharpening what you have in mind.
Turn rambling messages or voice dictation into a structured brief covering goals, decisions, open questions, reversals, and parked ideas. Separate the agent’s assumptions from the user’s statements and confirm understanding before work begins.