- 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".
常見問題
從發布者下載 skills/strategy/rejection-review/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/nishant-Tiwari24/cracked。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。