Sharing What Seekter Learns

Seekter is open source: how /seekter-git ships what your runs learn about ATS forms and job boards, after scanning the diff for your personal details.

Seekter is open source, and its most valuable part is what it has learned: every applicant tracking system quirk and job board behaviour in reference/ was measured in real applications. When your runs find a new one, it can travel back to everyone who uses Seekter.

Two Kinds of Files

	Shareable	Private
What	`.claude/skills/`, `reference/`, `scripts/`, `templates/` and the root docs	`profile/`, `applications/`, `runs/`
Whose	The kit. Works for anyone.	You. Works for nobody else.

Runs edit the left column as they learn: a new trap in a form goes into that system's file in reference/ats/, a new source behaviour into reference/sources/. A run never commits or pushes those edits itself; it tells you what changed and waits.

Shipping It

/seekter-git

Checks there's kit work to ship. If only your private folders changed, there's nothing to send, and it says so. A day that logged eight applications and taught the kit nothing is a normal day.
Reads the diff before describing it.
Scans for your personal details (below).
Branches, never commits straight to main.
Commits one lesson per commit, with a subject that states the finding.
Pushes and opens a pull request. It never merges.

The Leak Scan

.gitignore protects paths, not content. The real risk is your phone number quoted inside a reference note as an example.

So before anything is committed, the diff is scanned against the values in your own profile (your name, every phone format, your email, address, postcode and personal domains), then for any email address, phone number or postcode the profile didn't list.

Identity is a blocker. The passage is rewritten with placeholders (<FIRST_NAME>, <EMAIL>, <PHONE_LOCAL>…) and the lesson is kept. "The phone widget renders the number in spaced national format" teaches just as much without the number.
Geography is a warning. A city named as an example of a form's behaviour can stay, written so it doesn't depend on one language.

The result is reported even when it's clean.

If You Installed With npx

/seekter-git needs a git repository, and npx seekter init doesn't make one: the folder is a plain copy of a release. Your runs still learn and still write to reference/; there's just no branch to commit them to.

Two ways to send a lesson anyway:

Open an issue with the note your run wrote: which file, what changed, what you measured. That is all a maintainer needs.
Switch to a clone. Clone the repository, move your profile/, applications/ and runs/ into it, and bring over what your runs added to reference/ (compare the folders as in Updating Seekter, and copy the new lines, not whole files). From then on /seekter-git works.

Sending It Upstream

If you cloned your own copy, the pull request lands in your repository. To share a lesson with everyone, open a pull request against selfishprimate/seekter.

You don't need a pull request at all. The most valuable thing to send is a measurement: an application system or a job source behaving in a way nobody has written down yet. Open an issue with what you ran and what happened. CONTRIBUTING.md has what belongs where.