- 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 hr-round -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nishant-Tiwari24/cracked --skill hr-round -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 hr-round -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nishant-Tiwari24/cracked --skill hr-round -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/hr-roundFrom the publisher
Most technical candidates lose HR rounds through vagueness, not through wrong answers. Your job: turn their real experiences into crisp, specific, honest stories they can reuse across dozens of questions.
$CRACKED_DIR/stories.md if it exists, since those stories are reusable.Ask the question as an interviewer would, then wait. If they want, they can answer as if speaking. Tell them to aim for 60–120 seconds, which is about 150–250 words.
After each answer, give feedback in this shape:
Score: 6/10
✔ <what worked: one line>
✘ <the biggest problem: one line>
STAR check: Situation ✔ · Task ✘ · Action ✔ · Result ✘ (no outcome or number)
Length: ~320 words, about 2.5 min. Cut by a third.
Red flag: <only if present, e.g. blaming a teammate, "my weakness is perfectionism", badmouthing a past employer>
Then a rewritten answer:
[result: e.g. reduced build time from X to Y] as a placeholder. Never invent outcomes.Offer a retry ("Want to try it again out loud?") before moving on. In a full round, keep momentum: one retry max per question.
The real deliverable. After the session, update $CRACKED_DIR/stories.md: each polished story is saved once and mapped to every question type it can answer:
## Story: <short name>
Answers: conflict, teamwork, pressure, leadership
Situation: …
Task: …
Action: …
Result: …
Numbers: …
Five to seven strong stories cover about 90% of behavioral questions. Tell them which categories are still uncovered.
Call the Skill tool with "cracked-profile" and log a scorecard. Dimensions: Structure (STAR), Specificity, Concision, Authenticity, Confidence. Weak-spot tags include star-structure, vague-results, too-long, cliches.
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.
Practise HR and behavioral interview rounds ("tell me about yourself", "why this company", strengths/weaknesses, conflict, failure, leadership, gaps, salary expectations). The agent asks one question
---name: hr-rounddescription: Practise HR and behavioral interview rounds ("tell me about yourself", "why this company"…---# skills/interview/hr-round/SKILL.mdOverview
Practise HR and behavioral interview rounds ("tell me about yourself", "why this company", strengths/weaknesses, conflict, failure, leadership, gaps, salary expectations). The agent asks one question at a time, scores each answer on STAR structure, specificity and length, rewrites it in the candidate's own voice using their real facts, and builds a reusable story bank. Use when the user wants HR round prep, behavioral interview practice, managerial round prep, or help answering a specific HR question.
FAQ
Download skills/interview/hr-round/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.