job-workspace
Skill139 starsChanged 4 months agoMITView on GitHub
Open the local Job Apply Companion to manage jobs, applicant facts, resumes, and answers.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-workflowsSkill
- account-setupSkill
- answer-memorySkill
- application-setupSkill
- job-applySkill
- job-preferencesSkill
- job-searchSkill
- job-title-discoverySkill
- saved-jobsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Start the optional local Companion only when the user asks to open it.
- Distinctive: line 24
Leave the process attached while the user works.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Job Workspace
Start the optional local Companion only when the user asks to open it. It is still under development. Core setup, resume review, and application work use the plugin skills and Store CLI. For first use or a handoff between Companion and an agent, read the shared workflow map.
Launch
Requires Node.js 22 or newer in the host's launch environment on macOS arm64 or Linux x64. The packaged native lock is an addon, not a bundled Node interpreter.
- Resolve
<plugin-root>safely. In Codex, use the installed skill path and walk up fromskills/job-workspace/SKILL.md; usePLUGIN_ROOTonly after confirming it containsapps/companion/launch.mjsand the host's packaged native lock. In Claude Code, useCLAUDE_PLUGIN_ROOTafter the same checks. The launcher assembles a missing standalone build on first use, so the installed build need not exist yet. Run exactly:
node "<plugin-root>/apps/companion/launch.mjs"- Leave the process attached while the user works. Open the complete private URL printed locally. Ctrl-C stops the launcher.
The launcher chooses a free port, binds only to 127.0.0.1, prints the local URL, and uses the canonical native Store runtime. The browser never reads or writes Store files directly. A source-only marketplace installation prepares its standalone Companion on first launch using the pinned npm lockfile; this needs npm and package-registry access once per refresh. Applicant data stays local; the workspace needs no account, telemetry, separate database, or Python runtime.
Boundaries and completion
The workspace uses the same canonical Store contract as the native command router; it owns no separate applicant database. Never expose its localhost service on another host or copy the printed fragment token into chat or logs. If startup fails before printing a URL, report the startup failure and consult the Store upgrade and recovery guide.
Confirm the launcher is serving before reporting the workspace ready. Keep the process attached while the user works; Ctrl-C stops it cleanly. Do not restart a healthy workspace merely to explain a feature.
The UI queues work for the next active Job Apply agent and does not start or launch an agent. It cannot extract facts, complete or fail a request, or author a proposal. It lets the owner review, edit, and confirm facts already extracted for an individual resume. It never performs final application submission.
For title discovery, open Facts → Search preferences → Discover related titles. Companion copies a $job-apply:job-title-discovery or /job-apply:job-title-discovery invocation with only owner-entered criteria. Run that skill in the matching host and paste its version 1 JSON packet into Companion. The skill researches visible sources and reports logged-out, blocked, unavailable, or empty sources honestly. Companion validates the packet and shows saved titles, suggestions, evidence, and the exact selected set. Cancel, an invalid packet, or source retry makes no preference write. Confirming saves only approved targetTitles through the canonical revision-checked profile API; if the revision changed, reload and review before retrying. Job Preferences owns direct chat preference changes, and Job Search reads saved titles for opportunity search.
For Jobs, Facts, Resumes, Answers, extraction requests, Activity, Needs Attention, Trash, or recovery details, read workspace behavior only when that surface is relevant. Preserve drafts on revision conflicts and never automatically repair or downgrade the Store.
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.

