AI Agent Workflow Collection

Apply to WaterlooWorks Full-Cycle Service jobs from a valid WaterlooWorks job ID using the user's logged-in Chrome session. Use when the user asks Claude to apply on WaterlooWorks by job id and provides or can provide both the job ID and the resume/application document label to use. Handles recoverable WaterlooWorks logged-out states by invoking ww-login; handles required Cover Letter documents by invoking ww-upload-cover-letter against coverletter/Company-coverletter.pdf (generating it with ww-write-cover-letter if needed); still stops for required Other - Per Job Posting. If the posting says applicants must apply directly to the employer, still apply through WaterlooWorks and return the employer application link in chat.

Restore a WaterlooWorks Chrome session when Claude is viewing or applying to WaterlooWorks jobs and lands on recoverable logged-out states such as notLoggedIn.htm, WaterlooWorks - Not Logged In, the WaterlooWorks home page, or waterloo.htm?action=login. Use before asking the user to log in; stop and ask only when username/password, Duo/MFA, CAPTCHA, or another credential prompt is required.

Scrape WaterlooWorks co-op job descriptions into a folder under this repository's jds/ directory as individual Markdown files. Use when the user asks to collect, scrape, export, or save WaterlooWorks jobs/JDs and wants Markdown files matching the existing cycle1 format. Defaults to the WaterlooWorks "For my program" / "My Program" filter when the user does not specify a filter, but supports any user-requested WaterlooWorks filter or search. Defaults the output folder to today's date (e.g. jds/2026-6-26) unless the user names a specific folder or cycle.

Initialize this project by making sure every external tool the skills in .claude/skills need is actually installed. Use this whenever the user wants to set up, bootstrap, init, or onboard the project, or asks "are the tools/dependencies installed?", "will the skills run on this machine?", "set this repo up", or after cloning/pulling on a fresh machine. Scans the skills for their real dependencies (language runtimes, third-party Python/npm packages, command-line tools the skills shell out to like poppler, and MCP servers), checks each, auto-installs the safe ones, asks before heavy/system installs, and hands off anything that only the user can connect (like an MCP server).

Upload a PDF cover letter from the coverletter/ folder (typically coverletter/Company-coverletter.pdf produced by ww-write-cover-letter) into a required WaterlooWorks Cover Letter document slot during the Full-Cycle Service Submit Application workflow. Use when a WaterlooWorks application package requires Cover Letter, especially when called from ww-apply-to-job; do not use for resumes, grade reports, work histories, or Other - Per Job Posting documents.

Create a tailored, one-page cover letter PDF named -coverletter.pdf in the coverletter/ folder, generated from a job description and one of the user's résumés and styled like their sample letter (Times font, centered bold name, address-left/links-right header). Use this whenever the user wants to write, draft, generate, or make a cover letter for a specific job, company, or posting — e.g. "write a cover letter for job 475135", "make a coverletter for the Jaza Energy role using ai.pdf", "draft a cover letter for this JD". This is distinct from ww-upload-cover-letter, which only uploads an already-made PDF into WaterlooWorks; this skill GENERATES the PDF (hand the result to ww-upload-cover-letter afterward if applying). Header details (name, address, phone, email, LinkedIn, GitHub) live in coverletter-config.json in the current folder — if it is missing, ask the user for them and create it before generating.