Don’t install
the take-home yet.

Interview assignments often arrive as a full GitHub repo. The README usually says to run npm install. That can run hidden code on your laptop.

RepoSafety is a Cursor command. It reads the repository first — without installing or running it — and tells you whether to install. You still decide. A clean report is not a promise that the repo is safe.

/interview-repo-safety

The usual first steps are the risky ones.

You get a take-home. You clone it. You install packages. You start the app. Maybe you ask an AI coding assistant to work in the folder. Any of those steps can run code you have not read.

  1. Clone the repo This part is usually fine.
  2. Install packages This can run extra scripts the moment you type it.
  3. Start the app Starting the dev server can load the trap even when install scripts look clean.
  4. Let an AI agent loose in it An assistant that “just installs dependencies” is running the same commands you would.

RepoSafety sits after clone, before install.

Three steps. Then you decide.

  1. 1

    Clone. Stop.

    Copy the take-home to your machine. Do not run npm install, yarn, pnpm, pip, or the README’s “getting started” commands yet.

  2. 2

    Run the command in Cursor

    Open the folder and type /interview-repo-safety in Agent chat. The skill only reads files. It does not install the project to inspect it.

  3. 3

    Read the verdict

    You get one answer: safe to install, review first, or do not install — plus a short report. You choose what happens next.

What the skill actually does

Every row was checked against the public /interview-repo-safety skill. A tick means the skill performs that check. A cross means it does not — even if an older version of this page implied it.

The skill does this

The skill does not do this

This is what it caught on a real take-home.

A coding-interview repo presented as “Proof of Dev.” The README said to run npm install && npm run dev. That was enough to trigger the trap. The skill said do not install before anything ran.

Interview take-home nothing was installed
verdict
DO NOT INSTALL / RUN
confidence
HIGH
what the README asked
npm install && npm run dev
odd package
animatecss-tailwind-adapter — not needed for a wallet / scoring take-home
hidden package
@aaron205whitmore/postcss-animate-utils
what that package does
Talks to 153.75.81.2 and runs the response as code. Do not open that address.
secret in the repo
npm token in .npmrc (value hidden)
Git hooks
Clean. The trap is the install / start path, not a hook.
extra scanners
Sonatype and Opsera were not available on this run

In plain English

The assignment did not need an animation plugin. That plugin pulled in a second package. The second package calls a raw IP address and runs whatever comes back. Following the README is enough.

If you already ran it

Treat that machine as compromised. The skill cannot undo an install that already happened. Do not run this project in the sandbox either — the verdict was do not install.

Read the full report →

Install the skill, then run it on the take-home.

This is a Cursor skill (it also works in Claude Code). It is not a website you paste a GitHub link into.

git clone https://github.com/naval200/interview-repo-safety.git
cd interview-repo-safety
mkdir -p ~/.cursor/skills
ln -s "$(pwd)/skills/interview-repo-safety" ~/.cursor/skills/interview-repo-safety
  1. 1

    Restart Agent chat

    So Cursor picks up the new skill.

  2. 2

    Clone the take-home. Do not install.

    Open that folder in Cursor.

  3. 3

    Run /interview-repo-safety

    Read the verdict before you follow the README.

Docker is only needed later, if you ask to install inside the sandbox. Other agents can use npx skills add naval200/interview-repo-safety.

Before you run npm install, run this.

/interview-repo-safety — then you decide.