Skip to content
Back to search

gatepass

MarketplaceWorks with Claude CodeGitHub

Marketplace for Gatepass: get your resume through every hiring gate, with Claude Code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mrinal-aswin--gatepass/badge.svg)](/listings/mrinal-aswin--gatepass)

HTML

<a href="/listings/mrinal-aswin--gatepass"><img src="/api/listings/mrinal-aswin--gatepass/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "gatepass",
  3. "description": "Marketplace for Gatepass: get your resume through every hiring gate, with Claude Code.",
  4. "owner": {
  5. "name": "Mrinal Aswin"
  6. },
  7. "plugins": [
  8. {
  9. "name": "gatepass",
  10. "source": "./",
  11. "description": "Job-search packs built on the hiring funnel: resume, LinkedIn, ATS, reviewer lenses, cover letters, interview prep and a dashboard."
  12. }
  13. ]
  14. }
README.md · README · 342 lines
  1. <sub>Contributing? Run `git config core.hooksPath .githooks` once after cloning, then read [CONTRIBUTING.md](CONTRIBUTING.md).</sub>
  2. # Gatepass
  3. **Get your resume through every hiring gate.** Your job search, run like a project. Give Claude your resume and your LinkedIn profile. About
  4. twenty minutes later you have your **pack**: everything you need to apply, and a dashboard that tells you
  5. what to do next.
  6. It works for your own search, or for a whole team: one pack per person, all in one folder.
  7. **[See the website](https://mrinal-aswin.github.io/gatepass/)** for a tour.
  8. ## What you get
  9. - **A resume that gets through the filters.** One page, built to survive the automatic screening (ATS) that most companies run before a person reads anything. PDF to upload, Word for portals that want it.
  10. - **Resumes for each kind of role.** Applying to frontend *and* backend jobs? You get a resume for each role your experience genuinely supports. Same facts, different emphasis.
  11. - **A resume tailored to one job.** Paste a job ad and get a version reordered for it in seconds, plus an honest list of what the ad asks for that you can't claim.
  12. - **LinkedIn fixes, ready to paste.** A new headline, an About section and experience text, each with the steps to apply it, checked against your resume so the two never disagree.
  13. - **Five reviewers, before the real ones.** A recruiter, a hiring manager, a technical interviewer, an HR/background checker and a domain lead each judge your materials separately, and say what would stop them.
  14. - **Live job research.** Real current listings for your target roles and cities, and the keywords those ads keep asking for.
  15. - **Cover letters.** A main letter and a short version for emails and LinkedIn messages, plus a tailored letter for any job on request.
  16. - **Interview preparation.** A six-week plan, a bank of stories to tell, and a ready-made prompt that turns ChatGPT into a mock interviewer.
  17. - **A dashboard to work from.** Every improvement as a card you can tick off, your scores, your documents, and a weekly tracker that tells you where applications are getting stuck.
  18. **Nothing is made up.** Every line on your resume traces back to your own documents. Where something is
  19. missing, Claude either asks you or marks its best guess so you can confirm it. When your resume or
  20. LinkedIn changes later, it updates only what's affected and keeps everything you've already confirmed. If
  21. a new resume disagrees with something you confirmed, Claude asks which is true instead of overwriting it,
  22. and anything you rejected stays out.
  23. ## How it works
  24. ```mermaid
  25. flowchart TD
  26. A["Resume +<br/>LinkedIn"] --> B["Research +<br/>5 reviewers"]
  27. B --> C["Your pack"]
  28. C --> D["Dashboard"]
  29. D -- "something<br/>changes" --> B
  30. ```
  31. ## Get started
  32. You'll do this once. Setting up takes about ten minutes; your first pack takes about twenty more.
  33. ### Step 1. Get Claude Code
  34. Claude Code is the version of Claude that can work with files on your computer. It needs a paid Claude
  35. plan (Pro, Max, Team or Enterprise) or an Anthropic Console account.
  36. Install it from **[claude.com/claude-code](https://claude.com/claude-code)**. Then open the Terminal app (see
  37. Step 2 for how), type `claude`, press <kbd>Enter</kbd>, and finish signing in in the browser window that
  38. opens. Type `/exit` to close it again when you're done.
  39. ### Step 2. Add this plugin
  40. Open the **Terminal** app:
  41. - **Mac:** press <kbd>Cmd</kbd> + <kbd>Space</kbd>, type `Terminal`, press <kbd>Enter</kbd>.
  42. - **Windows:** open **PowerShell** from the Start menu.
  43. - **Linux:** open your terminal.
  44. Paste these two lines, one at a time, pressing <kbd>Enter</kbd> after each:
  45. ```bash
  46. claude plugin marketplace add mrinal-aswin/gatepass
  47. ```
  48. ```bash
  49. claude plugin install gatepass@gatepass
  50. ```
  51. Each line ends with a green tick and "Successfully added" or "Successfully installed".
  52. ### Step 3. Make a folder for your job search
  53. Your packs live in an ordinary folder. Still in Terminal, paste these three lines:
  54. ```bash
  55. mkdir -p ~/job-search
  56. ```
  57. ```bash
  58. cd ~/job-search
  59. ```
  60. ```bash
  61. claude
  62. ```
  63. On Windows PowerShell, use `mkdir $HOME\job-search` and `cd $HOME\job-search` for the first two lines.
  64. Claude Code starts inside that folder. If it asks whether you trust this folder, choose **Yes**. You're
  65. ready when you see a box to type in.
  66. Next time, just open Terminal and run the last two lines again.
  67. ### Step 4. Let Claude check your computer
  68. Type this to Claude, in plain words:
  69. > Check the gatepass setup and help me install anything that's missing.
  70. It checks for five things (listed under [What it needs](#what-it-needs)) and walks you through
  71. installing any that are missing. When everything is there, it says **Ready**. You can ignore a line that
  72. starts with `note`.
  73. Claude asks before it runs anything on your computer. Read what it wants to do, and choose **Yes** to let
  74. it. On a new Mac, a window may ask to install "command line developer tools": click **Install**.
  75. ### Step 5. Build your first pack
  76. Type:
  77. > Build my job-search pack.
  78. Then **add your resume**: drag the file into the window. In Terminal this pastes the file's location;
  79. press <kbd>Enter</kbd>. PDF, Word or text all work.
  80. Claude asks a few questions, one at a time, usually with buttons to click:
  81. 1. **Whose profile is this?** Yours, or someone else's. For someone else's, Claude checks they know and
  82. agree, because the pack holds their career history.
  83. 2. **Your resume,** if you haven't attached it yet.
  84. 3. **Your LinkedIn profile:** confirm the link, then choose how Claude reads it (see [LinkedIn](#linkedin)).
  85. 4. **The jobs you want:** the titles, cities, and whether you're open to remote work. Claude suggests
  86. these from your resume; just confirm or change them.
  87. 5. **Missing details:** have Claude fill gaps with clearly marked best guesses (recommended), or leave
  88. visible blanks.
  89. Say **"go"** at any point and Claude carries on with what it has.
  90. Then it gets to work. Research and the five reviewers run at the same time, so the first pack takes about
  91. **twenty minutes**. Later updates are much quicker. It's done when Claude says your pack is ready and lists
  92. anything it still needs from you.
  93. ### Step 6. Open your dashboard
  94. Type:
  95. > Start my dashboard.
  96. Claude starts it and gives you a link, usually **http://127.0.0.1:8765**. Open it in your browser. It runs
  97. only on your computer, so keep Terminal open while you use it: closing it stops the dashboard.
  98. Start with **Do next** on the Overview tab, and work down the list.
  99. ## Your dashboard
  100. | Tab | What it's for |
  101. |---|---|
  102. | **Overview** | Where you stand at each stage of hiring, from "can recruiters find me?" to "will I pass the background check?" Plus your **Do next** list and key numbers. |
  103. | **Actions** | Every improvement as a card: why it matters, a link to the exact page, text to copy, and step-by-step help. Mark each one **Resolved** or **Ignored** when you're done. Undo is there if you misclick. |
  104. | **Documents** | Download your resume, cover letters, learning plan and mock-interview prompt as PDF, Word or plain text (Markdown). |
  105. | **Tailor to a job** | Paste a job ad and get a resume tailored to it in seconds. Each one is kept with its ad, so you can tell which version you sent, and it's flagged if your main resume changes later. |
  106. | **Lenses** | What each of the five reviewers thought, and the problems two or more of them agreed on. |
  107. | **ATS** | How well your resume and LinkedIn match the keywords employers search for, and one-click copying of skills to add to LinkedIn. |
  108. | **Funnel** | Each week, log how many applications, replies and interviews you got. It tells you which stage is leaking. |
  109. | **Framework** | The hiring stages explained, and what to do when one is the problem. |
  110. Everything you tick is saved straight away. If you open the dashboard file directly instead of through
  111. Claude, it remembers your clicks in that browser and gives you a button to save them properly later.
  112. The dashboard is a single file with everything inside, including the documents, so you can send it to the
  113. person whose pack it is.
  114. ## What to say to Claude
  115. Plain words work. Some examples:
  116. | You want to... | Say |
  117. |---|---|
  118. | Update your resume | "I have a new resume." *(attach it)* |
  119. | Refresh after editing LinkedIn | "My LinkedIn changed." |
  120. | Check your LinkedIn fixes went live | "I've made the LinkedIn changes." *(Claude re-reads your profile and checks each one)* |
  121. | Apply for a specific job | "Tailor my resume to this job:" *(paste the ad)* |
  122. | Get a cover letter for it | "Write a cover letter for this job." |
  123. | Apply to more than one kind of role | "Which roles does my profile support? Make a resume for each." |
  124. | Answer Claude's open questions | "Here are my answers: I started at my current job in March 2021..." |
  125. | Log a week of applications | "This week: 8 applications, 2 replies, 1 interview." |
  126. | Get a straight opinion | "Review my resume like a recruiter would." |
  127. | Prepare for interviews | "Help me prepare for interviews." |
  128. | Help a colleague | "My teammate Priya wants to prepare for senior backend roles in Bengaluru." |
  129. When something in a pack is out of date, Claude mentions it at the start of your next session and offers
  130. to update it.
  131. ## LinkedIn
  132. Claude reads your profile in one of two ways. You choose when it asks.
  133. - **Through Chrome (recommended).** Install the **Claude in Chrome** extension and sign in to LinkedIn
  134. yourself. Claude reads the profile through your own browser. It never asks for your password and never
  135. clicks anything on your profile.
  136. - **From a PDF.** On your LinkedIn profile, click **More**, then **Save to PDF**, and attach the file to the
  137. chat.
  138. ## Where your files are
  139. Everything stays in the folder you made in Step 3:
  140. ```text
  141. job-search/
  142. └── people/
  143. └── your-name/
  144. ├── inputs/ every resume and LinkedIn copy you've given, dated, never changed
  145. ├── outputs/
  146. │ ├── actions.html your dashboard
  147. │ ├── resume/ your resume (PDF, Word) and the list of details to confirm
  148. │ ├── cover-letters/
  149. │ └── ... reviews, research, learning plan, mock-interview prompt
  150. └── CHANGELOG.md what changed each time Claude updated the pack
  151. ```
  152. You can also drop files into a `raw/` folder next to `people/` instead of adding them in the chat. Claude
  153. files them into the right place and offers to empty `raw/` afterwards.
  154. ## Privacy
  155. A pack holds personal information: contact details, work history, and the decisions you made.
  156. - Everything stays on your computer. The dashboard runs only on your machine.
  157. - Build a pack for someone else only with their agreement.
  158. - Don't upload the `people/` folder anywhere public. *(For developers: if your job-search folder is a git
  159. repository, add `people/` and `raw/` to its `.gitignore`.)*
  160. - This plugin contains no personal data, and its automatic checks refuse any that's added by mistake.
  161. ## What it needs
  162. Five things, all free. Claude checks for them in [Step 4](#step-4-let-claude-check-your-computer) and helps
  163. you install any that are missing.
  164. | Tool | What it does | Mac | Windows / Linux |
  165. |---|---|---|---|
  166. | Python 3.10 or newer | runs the pipeline | usually already there | [python.org](https://www.python.org/downloads/) |
  167. | pandoc | makes the Word documents | `brew install pandoc` | [pandoc.org](https://pandoc.org/installing.html) |
  168. | poppler | reads PDFs the way screening software does | `brew install poppler` | `apt install poppler-utils` |
  169. | Chrome, Chromium or Edge | turns documents into PDFs | [google.com/chrome](https://www.google.com/chrome/) | usually already there |
  170. | SQLite | saves your dashboard clicks | built into Python | built into Python |
  171. The Mac commands use [Homebrew](https://brew.sh); if you don't have it, Claude can install it for you.
  172. It's tested on macOS; Linux should work; Windows is untested.
  173. ## If something goes wrong
  174. <details>
  175. <summary><b>Claude says it can't read my file ("Operation not permitted")</b></summary>
  176. On a Mac, apps need permission to read your Downloads, Desktop and Documents folders. Claude gives you a
  177. one-line command to copy the file somewhere it can read. Paste that command into Terminal, press
  178. <kbd>Enter</kbd>, and tell Claude it's done.
  179. </details>
  180. <details>
  181. <summary><b>Claude can't read my LinkedIn</b></summary>
  182. Check that the Claude in Chrome extension is installed and that its side panel is open in Chrome, signed
  183. in to the same Claude account. If it still can't connect, use **More → Save to PDF** on your profile and
  184. attach the file instead.
  185. </details>
  186. <details>
  187. <summary><b>Claude doesn't seem to know about the plugin</b></summary>
  188. Close Claude Code and open it again; plugins load when it starts. To check that it's installed, run
  189. `claude plugin list` in Terminal and look for `gatepass`.
  190. </details>
  191. <details>
  192. <summary><b>My clicks on the dashboard aren't saved</b></summary>
  193. Open the dashboard through Claude ("Start my dashboard") rather than by double-clicking the file. If you
  194. already made changes in the file version, they're kept in that browser: start the dashboard and use
  195. **Save to database** on the bar at the bottom.
  196. </details>
  197. <details>
  198. <summary><b>The dashboard link doesn't open</b></summary>
  199. The dashboard runs only while Claude Code has it started. Ask Claude to "start my dashboard" again and use
  200. the link it gives you.
  201. </details>
  202. <details>
  203. <summary><b>My resume runs over one page</b></summary>
  204. Ask Claude to "tighten the resume to one page". It shortens bullets rather than shrinking the text. With
  205. twelve or more years of experience, two pages is normal; tell Claude if you'd prefer that.
  206. </details>
  207. <details>
  208. <summary><b>How much does it cost?</b></summary>
  209. The plugin is free. It uses your normal Claude Code allowance. A first pack is the biggest job, because
  210. of the research and the five reviewers; updates use much less.
  211. </details>
  212. ## Update or remove
  213. To get the latest version, run this in Terminal:
  214. ```bash
  215. claude plugin update gatepass@gatepass
  216. ```
  217. To remove it:
  218. ```bash
  219. claude plugin uninstall gatepass@gatepass
  220. ```
  221. Removing the plugin doesn't touch your packs. Your `people/` folder stays exactly as it was. What's new
  222. in each version is in the [changelog](CHANGELOG.md).
  223. ### Coming from resume-pipeline?
  224. Gatepass used to be called resume-pipeline. Version 2.0 changed the name, so the old install can't update
  225. itself. Switch once, in Terminal:
  226. ```bash
  227. claude plugin uninstall resume-pipeline@resume-pipeline
  228. claude plugin marketplace remove resume-pipeline
  229. claude plugin marketplace add mrinal-aswin/gatepass
  230. claude plugin install gatepass@gatepass
  231. ```
  232. Your packs carry over unchanged. If a project's `.claude/settings.json` lists `resume-pipeline@resume-pipeline`
  233. under `enabledPlugins`, change it to `gatepass@gatepass`. If you set `RESUME_PIPELINE_CHROME`, it still works;
  234. the new name is `GATEPASS_CHROME`.
  235. ## Other ways to use it
  236. - **Without the plugin system:** copy `skills/gatepass/` into a project's `.claude/skills/` folder.
  237. To get the start-of-session reminder, also merge `skills/gatepass/assets/session-start-hook.json`
  238. into that project's `.claude/settings.json`.
  239. - **On claude.ai or in the Claude desktop app (experimental):** run `tools/build-skill-zip.sh` and upload
  240. `dist/gatepass.zip` under Settings → Capabilities → Skills. Reviews and writing work there.
  241. Making PDFs needs the tools above, which only Claude Code on your own computer has.
  242. - **Try a copy without installing it:** `claude --plugin-dir /path/to/gatepass`.
  243. ## License
  244. MIT. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.