Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

interview

Estrelas0

Forks0

Atualizado11 de fevereiro de 2026 às 21:25

Interview the user to deeply explore an idea, feature, or problem through Q&A. Use when the user asks to be interviewed, wants to think through something, or needs help clarifying a concept.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

hsablonniere

hsablonniere/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de pesquisa de mercado e especialistas em marketingNegócios e Operações Financeiras·SOC 13-1161

SKILL.md

readonly

name	interview
description	Interview the user to deeply explore an idea, feature, or problem through Q&A. Use when the user asks to be interviewed, wants to think through something, or needs help clarifying a concept.
argument-hint	["what you want to explore"]
model	opus
allowed-tools	AskUserQuestion, Read

Interview

Read what the user wants to explore: $ARGUMENTS

Interview the user in depth using AskUserQuestion. Adapt the questions to the topic — this could be a feature, an architecture decision, a process, a problem to solve, or any idea worth exploring.

Dig into:

Goals and constraints
Tradeoffs and alternatives considered
Edge cases and unknowns
Non-obvious decisions
Anything that seems underspecified

Don't ask surface-level questions — challenge assumptions and explore the hard parts.

Keep interviewing until the user says "done" or signals they're ready to move on. Do not stop early.

When the interview is over, provide a concise summary of what was clarified, then let the user decide the next step (plan mode, implementation, write a doc, etc.).

Mais deste repositório

mesmo repositório

paper-review

hsablonniere/skills

Conversational code review written to a markdown file the reviewer annotates, then acted on. Use when the user asks to review the current branch or diff, runs /paper-review (optionally with "working tree", "staging", "rescan", or a ref/range), says "review my changes", or asks to act on their annotations in an existing review file.

2026-06-140

pull-request

hsablonniere/skills

Create a Pull Request (GitHub) or Merge Request (GitLab) with a well-crafted title and description. Use when the user asks to create a PR, MR, open a pull request, submit a merge request, or says something like "open a PR".

2026-03-150

rebase

hsablonniere/skills

Perform a non-interactive interactive git rebase. Use when the user asks to rebase, squash, reorder, drop, or rename commits.

2026-02-110

commit

hsablonniere/skills

Create a git commit with a well-crafted conventional commit message. Use when the user asks to commit, create a commit, or says something like "commit this".

2026-02-110

name	interview
description	Interview the user to deeply explore an idea, feature, or problem through Q&A. Use when the user asks to be interviewed, wants to think through something, or needs help clarifying a concept.
argument-hint	["what you want to explore"]
model	opus
allowed-tools	AskUserQuestion, Read

Interview

Read what the user wants to explore: $ARGUMENTS

Interview the user in depth using AskUserQuestion. Adapt the questions to the topic — this could be a feature, an architecture decision, a process, a problem to solve, or any idea worth exploring.

Dig into:

Goals and constraints
Tradeoffs and alternatives considered
Edge cases and unknowns
Non-obvious decisions
Anything that seems underspecified

Don't ask surface-level questions — challenge assumptions and explore the hard parts.

Keep interviewing until the user says "done" or signals they're ready to move on. Do not stop early.

When the interview is over, provide a concise summary of what was clarified, then let the user decide the next step (plan mode, implementation, write a doc, etc.).