- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add nishant-Tiwari24/cracked --skill prep-plan -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add nishant-Tiwari24/cracked --skill prep-plan -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add nishant-Tiwari24/cracked --skill prep-plan -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add nishant-Tiwari24/cracked --skill prep-plan -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/nishant-Tiwari24/cracked/tree/HEAD/skills/strategy/prep-planVom Herausgeber
A plan that ignores where the candidate actually is goes in the bin by week two. This one is built from their deadline, their hours, and their real performance data in the cracked journal, and it's rebuilt whenever they come back.
deadline, hours_per_day, target_companies, target_roles, dsa_level, language. Ask for any that are missing (in one round).target_companies (max 3), call the Skill tool with "company-intel". Use the briefs' DSA topic mix to weight the patterns, and their process to schedule company-specific mocks. No target companies? Plan for the target tier.$CRACKED_DIR/journal.md. Normalise the tags first: lowercase, hyphenate, map near-duplicates onto the canonical list in cracked-profile (DP, dynamic-programming and dp → dp-1d or dp-2d by context; edgecases → edge-cases). Then count sessions per skill, collect every weak_spots tag with its frequency and recency, count pattern: fields, and note score trends.$CRACKED_DIR/plan.md if it exists. If it does, this is a review run: go to §3 first.date +%F (or python3 -c "import datetime; print(datetime.date.today())"); never assume it. Total hours = weeks × 7 × hours_per_day × 0.8 (life happens; plan for 80%).Save to $CRACKED_DIR/plan.md:
# Prep plan · <target> · <today> → <deadline>
## Reality check
<2–3 lines: time budget, the gap, the strategy>
## Weekly plan
### Week 1 (<dates>): <theme>
- DSA: <patterns + target problem counts, e.g. "Sliding window + two pointers: 12 problems (4E/6M/2H)">
- Core: <subject topics>
- Projects/Resume: <one concrete deliverable>
- Mock: <which cracked skill to run and when, e.g. "Sat: /mock-interview on arrays (medium)">
- Checkpoint: <a measurable goal to hit by Sunday>
### Week 2 …
## Daily template (<hours>/day)
<a time-boxed routine, e.g. 60 min new pattern · 45 min revision (spaced repetition of old problems) · 30 min core subject · 15 min log>
## Rules
- Weekly: 1 mock (alternating /mock-interview, /oa-sim, /core-viva), 1 /prep-plan review
- Never more than 2 days without revising old problems
Principles:
pattern-coach skill's catalog by calling the Skill tool with "pattern-coach" if you need it). Sequence: arrays/hashing → two pointers/sliding window → binary search → stack → linked list → trees → heaps → graphs → DP → backtracking./roast-my-resume, /make-it-hireable): applications open before interviews.questions.py get "<Company>" --window 3m) as named problems in the weekly lists./resume-blueprint, /jd-match, /oa-sim in that company's style, /hr-round company mode), revision, and no new topics.On track / Behind by ~N days / Ahead, plus the 3 most important observations (e.g. "DP still fails in 3 of 3 mocks", "Communication up from 5 to 8").plan.md. Keep completed weeks as history, marked ✅/🟡/❌.Give the plan's headline and this week's first three actions, each with the exact cracked command to run. There's no scorecard for planning sessions; don't log to the journal.
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.
Build a realistic week-by-week placement / job-prep plan from the candidate's deadline, daily hours, target companies, current level and their actual weak spots from past cracked sessions. Re-running
---name: prep-plandescription: Build a realistic week-by-week placement / job-prep plan from the candidate's deadline, daily hours, target…---# skills/strategy/prep-plan/SKILL.mdÜbersicht
Build a realistic week-by-week placement / job-prep plan from the candidate's deadline, daily hours, target companies, current level and their actual weak spots from past cracked sessions. Re-running it reviews progress and re-plans. Use when the user asks for a prep roadmap, a study plan for placements or interviews, "how should I prepare in N weeks", what to study next, or wants to review their prep progress.
FAQ
Laden Sie skills/strategy/prep-plan/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/nishant-Tiwari24/cracked.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.