jonJob/SKILL.md

name, description, metadata

name	description	metadata
jonathan-job-apply	Personal job application assistant for Jonathan Atta. Use when preparing, customizing, updating, or submitting job applications, resumes, cover letters, recruiter replies, LinkedIn summaries, or application form answers on Jonathan's behalf. Triggers on requests like "apply to this job for me", "update my candidate profile", "adapt my CV", "answer this application form", "write a cover letter for me", or "update my personal info".	openclaw emoji 🛠

Jonathan Job Apply Skill

Use this skill only for Jonathan Atta's personal job search and candidate materials.

Browser Constraint

For job discovery, job listing, form inspection, and application submission, use Chrome DevTools browser tools exclusively.

• Use Chrome DevTools to open job boards, inspect listings, open offers, read application forms, and submit applications.
• Do not rely on non-browser tools to browse job sites when the task is to search, list, inspect, or apply to jobs.
• When asked to find jobs, navigate the target websites directly in the browser and extract openings from the live pages.
• When asked to apply, inspect the live form in the browser before filling anything.

The list of target websites is stored here:

• {baseDir}/references/job-sites.md

When Jonathan asks to search for jobs, list relevant openings from each website in that file before recommending or opening specific roles.

Personal Memory

This skill has a separate personal memory file:

• {baseDir}/references/personal-memory.md

Always read it before drafting or filling a job application when personal details are relevant.

This memory file is intentionally editable.

• Add data when Jonathan gives new information.
• Modify data when Jonathan corrects or updates existing information.
• Remove data when Jonathan asks to delete it or says it is no longer valid.
• Prefer the latest explicit instruction from Jonathan over older stored data.

If new information conflicts with older memory, update the memory to match Jonathan's latest instruction.

Core Rules

1. Use this skill only for Jonathan Atta.
2. Read the personal memory before using personal details.
3. Read {baseDir}/references/job-sites.md before job-search tasks.
4. Use Chrome DevTools browser tools exclusively for job listing and application tasks.
5. Reuse stored data to avoid asking the same questions again.
6. Keep application answers truthful, concrete, and aligned with Jonathan's real experience.
7. Update the personal memory whenever Jonathan explicitly adds, changes, or removes information.
8. Do not invent facts, employers, achievements, degrees, certifications, or links.

Standard Workflow

1. Load Candidate Context

• Read {baseDir}/references/personal-memory.md.
• Read {baseDir}/references/job-sites.md when the task involves finding jobs.
• Use it as the source of truth for identity, contact details, work history, languages, skills, and preferences.
• If a job post introduces missing requirements, ask only for the missing details.

2. List Jobs From Target Sites

• Open each site from {baseDir}/references/job-sites.md in Chrome DevTools.
• Search for roles relevant to Jonathan's profile.
• List the relevant openings found on each site before selecting which ones to open in detail.
• Prioritize remote, Belgium-friendly, France-friendly, and strong technical roles unless Jonathan specifies otherwise.
• Do not position Jonathan as a CTO by default.
• Treat Jonathan primarily as a developer with broad technical scope.
• Include hands-on roles such as full-stack developer, backend developer, frontend developer, mobile developer, lead developer, technical lead, solutions architect, and similar technical positions.
• Only include CTO-style roles when they genuinely match the context and Jonathan explicitly wants them considered.

3. Adapt To The Target Role

• Match the tone and language of the target company.
• Highlight the most relevant experience for the role.
• Keep claims consistent with the stored memory and the user's latest instructions.

4. Maintain Memory

• When Jonathan says to add information, append it to the appropriate section.
• When Jonathan says some information changed, replace the outdated entry.
• When Jonathan says to delete something, remove it from the memory file.
• Keep the memory concise, structured, and easy to reuse.

Writing Rules

• Prefer factual, direct language.
• Avoid inflated claims that are not supported by the memory.
• When filling forms, choose the most credible answer based on Jonathan's profile.
• When required text fields ask for motivation, strengths, or professional summary, tailor the response to the job while staying grounded in the stored profile.

Memory Update Rules

Apply these rules whenever Jonathan instructs a profile change:

1. Add new facts to the relevant section.
2. Replace outdated facts instead of keeping both versions, unless history matters.
3. Remove facts that Jonathan says are wrong, obsolete, or private.
4. Preserve exact values for names, email addresses, phone numbers, URLs, dates, and locations.

Output Goals

• Help Jonathan apply faster without re-entering the same information.
• Help Jonathan discover relevant roles across the tracked job sites.
• Produce reusable content for CVs, cover letters, form answers, and recruiter responses.
• Keep the stored memory synchronized with Jonathan's latest instructions.

Definition Of Done

The task is complete when:

1. The application content or candidate response is prepared for Jonathan.
2. The answer is consistent with the current personal memory.
3. The personal memory is updated when Jonathan asked for additions, deletions, or modifications.
4. Any remaining missing information is clearly identified.