interview-guide
Skill1 starsChanged 2 months agoMITView on GitHub
Build a structured technical interview guide with a scoring rubric and an evaluation template, segmented by audience (e.g. engineer vs architect). Use whenever the user is preparing to interview or verify a candidate, asks for interview questions, a screening guide, or a candidate evaluation form.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- miguelclavel/ux-research-skillstheir own version, first seen Nov 8, 2026
- ql-link/drawoffer-skillstheir own version, first seen Nov 1, 2026
- Pearl1531/Archetype-talktheir own version, first seen Oct 13, 2026
- denchik2245/Skillstheir own version, first seen Oct 9, 2026
- talgacapri/pm-ostheir own version, first seen May 23, 2026
- nbirkner/digital-braintheir own version, first seen Apr 12, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Pearl1531/Archetype-talk★ 2same name
- denchik2245/Skills★ 1same name
- miguelclavel/ux-research-skills★ 1same name
- nbirkner/digital-brain★ 0same name
- ql-link/drawoffer-skills★ 0same name
- talgacapri/pm-os★ 0same name
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 repository28 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- architect-reviewSkill
- article-writingSkill
- changelog-watchSkill
- coordinator-workersSkill
- cost-forecastSkill
- design-docSkill
- documentSkill
- ea-briefingSkill
- estimateSkill
- eval-toolSkill
- gh-ticketsSkill
- headless-loopSkill
- job-supervisorSkill
- market-researchSkill
- meeting-notesSkill
- migration-planSkill
- obsidian-noteSkill
- plan-to-issuesSkill
- postmortemSkill
- readSkill
- release-notesSkill
- skill-stocktakeSkill
- slide-deckSkill
- status-reportSkill
- threat-modelSkill
- tradeoff-tableSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
If the audience is mixed (engineers AND architects), produce two question tracks.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
Produce a guide with:
- Role context — the competencies the role actually needs (pull from the JD/conversation).
- Competency areas — group questions by area (e.g. system design, language depth, AI-in-SDLC, collaboration).
- Calibrated questions — per area, 2–4 questions ordered easy → hard. For each: a model answer / what "good" sounds like, and concrete red flags.
- Scoring rubric — 1–5 per competency with anchored descriptions for 1, 3, and 5.
- Evaluation template — a fill-in block (scores per competency, evidence notes, overall recommendation: Strong Hire / Hire / No Hire).
If the audience is mixed (engineers AND architects), produce two question tracks; architects get more design/tradeoff/governance depth, engineers get more hands-on/implementation depth. Output Markdown only.
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.