Is Interview Me safe and trustworthy?

tashan scores Interview Me on public evidence — tashan score 43.0/100, it is currently active, note: a single primary maintainer (bus-factor risk). Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Interview Me?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Interview Me?

1 GitHub contributors, source: pySilver/cc-tools.

‹ The Index

Interview Me

skill

Extracts what the user actually wants instead of what they think they should want, through a one-question-at-a-time interview until ~95% confidence about the underlying intent. Each question carries the agent's own guess, so the user reacts instead of composing from scratch. Use when an ask is underspecified ("build me X" with no "for whom" or "why now"), when two reasonable values are in tension and the user has not said which one wins, or when you catch yourself silently filling in ambiguous requirements before any plan, spec, ADR, or code exists. Activates on "interview me", "grill me", "before we start, are we sure?", or "stress-test my thinking".

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Dev Tools & CI — see all ranked ›

Install (Claude Code):

cp -r interview-me ~/.claude/skills/

tashan score: 43.0
Adoption: 3 repos
Upkeep: 62.0
Freshness: 95.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 1
License: MIT

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it, says when not to, shows worked examples and states a limitation.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Interview Me scores 43 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/skill-pysilver-interview-me.svg)](https://tashan.sh/capability/skill-pysilver-interview-me.html)

source ↗ · skill:pySilver/interview-me

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-12 · scorer s5 · how · something wrong here?