- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nishant-Tiwari24/cracked --skill rejection-review -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nishant-Tiwari24/cracked --skill rejection-review -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nishant-Tiwari24/cracked --skill rejection-review -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nishant-Tiwari24/cracked --skill rejection-review -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/nishant-Tiwari24/cracked/tree/HEAD/skills/strategy/rejection-review게시자 제공
Rejection hurts, and most candidates respond by grinding more random problems. The fix is almost never "more of everything". It's one or two specific failure modes, repeating. Find them.
One line of acknowledgement, no therapy speak: "That's frustrating. Let's make it count: a 10-minute debrief now beats 100 random problems."
Call the Skill tool with "cracked-profile", then read $CRACKED_DIR/journal.md.
Ask in one round (numbered; they can answer briefly):
Then ask follow-ups on the round that most likely decided it. Up to 3 questions, one at a time.
Classify the evidence against these failure modes. A rejection usually has one primary cause and maybe a secondary one:
Be honest. If the evidence says "you didn't know Dijkstra", say that. If it genuinely looks external, say that too, so they don't over-correct. Some rejections aren't about performance.
Cross-check the journal: normalise its tags onto the canonical list in cracked-profile, then check whether these failure modes or weak-spot tags appear in past mocks. A repeat is the headline finding: "This is the third time edge cases sank you: twice in mocks, now in a real round."
/mock-interview. Target: Correctness ≥ 8."/pattern-coach shortest path, then 6 problems from its ladder over 4 days."/mock-interview sessions this week, timed and out loud. Exposure is the fix."<Company> · <round>. Dimensions: Knowledge, Problem-Solving Process, Implementation, Communication, Composure, scored from the reconstruction. Tag weak spots precisely; this is where prep-plan gets its data.$CRACKED_DIR/plan.md exists, offer to run /prep-plan to fold the drills into the plan.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.
A structured, honest post-mortem after an interview or OA, whether rejected, ghosted, or unsure. It reconstructs what happened round by round, finds the real root causes (knowledge gap, problem-solvin
---name: rejection-reviewdescription: A structured, honest post-mortem after an interview or OA, whether rejected, ghosted, or unsure. It…---# skills/strategy/rejection-review/SKILL.md개요
A structured, honest post-mortem after an interview or OA, whether rejected, ghosted, or unsure. It reconstructs what happened round by round, finds the real root causes (knowledge gap, problem-solving process, communication, time, nerves, or fit), cross-checks them against past cracked sessions for repeating patterns, and turns them into three targeted drills and an updated plan. Use when the user got rejected, failed an interview or OA, wants to debrief an interview, or asks "why do I keep failing interviews".
FAQ
게시자에게서 skills/strategy/rejection-review/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/nishant-Tiwari24/cracked에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.