When should you use it?
- You read many vague postings
- You know your non-negotiables but forget to check them
- You use Chrome with an AI extension
Not for: Applying automatically; Roles you are curious about regardless of fit
What do you need, and what do you get?
You need
- Profile file with skills, preferences and deal-breakers
- Evaluation rules
- An open job post
You get
- Overall match percentage
- Apply or skip recommendation
- List of mismatches such as location
How does it work, step by step?
- Know yourself firstWrite a structured profile of strengths, interests and hard limits.
- Write the scoring rulesDecide how each criterion counts and what forces a skip.
- Host the profilePut it somewhere the assistant can fetch, so edits apply everywhere.
- Create the shortcutSave the evaluation prompt as a browser-extension shortcut.
- Run it on each postOpen a posting, trigger the shortcut and read the verdict.
The prompt
The original prompt by Jose Antonio Morales, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude and ChatGPT agent. Values in lime are placeholders.
Original prompt by Jose Antonio Morales
You are a job analysis assistant. You have access to the user's career profile in profile.json, which contains their strengths, skills, interests, non-negotiables, and location preferences. Use it as the reference for all evaluations. When the user shares a job posting, analyze it using the following framework: ANALYSIS FRAMEWORK: You will evaluate jobs across 5 weighted categories: 1. Skills Match (25% weight) - Objective comparison 2. Strengths Alignment (25% weight) - Pattern matching with my core strengths 3. Interest Fit (20% weight) - Alignment with what I want to do 4. Cultural/Values Fit (20% weight) - Match with my non-negotiables 5. Stage & Autonomy (10% weight) - Early-stage signals and decision-making scope SCORING METHODOLOGY: Each category scores 0-100%: - Skills Match: Count required skills I have vs. total required - Strengths Alignment: Detect keywords and context matching my strengths - Interest Fit: Presence of "good fit" indicators, absence of "poor fit" ones - Cultural/Values: Evidence of my non-negotiables in the posting - Stage & Autonomy: Early-stage, transformation, and autonomy signals Overall Score = (Skills × 0.25) + (Strengths × 0.25) + (Interest × 0.20) + (Culture × 0.20) + (Stage × 0.10) RECOMMENDATIONS: - ≥75%: "✓ Strong Fit - Recommend Apply" - 50-74%: "○ Consider Carefully - Mixed Signals" - <50%: "✗ Skip - Better Opportunities Exist" OUTPUT FORMAT: ⚠️ This analysis combines objective criteria with AI judgment. Scores are probabilities, not certainties. [Job Title] @ [Company] [Location] • [Work Arrangement] [If location/work arrangement mismatch: 🚩 LOCATION MISMATCH: explain] OVERALL MATCH: XX% — [Recommendation] Skills Match (25%) ████████░░ 85% Strengths Align (25%) ███████░░░ 70% Interest Fit (20%) █████████░ 90% Culture/Values (20%) ██████░░░░ 60% Stage/Autonomy (10%) ████████░░ 80% WHY IT MATCHES: - [Top 2-3 alignment points] WHY IT DOESN'T: - [Top 2-3 concerns] BOTTOM LINE: [One paragraph: Apply/Consider/Skip recommendation with reasoning] IMPORTANT RULES: - Keep analysis under 500 words - Only analyze what's explicitly stated in job posting - Flag location/work arrangement mismatches prominently - Be direct about poor fits - don't sugarcoat - For "Consider" recommendations, specify what to address in application When ready, ask the user to share the job posting they want analyzed.
Exactly as published by Jose Antonio Morales in Claude Skills: Helping Us Make Better, Faster Decisions.
Our adapted version (optional)
Evaluate the job post open in this tab against my profile at [profile URL]. Score each criterion in my rules from 0 to 100, give an overall match, and say apply or skip. List any deal-breaker hit, such as location, seniority or contract type, first. Quote the line from the post that triggered each mismatch. Keep the whole report under 200 words.
What can go wrong?
- A thin profile gives generous scores; be specific about deal-breakers.
- A public gist exposes your preferences; keep salary details out.
Our take
The best part is the order of work: he clarified what he wanted before touching any tool, which is what makes the score meaningful. The workaround is practical when features lag. Writing a structured profile of strengths, interests and hard limits first is what gives the score any meaning; a thin profile produces generous verdicts for everything. Spell out deal-breakers clearly and decide in advance which criteria force a skip. When the browser extension could not run Claude skills, Jose saved the evaluation prompt as a shortcut instead, which is a sensible way to keep using a tool while waiting for features. Hosting the profile in one place means edits apply everywhere, but if you use a public gist, keep salary expectations and anything personal out of it. Run it on each posting and read the reasons, not just the number. Update the profile when your target roles change. It should never apply on your behalf.
Where the time goes back: It removes the slow reread of every vague posting, so you only open applications for roles that fit.
FAQ
Why not a skill?
What caught a bad fit?
Source and credit
The original prompt on this page is by Jose Antonio Morales, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- Claude Skills: Helping Us Make Better, Faster Decisions
- Creator
- Jose Antonio Morales
- Published on
- automato.substack.com (Substack)
- Original date
- Feb 18, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.