job-application-assistant

Files (1)

• SKILL.md

SKILL.md (first lines)

# Job Application Assistant

Help the user complete the visible form or pasted application questions from the selected text, the visible page, or what they describe. Work only from the job description and the user's own background; never invent personal facts — employment history, metrics, authorization status, salary expectations, demographics, or availability — and never guess at structured or sensitive answers. Draft so the user can review and copy each answer; never click submit, pay, consent, create an account, or upload a file until the user explicitly asks after reviewing the final values. Adapted from [santifer/career-ops](https://github.com/santifer/career-ops/tree/main) `apply` mode.

1. Identify the company and role from the visible page. If the form looks like a different company or role than the user's context, stop and confirm before drafting.
2. Check whether the posting still looks active. If it says expired, closed, no longer accepting applications, or only shows a generic careers shell, say so before drafting.
3. List every visible field with its type, required status, character or word limit, visible options, and whether the answer needs user confirmation. If the form continues below the fold, ask the user to scroll or paste the rest.
4. Draft copy-paste-ready responses for free-text questions, answering the doubt behind each one directly — motivation, stack fit, logistics, salary, work authorization, availability, seniority, or communication style — using real details from the posting and the user's background.
5. Never guess on dropdowns, radio buttons, checkboxes, or legal, demographic, work-authorization, visa, sponsorship, relocation, salary, background-check, disability, veteran, or self-identification questions. If the answer isn't explicitly provided, write the exact confirmation question to ask the user.
6. Practice disclosure discipline: answer logistics and screening questions truthfully when the form asks, but don't volunteer sensitive or HR-only details inside unrelated motivation or fit answers.

Return concise headings: **Application context**, **Field map**, **Draft responses**, **Needs confirmation**, and **Review before submitting**. For each draft, use the exact form question as the heading and put the answer in a blockquote so the user can copy it. Keep every answer specific, honest, and tied to a real detail from the posting or the user's background.

## Example

Form on screen (excerpt) + a note:

> **Apply — Backend Engineer, Northwind.** Fields: "Why do you want to work here?" (free text, 500 char), "Years of Python experience" (dropdown: 0-1 / 2-4 / 5+), "Are you authorized to work in the US?" (yes / no). My note: 3 years of Python at Acme, built their billing service.

Output:

> **Field map**
>
> - Why do you want to work here? — free text, 500 char, draft below.
> - Years of Python experience — dropdown, **needs confirmation** (your note says 3 years → "2-4", confirm).
> - Authorized to work in the US? — yes/no, **needs confirmation**, not provided.
>
> **Draft responses**
>
> **Why do you want to work here?**
>
> > Northwind's billing-heavy backend is exactly where I've spent the last three years — I built and owned Acme's billing service in Python, and I'd like to bring that depth to your team.
>
> **Needs confirmation**
>
> - Python dropdown: select "2-4"? (Your 3 years falls in that band.)
> - Work authorization: I won't answer this for you — what should it say?
>
> _I'll pause before anything is submitted — review the values above first._

From surfmind-space/awesome-surfmind, MIT.

More from surfmind-space/awesome-surfmind