← Employed by Guaq AICONTENT HISTORY
WHAT CHANGED
Update to Employed by Guaq AI
Snapshot Oct 28, 2026 · 13:12 UTC · version 1.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Employed by Guaq AI 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": "Track the jobs the user saved or applied to in their Employed by Guaq AI tracker (the web app's Saved tab), update statuses, and review progress. Use when the user says \"save these\", \"track my applications\", \"I applied to\", \"I got an interview\", \"what did I apply to\", \"remind me to follow up\", or wants a shortlist exported as a table or CSV.",
"included_files": [],
"name": "application-tracker",
"skill_md_contents": "---\nname: application-tracker\ndescription: Track the jobs the user saved or applied to in their Employed by Guaq AI tracker (the web app's Saved tab), update statuses, and review progress. Use when the user says \"save these\", \"track my applications\", \"I applied to\", \"I got an interview\", \"what did I apply to\", \"remind me to follow up\", or wants a shortlist exported as a table or CSV.\nlicense: MIT\nmetadata:\n author: Guaq AI\n version: \"1.2.0\"\n---\n\n# Application tracker\n\nThe tracker lives in the user's Employed account, so it is the same list they see on the Saved tab at https://jobs.guaqai.me, on any device. This skill never submits applications.\n\n## Tools\n\n- `list_my_applications`: every tracked role with status, notes and history.\n- `track_job`: save a role (`status: saved`) or record progress: `applied`, `oa`, `phone_screen`, `technical_interview`, `behavioral_interview`, `onsite`, `offer`, `rejected`, `withdrawn`, `ghosted`, `not_applied`. Optional `remarks`. Each change is added to the history, so earlier notes are kept.\n- `untrack_job`: remove a role and its history. Only when the user asks.\n\n## Workflows\n\n- **Save results**: take the rows the user picked from a search or their feed and call `track_job` with each posting `id`. Confirm what was saved.\n- **Update**: \"I applied to the Stripe role\", \"I have an onsite with Wise on Friday\": find the row with `list_my_applications`, say the change, then call `track_job` with the new status and the user's words as `remarks`.\n- **Check still live**: for each `saved` or `applied` row, call `get_job` with the `job_id`; if the posting is gone, tell the user and offer to mark it `withdrawn` or remove it.\n- **Review**: summarise counts by status, list roles waiting on a reply the longest, and suggest follow-ups the user can send themselves. Do not send messages for them.\n- **Export**: a Markdown table in chat, or a CSV written only to a path the user approves.\n\n## Rules\n\n- Record only what the user said or the results contain. Do not invent contacts, deadlines or interview dates.\n- Keep the user's notes verbatim in `remarks`.\n- Ask before removing anything. A status change is reversible; `untrack_job` deletes the history.\n"
}SHA-256 of public snapshot: 3f08b0e2651241713be5d07d294062e48b1fd2511976472d9c516992e2fd2adc