0122 files · 164 KB
Agent desk
Give a standing job a plan, SQL memory and enforced limits, so your agent can pick it up tomorrow.
Keep roles, CV versions, applications and follow-ups together, with your approval before applying.
3 files · 20 KB
Why I keep it
A job search has the same problem as a sales pipeline: every opportunity has a next step, but the record can disappear between conversations. I built job-desk around one loop — find, pick, tailor the CV, apply, follow up and record — so the agent can keep that work together on your computer.
The database and CV stay in the local data folder, so the next session can work from the same history. Applications always wait for your approval. The agent can learn your email voice through coached drafts and unchanged approvals, but it never handles passwords, creates accounts or solves access challenges.
I’ve included README.md, SETUP.md and AGENTS.md; the working code is in the public repo. Give SETUP.md to your agent and work through it together, so the desk starts with your CV, your tools and your choices about the roles worth pursuing.
How I use it: Give standing work a desk →3 files · 20 KB
0122 files · 164 KB
Give a standing job a plan, SQL memory and enforced limits, so your agent can pick it up tomorrow.
026 files · 35 KB
Keep companies, deals, calls and promises in one database, with the next decision ready for you.
I’ll send you one build log a week: what I added to the library and what I shipped with it. You can unsubscribe any time.