interview-me
Skill4 starsChanged 4 months agoLicence not identifiedView on GitHub
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 59 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 59 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Other versions92 projects use a version of this.
Word for word · 19
- jaskirat1616/grok-skills★ 22100% same
- HK-hub/AgentSkills★ 6100% same
- ddddjaak/ae-skills★ 4100% same
- PenceZHR/stagepass★ 4100% same
- Adhamxon/claude-code-skills★ 2100% same
- RainMT-dv/skills-pack★ 2100% same
- christianmz565/skills★ 1100% same
- FuSheng-MG/Pi-Agent-skills★ 1100% same
- zdnemz/claude-team★ 1100% same
- ZeroTokenClaw/agents-skills★ 1100% same
9 more not listed
Edited · 27
- addyosmani/agent-skills★ 112k95% same
- mycelium-hq/ai-brain-starter★ 5089% same
- vinvcn/addyosmani-agent-skills-zh★ 4636% same
- sampleXbro/agentsmesh★ 24100% same
- JPeetz/agent-skills★ 1483% same
- mxrsv/agents-skills★ 983% same
- Marvellbrazil/my-agentic-skills★ 495% same
- b-mendoza/agent-skills★ 395% same
- pytholic/claude-skills★ 382% same
- bnalwalid/walidforge-skills★ 213% same
17 more not listed
Wrote their own version · 46
- pedrohcgs/claude-code-my-workflow★ 1.6ksame name
- kdlbs/kandev★ 1ksame name
- Neeeophytee/finding-unknowns-skills★ 339same name
- flonat/flonat-research★ 145same name
- maxwell2732/paper-replicate-agent-demo★ 134same name
- maxwell2732/my-submission-formatting-agent★ 106same name
- PaulRBerg/agent-skills★ 104same name
- c-kick/hnl-agent-skills★ 56same name
- Sorbh/interview-me★ 52same name
- zvadaadam/az-skills★ 50same name
36 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use constraint-driven-development, observability-and-instrumentation and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 16 projects that use this
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 31 projects that use this
orenluxySkillimplementation-notes
Maintain an IMPLEMENTATION_NOTES.md decision log during any multi-step implementation session. Use this in EVERY session that involves writing or modifying code across more than one file, or any session expected to run longer than a few tool calls. Records decisions, deviations from plan, and open questions so nothing is silently guessed.
Also in 3 projects that use this
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- api-and-interface-designSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- doubt-driven-developmentSkill
- git-workflow-and-versioningSkill
- idea-refineSkill
- incremental-implementationSkill
- performance-optimizationSkill
- planning-and-task-breakdownSkill
- security-and-hardeningSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- using-agent-skillsSkill
- zynk-pre-release-auditSkill
- debugging-difficult-bugsSkill
- pr-explainerSkill
- pr-splitterSkill
- smoke-testSkill
- zynk-docsSkill
- zynkSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

