← Mogi AI Job Application AgentCONTENT HISTORY
WHAT CHANGED
Update to Mogi AI Job Application Agent
Snapshot Oct 24, 2026 · 13:48 UTC · version 1.0.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Mogi AI Job Application Agent and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Walk a Mogi user through setup in chat once their account is active: upload a resume, create a job search, add the first jobs, fill the required application answers, then accept the Terms and go live. Use whenever setup is not complete.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 148
}
],
"name": "mogi-setup",
"skill_md_contents": "---\nname: mogi-setup\ndescription: Walk a Mogi user through setup in chat once their account is active: upload a resume, create a job search, add the first jobs, fill the required application answers, then accept the Terms and go live. Use whenever setup is not complete.\nmetadata:\n short-description: Set up your search and go live\n---\n\n# Finish setup\n\n## Workflow\n\n1. Call `get_onboarding_status`. If `plan_active` is false, explain that setup continues once\n the account is active in the Mogi app (`app_url`), and stop. Otherwise follow `next_steps` in order and say how many are left.\n2. **Resume.** Ask the user to attach their resume (PDF or Word), then call `upload_resume`.\n Formatting takes a minute or two; check with `list_resumes`. When the status is `ready`,\n share `document_link`, and call `approve_resume` only after the user says it looks right.\n3. **Search.** Ask which roles and where (remote, hybrid or on-site; cities or states) and any\n pay floor. Call `preview_new_jobs` once to show a sample. Adjust with the user, then call\n `add_jobs_from_search` with the filters and the ids they liked.\n4. **Answers.** For each item in `missing_answers`, ask the user and save with\n `update_profile`. `referral_source` is how they heard about Mogi. Never guess an answer\n (work authorization, sponsorship, phone).\n5. **Three key terms.** Show the user each of the three `key_acknowledgments`, one per\n message, word for word, and ask for an explicit yes to each before showing the next: AI\n writes their resumes and cover letters and they take responsibility for them; about 20 to\n 30% of applications are a looser fit, at no extra charge; they can pause or cancel any time\n themselves. If they will not agree to one, do not go live; answer their question instead.\n6. **Go live.** Show the user `terms_text` and every other acknowledgment from\n `get_onboarding_status`, word for word, and ask:\n - whether Mogi approves strong matches (`job_auto_approve` `high_fit`) or every match\n (`all`); approving every job by hand is not offered;\n - how their resume is used: Heavy customization (default, recommended, `resume_creativity`\n medium), Light (`low`), or My own file (`custom_resume_opt_in` false). Tailored resumes\n are sent without per-resume approval; say so plainly.\n - whether they want one cover letter that goes with every application (default no).\n Then ask them to type their initials. Call `complete_onboarding` with\n `user_agreed_to_key_terms` and `user_agreed_to_terms` true only after they explicitly agree.\n7. Confirm Mogi is live and offer to review the first jobs (mogi-review-jobs).\n\n## Guardrails\n\n- Going live signs the Terms. Never set `user_agreed_to_key_terms` or `user_agreed_to_terms`\n without the user's explicit yes in this conversation (one yes per key term), and never type\n their initials for them.\n- One question at a time; keep each message short.\n- Use only facts the user gave.\n"
}SHA-256 of public snapshot: cb503fc3deaa0e502704bb6f0208a49a97a0a2ef63d1c14672f3ac09e764e2a5