- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nishant-Tiwari24/cracked --skill defend-my-project -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nishant-Tiwari24/cracked --skill defend-my-project -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nishant-Tiwari24/cracked --skill defend-my-project -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nishant-Tiwari24/cracked --skill defend-my-project -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/nishant-Tiwari24/cracked/tree/HEAD/skills/interview/defend-my-projectFrom the publisher
"Walk me through your project" is in nearly every interview, and it's where many candidates fall apart: they built it, but can't explain why it's built that way. You read their real code, then interview them the way a sharp engineer would.
git clone <url> "$(mktemp -d)/repo". If it's very large, git clone --filter=blob:limit=1m and say so.Verify before you accuse. Every claim you'll quote back must have evidence:
package.json scripts, Makefile, pytest.ini, go test ./...). Tell the candidate you're about to run them, and run them read-only. Never install dependencies or run install scripts from an unfamiliar repo without asking, because they can execute arbitrary code; if running isn't safe, read instead and say so. Base every testing question on the result ("npm test isn't defined", "pytest: 3 failed"), not on a guess.git grep -nIE '(api[_-]?key|secret|password|token)\s*[:=]|AKIA[0-9A-Z]{16}|sk-[A-Za-z0-9]{20,}|-----BEGIN [A-Z ]*PRIVATE KEY') and history (git log -p -S'SECRET' --all | head -200, repeated for KEY, TOKEN, PASSWORD). A real leaked secret becomes question #1, with a rotate it now and purge it from history warning (same rule as github-glowup).git log --format= --name-only | sort | uniq -c | sort -rn | head -20), and tell the candidate you sampled.Then read the project like an interviewer prepping for the round. Look at the README, dependency manifests, entry points, folder structure, data models/schemas, API routes, auth, config/env handling, tests, CI, deploy files, and the git log (git log --oneline | head -50, and git shortlog -sn for team projects).
Build an attack list of 12–20 questions across these categories, each grounded in a specific file or line:
Order them from easy to hard. Mark the 3–5 most dangerous: questions that expose real flaws in the code.
Save the attack list, with the file:line evidence for each question, to $CRACKED_DIR/defense/.hidden/<repo-name>-attack-list.md. It lets a later session resume where this one stopped, and becomes the skeleton of the defense sheet. Tell the candidate it's there and not to open it until the session is over.
Tell the candidate: "I've read your code. I'm going to interview you about it like a senior engineer would. Answer as if you're in the room."
POST /orders", naming the real route and file. Save the 30-second pitch for later in the session.server/auth.js:41 you…").Write $CRACKED_DIR/defense/<repo-name>.md containing:
/make-it-hireable.Call the Skill tool with "cracked-profile" and log a scorecard titled with the repo name. Dimensions: Ownership & Depth, Technical Justification, Honesty About Weaknesses, Communication, Scale Thinking.
Skill calls: if your agent has no Skill tool, open the named skill's SKILL.md in the cracked skills folder (core/, interview/, profile/, strategy/) and follow it instead.
Interviewers always grill candidates on their resume projects ("why MongoDB?", "what happens at 10k users?", "what was the hardest bug?"). This skill reads the candidate's actual project code (current
---name: defend-my-projectdescription: Interviewers always grill candidates on their resume projects ("why MongoDB?", "what happens at 10k users?"…---# skills/interview/defend-my-project/SKILL.mdOverview
Interviewers always grill candidates on their resume projects ("why MongoDB?", "what happens at 10k users?", "what was the hardest bug?"). This skill reads the candidate's actual project code (current repo or a GitHub URL), finds every decision an interviewer would attack, then cross-examines them one question at a time and writes a defense sheet of prepared answers. Use when the user wants to prepare to explain or defend their project, be grilled on their GitHub repo, prepare for "walk me through your project", or practise project-based interview questions.
FAQ
Download skills/interview/defend-my-project/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/nishant-Tiwari24/cracked.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.