Commands

You use Seekter by talking to Claude Code. Six slash commands start the main jobs, and after that you can mostly say what you want in your own words: "Acme rejected me", "apply to these too", "how is my search going?". Claude runs the scripts for you.

Initialize

Initializing sets Seekter up for you: it interviews you, one short question at a time, and writes everything the other commands read. Start it with:

/seekter-init

It asks about forty questions in nine groups: your resume, your contact details, the roles you're after, where you can work and under which visa, your salary bands, your standard answers to form questions, the sectors and companies you won't touch, the facts and stories your answers may draw on, and how you write. Then your search: it shows the job sites and the companies that fit where you live and the work you do, and you keep what you want.

When. Once, before your first run. It starts with the disclaimer and does nothing until you agree to it. It saves after every answered group, so you can stop and pick up where you left off. Run it again to update your profile section by section.

What to say. Answer in your own words, and say "skip" or "later" to anything you'd rather not answer now. Have your resume file ready: it reads it first, so most questions become "Your resume says eight years in this field. Correct?" If you already track applications in Notion, Airtable or Google Sheets, say so, and it imports a CSV export so nothing is applied to twice.

What it writes. profile/profile.md (you), profile/settings.json (your search) and a copy of your resume in profile/documents/. All git-ignored. At the end it lists the answers still missing, the LinkedIn job alerts to create by hand, and the next command.

What it never does. Guess. A value you didn't give stays blank and is asked when a form needs it.

More: Getting Started and Your Profile.

Run

The daily run is the job search itself: one command finds the postings, applies to the ones that fit and tells you what it did. Start it with:

/seekter-run

It searches every source in a fixed order (your links, the job APIs and the career sites you watch, your LinkedIn alert emails, then the other boards), drops what your rules rule out and what you've applied to already, scores each posting from 1 to 5 for fit, checks that it's still open, and fills the application forms in your own Chrome, best fits first. Every application and every skipped posting is written to your tracker, and the run ends with a report.

When. Once each working day, with Chrome open, the Claude in Chrome extension connected and your webmail signed in.

What to say. The command is enough. Before it, paste any postings you found yourself ("apply to these too", followed by the links) or put them in profile/links.txt; they go first, and a link you bring overrides the one-application-per-company hold. During the run you can stop it, ask it to skip a company, or answer the question it's waiting on.

What it writes. One file per application in applications/<month>/, a row per skipped posting in skipped.md, and the day's report in runs/<date>.md: what each source found, what was applied to, what was passed over and why, and the list of LinkedIn Easy Apply postings for you to send, best fit first. Anything only you can do, such as a CAPTCHA or an account to create, is left open in its own tab and listed under Needs you in applications/README.md.

What it never does. Fill LinkedIn Easy Apply, solve a CAPTCHA, create an account, type a password, accept terms for you, send a message or an email as you, or write an answer your profile doesn't support.

More: The Daily Run and Guardrails.

Log

Logging keeps your tracker true after the run: rejections, interviews, offers, applications you sent by hand, hand-offs you finished. Start it with the command, then say what happened:

/seekter-log

When. Whenever something happens, and before /seekter-report, because the report reads your tracker, not your email.

What to say. One sentence is enough:

• "Acme rejected me."
• "I have a call with Globex on Thursday."
• "Got an offer from Initech."
• "I applied to Hooli myself." It checks the tracker first, then records it.
• "I sent the hand-offs." The pending ones become applications.
• "Don't apply to Umbrella again." It records the skip and adds the company to your blacklist.
• "Sweep my inbox." It reads your webmail in Chrome, matches each reply to an application and updates it.

What it writes. The status and a dated note in each application's file, then a fresh applications/README.md.

What it never does. Reply to an email, or decide something a mail asks of you. A mail that needs you, such as a take-home or a scheduling link, is pointed out to you.

More: Tracking Replies.

Prepare

Preparing gets you ready for one interview stage: a screening call, a hiring-manager round, a portfolio review, a take-home, an async video, a final round. Start it with:

/seekter-interview

It reads the posting, what your application said, the company's own site and your story bank, then writes answers that open with how you work and use only your own stories.

When. Once an invitation arrives, and again after the call, to write down how it went.

What to say. "I have a hiring-manager call with Acme on Thursday at 3 pm, 45 minutes, with the design lead." It asks only for what it can't find. After the call: "It went well, they asked about my design system work and I hesitated on pricing."

What it writes. A prep file in profile/interviews/, named for the date, the company and the stage: what to know about them, an answer for each thing the role asks for, "tell me about yourself", likely questions, what to decide before the call, and questions to ask back. Your notes on how it went are added to the same file, and new stories go into your story bank.

What it never does. Invent a story or a number, answer or schedule the invitation, or join the call.

More: Preparing for Interviews.

Report

The report shows how your search is going. Start it with:

/seekter-report

It counts applications sent, replies and interviews, and the same broken down by source, form system, location, title, fit score and resume type, plus the most common reasons postings were skipped and everything still waiting on you.

When. Once a week, after /seekter-log.

What to say. The command, or just ask: "how is my search going?", "what's working this month?".

What it writes. runs/report-<date>.md, and a short version in the chat: a few plain observations with the numbers behind them, and at most two suggested changes to your search.

What it never does. Change anything. It only reads; a suggested change waits for your yes.

More: Reading the Report.

Share

Sharing sends back what your runs taught the kit. Start it with:

/seekter-git

A run that meets a new form trap or a source that behaves differently writes the lesson into reference/; this command puts those edits on a branch, commits them and opens a pull request, so the next release has them for everyone.

When. After a run has changed something under reference/, .claude/skills/, scripts/ or templates/. It needs a clone of the repository; with an npx install, send the lesson as an issue instead.

What to say. The command. It reads the changes, tells you what the scan found, and then ships them.

What it writes. A branch with one commit per lesson, in the repository's own voice, pushed to your repository with a pull request. Merging it stays yours.

What it never does. Commit profile/, applications/ or runs/, or commit anything before it has scanned the changes for your name, email, phone number and address. A value from your profile found in a reference note is rewritten as a placeholder first.

More: Sharing What Seekter Learns.