- 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 oa-sim -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nishant-Tiwari24/cracked --skill oa-sim -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 oa-sim -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nishant-Tiwari24/cracked --skill oa-sim -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/oa-simFrom the publisher
A realistic online assessment, run from files on disk: the candidate solves in their own editor, and you grade with hidden test cases you execute, just like the real platforms.
questions.py get "<Company>" --window 6m --format json --limit 60. Favour high-frequency problems from the recent windows, then match the brief's difficulty mix. Skip problems already in journal.md. If the brief doesn't describe the OA, use its archetype's preset below.These are generic archetypes, not any specific company's real test. Say so once.
Create two folders for session id <YYYY-MM-DD-HHMM>:
$CRACKED_DIR/oa/<id>/, the only folder you tell them about$CRACKED_DIR/oa/.sessions/<id>/, outside the candidate folder, which holds everything hiddenIn the candidate folder, write:
README.md: the rules, the time limit, the section list, and how to submit ("say submit in the chat when done").qN:
qN.md: the full statement, input/output format via stdin/stdout, constraints, and 2 sample cases. Write it in the style of a real OA: a short story wrapper, precise constraints. For problems taken from the company list, write the statement in your own words (don't copy LeetCode's text), and don't reveal the title or link until the debrief, so the solution can't be looked up mid-test.qN.<ext>: a starter file in the profile language that reads stdin and writes stdout, with a solve function stub.qN/: 10–15 hidden test cases as NN.in / NN.out pairs. Include the samples, edge cases, and at least 2 large cases that time out a brute force. Generate the large cases with a small script, and compute every expected output with your own reference solution, executed. Never hand-write expected outputs for non-trivial cases. Keep the reference solution in the grader folder as qN/ref.<ext>, and a brute force (qN/brute.<ext>) where feasible, cross-checked as in RUNNER.md § Differential testing.mcq.md with numbered questions and options A–D, plus an answer-sheet template answers.txt (1: , 2: , …). Keep the key in the grader folder as mcq-key.txt. Compute every numerical answer (aptitude, probability, time and work, page faults, subnetting) with Python and store the working next to the key. Drop any question whose answer you can't verify by computation or a definition you're certain of.Verify before starting: run each reference solution against its own sample cases and confirm they match qN.md. Fix any mismatch before the candidate sees the test.
Tell the candidate only the candidate folder. If they ask where the tests are: "They're stored separately so the test stays fair. Looking at them would only cheat yourself."
date +%s (or the fallback in RUNNER.md § Clock).Q1 Two-Pointer Inventory 12/12 AC 100
Q2 Grid Delivery Routes 8/12 (2 WA, 2 TLE) 67
Q3 Interval Scheduler 0/12 (CE) 0
MCQ 24/30 80
Likely shortlisted, Borderline or Unlikely, with the one-line reason, and label it: "heuristic, not this company's real cutoff".For each problem: its original title and LeetCode link (in company mode, noting that it's "frequently reported for "), what the failing hidden cases had in common (e.g. "all TLE cases have n = 10⁵: your O(n²) loop"), the intended approach, and the clean reference solution. Show failing inputs only if they're small.
Then produce the scorecard by calling the Skill tool with "cracked-profile". Dimensions: Correctness, Efficiency, Edge Cases, Time Management, plus Aptitude if the test had MCQs. Tag weak spots by pattern.
mock-interview style hand-tracing. Don't pretend to have run tests.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.
Simulate a timed online assessment (OA / coding test) like the ones used in campus placements and off-campus hiring. It generates a full test with coding problems (and optional aptitude/MCQ sections)
---name: oa-simdescription: Simulate a timed online assessment (OA / coding test) like the ones used in campus placements and off-campus…---# skills/interview/oa-sim/SKILL.mdOverview
Simulate a timed online assessment (OA / coding test) like the ones used in campus placements and off-campus hiring. It generates a full test with coding problems (and optional aptitude/MCQ sections) as real files, the candidate solves them in their editor, then the agent runs hidden test cases and reports a cutoff verdict. Use when the user wants an OA, online test, coding round practice, HackerRank/CodeSignal-style test, or a placement test simulation.
FAQ
Download skills/interview/oa-sim/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.