interview
Skill0 starsChanged 9 months agoNo licenceView on GitHub
This skill conducts discovery conversations to understand user intent and agree on approach before taking action. It should be used when the user explicitly calls /interview, asks for recommendations, needs brainstorming, wants to clarify, or when the request could be misunderstood. Prevents building the wrong thing by uncovering WHY behind WHAT.
105 other projects use a version of this.
Adopted by
Most recently taken up by
- endqwerty/endstacktheir own version, first seen Nov 16, 2026
- antick/skillstheir own version, first seen Nov 16, 2026
- mahirhacks/mstacktheir own version, first seen Nov 16, 2026
- ronedgecomb/anythingtheir own version, first seen Nov 16, 2026
- andymai/claude-agent-teamtheir own version, first seen Nov 16, 2026
- Renozoic-Foundry/forge-publictheir own version, first seen Nov 15, 2026
Used with
Projects with it also use contributor, teach-me and 6 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.
NimbleBrainIncSkillcontributor
Get started contributing to NimbleBrain open source — find an integration to build, set up your environment, propose an idea, or check on your work. Use when onboarding as a contributor. Triggers include "I'm a new contributor", "what should I build", "show me open issues", "file an issue".
Also in 3 projects that use this
qa-amanSkillteach-me
Teach a topic, video, article, codebase change, spec, or transcript until the user demonstrably understands it, using staged instruction, a running checklist doc, and quizzes. Use whenever the user says "teach me", "explain this in detail", "help me understand X", "/teach-me", "walk me through this", "I want to learn X", "understand this deeply", or pastes a YouTube URL, article, paper, PR, or spec and asks to understand it rather than summarize it. Also use when the user wants study notes or raw material from a source they are learning. Do NOT use for a quick factual lookup, a summary request, or when the user just wants the answer.
Also in 8 projects that use this
trebaudSkillfind-unknowns
Workflow for surfacing a task's unknowns before, during, and after implementation — blind spot pass, brainstorm/prototype, interview, references, implementation plan, deviation notes, quiz. Use when starting work in an unfamiliar domain or codebase, when a task feels underspecified, when the user says "find my unknowns", "blindspot pass", "what am I missing", "help me scope this", or when a long task came back wrong.
Also in 3 projects that use this
donatassimkusSkilloffer
Offer design, pricing strategy, and business model architecture. Invoke when asked about making an offer better, pricing a product or service, naming an offer, raising prices, generating fast cash, increasing lifetime value, finding the right customer, qualifying buyers, or designing a business model where customers pay for their own acquisition. Use when someone says their offer isn't converting, they need to charge more, they want to add bonuses or guarantees, or they need a money model for their business.
Also in 3 projects that use this
galsapirSkilllong-horizon
Transform a user's draft prompt into a long-horizon coding-agent task prompt. Use when the user asks to make a prompt long-horizon, turn something into a long-running agent task, add long-horizon scaffolding, or invokes "$long-horizon" or "/long-horizon". Appends framing for running far without unnecessary stops, using subagents for scoped background work, and maintaining implementation-notes.html with decisions, deviations, tradeoffs, and open questions.
Also in 3 projects that use this
LesaniSkillste
Rewrite prose (docs, READMEs, PR descriptions, error messages, release notes, comments — never code) into ASD-STE100 Simplified Technical English to remove "AI slop". Use when asked to make writing not sound like AI, make docs clear or plain, enforce a controlled writing style, or write technical documentation that reads human. Two modes — strict (procedures/safety) and STE-flavored (general prose).
Also in 3 projects that use this
Other versions105 projects use a version of this.
Word for word · 3
- panaversity/claude-code-skills-lab★ 57100% same
- sheikh-mohammad/agent-factory-claude-skills★ 6100% same
- syeda-hoorain-ali/personal-ai-employee-hackathon★ 0100% same
Edited · 0
None found.
Wrote their own version · 102
- claude-code-best/claude-code★ 23ksame name
- Q00/ouroboros★ 6.4ksame name
- Hisn00w/ASu-skills★ 6.1ksame name
- boshu2/agentops★ 454same name
- genkovich/sdd★ 187same name
- jvm-skills/jvm-skills★ 140same name
- kv0906/pm-kit★ 138same name
- tobieapb/claude-interactive-documentation-workflow★ 105same name
- roman01la/skills-agents★ 48same name
- hiddenjobs/job-search-mcp★ 28same name
92 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.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- browsing-with-playwrightSkill
- doc-coauthoringSkill
- docker-skillSkill
- docxSkill
- fastapiSkill
- fastmcp-guideSkill
- fetch-library-docsSkill
- frontend-designSkill
- internal-commsSkill
- nextjs-app-router-skillSkill
- openai-agents-skillSkill
- pdfSkill
- pptxSkill
- pytest-fastapiSkill
- skill-creator-proSkill
- skill-creatorSkill
- skill-validatorSkill
- sqlmodelSkill
- theme-factorySkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 85 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 85 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.
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.

