agentleFS
Sign inStart free
nishant-Tiwari24nishant-Tiwari24/cracked/skills/core/setup-cracked/SKILL.md

setup-cracked

Skill5 starsChanged 8 days agoMITView on GitHub

One-time setup for cracked. Creates your prep profile, builds briefs for your target companies, and suggests your first three sessions. Run once before using the other skills, and again whenever your targets change.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call the Skill tool with "cracked-profile".

    line 11
  2. Distinctive:

    Check the environment once and report it in a short table:

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup cracked

Get the candidate from zero to their first useful session in about two minutes.

  1. Call the Skill tool with "cracked-profile". Let it infer what it can, then ask its single round of questions. If a profile already exists, show it and ask what changed.
  2. For each company in target_companies (max 3), call the Skill tool with "company-intel". Skip this if they have no specific companies.

  3. Check the environment once and report it in a short table:

    • python3 available (needed for company questions, OA grading and the portable timeout runner)
    • the profile language's toolchain: g++/clang++ (C++), javac and java (Java), node (JavaScript), go (Go), python3 (Python). Without it, /oa-sim and /mock-interview fall back to hand-tracing, so say so.
    • timeout or gtimeout (optional: the Python runner in skills/interview/oa-sim/RUNNER.md replaces it, which matters on macOS and Windows)
    • on Windows: note that date +%s and mktemp aren't available. The skills use the Python fallbacks in RUNNER.md.
    • sqlite3 or Python's sqlite3 module (for SQL in /core-viva)
    • gh installed and authenticated (for /github-glowup)
    • a text-to-speech command (say, spd-say or espeak) and the agent's voice dictation, for voice mode in /mock-interview

    Missing tools are fine. Just say which skills lose which feature.

  4. Recommend the first three sessions for their situation, e.g. /roast-my-resume → /mock-interview <company> → /prep-plan. Then stop and let them pick.

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free