update-status
Skill1 starsChanged 5 months agoMITView on GitHub
Use when the user reports progress on a role and wants the board updated. Triggers: /update-status, "move X to tech interview", "I got an HR screen with Y", "Z rejected me", "got an offer from W", "schedule my interview with V". Moves a vacancy through the pipeline, appends a timestamped statusDetail (preserving history), optionally adds a schedule event, honors pipeline-lock rules, and — when an interview is being scheduled — offers to generate interview prep notes.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Mahashwetha/Job-search-email-system-claudetheir own version, first seen Nov 5, 2026
- Rishabh-Choudhry/anchor-memorytheir own version, first seen Oct 15, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Mahashwetha/Job-search-email-system-claude★ 12same name
- Rishabh-Choudhry/anchor-memory★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-sourceSkill
- add-vacancySkill
- build-profileSkill
- cover-letterSkill
- ingest-cvSkill
- interview-prepSkill
- recheck-statusesSkill
- refresh-listingsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Use today's real date (check the environment date).
- Very specific: line 49
If yes, run /interview-prep <id> [eventId] and persist the brief on that event (events[].prep).
- Very specific: line 59
If scripts/serve.py is running and the board is open in a browser, the viewer auto-loads the new data on next change.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
update-status
Reflect a real conversation/outcome on the board. Edits one vacancy in
data/vacancies.json (the v2 envelope's vacancies[]).
Steps
- Identify the vacancy — by id, or company/role match. If ambiguous, ask.
- Set
statusto the new stage:to_apply·applied·hr_screen·tech_interview·final·offer·rejected·closed·watch·disliked. Append to
statusDetail— never overwrite. Prepend a dated line and keep the prior text:2026-06-09 · HR screen booked for the 12th (recruiter: friendly, comp TBD). <previous statusDetail…>Use today's real date (check the environment date).
statusDetailmay contain light formatting (<b>,<a href>, …) — the viewer sanitizes it.- Schedule event (optional) — if the update involves a meeting/deadline, add an entry to
events[]:{id, kind, at (ISO YYYY-MM-DDTHH:MM), durationMin?, title?, via?, meetingUrl?}.kind∈ interview · take_home_due · follow_up · offer_deadline · other.
Pipeline-lock rule (sacred)
A real pipeline status — applied, hr_screen, tech_interview, final, offer,
rejected — reflects a real conversation. Never silently downgrade it (e.g. a dead posting
doesn't turn tech_interview into closed). Only move it on the user's explicit say-so.
Interview-prep prompt (the important bit)
When this update schedules an interview — i.e. you're adding an interview-kind event, or
moving the role into hr_screen / tech_interview / final — ask the user:
"Want me to prepare interview prep notes for this? I'll research the company and build a brief tailored to your profile and the JD."
If yes, run /interview-prep <id> [eventId] and persist the brief on that event
(events[].prep). If no, just save the status change.
Finish
python3 scripts/validate.py
python3 scripts/build.py --real # refresh the gitignored file:// snapshotIf scripts/serve.py is running and the board is open in a browser, the viewer auto-loads the
new data on next change; a stale open page that tries to save will get a 409 and offer to reload.
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
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.

