hsablonniere/interview
skills/interview/SKILL.md
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.
tools
Updated Jun 15, 2026
$ install --global
skillsauthnpx skillsauth add hsablonniere/skills interviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 15, 2026, 2:22 AM10.0s1 file scanned
SKILL.md
- 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
<!-- Inspired by https://github.com/PierreZ/claude-personal-skills/blob/main/skills/spec-interview/SKILL.md -->
Interview
Read what the user wants to explore: <topic>$ARGUMENTS</topic>
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.).
Related Skills
hsablonniere/rebase
tools
VerifiedTrustedCommunity
Perform a non-interactive interactive git rebase. Use when the user asks to rebase, squash, reorder, drop, or rename commits.
SKILL.mdUpdated Jun 15, 2026
hsablonniere/pull-request
tools
VerifiedTrustedCommunity
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".
SKILL.mdUpdated Jun 15, 2026
hsablonniere/paper-review
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 15, 2026
hsablonniere/commit
tools
VerifiedTrustedCommunity
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".
SKILL.mdUpdated Jun 15, 2026