splash0047/resume-generator / skills/application-strategy
Application Strategy
VerifiedDecide how to prioritize job applications using hard eligibility, evidence coverage, role alignment, and real application outcomes rather than arbitrary fit scores.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.0 KB |
SKILL.md
View on GitHub---
name: Application Strategy
description: Decide how to prioritize job applications using hard eligibility, evidence coverage, role alignment, and real application outcomes rather than arbitrary fit scores.
---
# Application Strategy
## Purpose
Prevent low-value "spray and pray" applications while avoiding false precision from a universal match score.
## Step 1 — Hard Eligibility Gate
Extract and check:
- graduation batch / degree completion timing;
- current-student or new-grad status;
- degree/discipline constraints;
- work authorization or sponsorship language;
- location or relocation requirements;
- internship/full-time availability dates;
- mandatory years of professional experience;
- any required application-question conditions.
Classify each as **Meets / Does not meet / Unclear**.
Do not optimize the resume around a role before this gate is checked.
## Step 2 — Requirement Evidence Coverage
For every required and preferred criterion, record whether the candidate has:
- **Direct evidence** — project/experience demonstrates use;
- **Indirect evidence** — coursework/certification/adjacent experience;
- **No evidence**.
Summarize with counts, for example:
"Required criteria: 6 direct, 1 indirect, 1 missing."
This is a transparent coverage summary, not an ATS probability.
## Step 3 — Role-Family Alignment
Choose the resume variant that best matches the role:
- Software / Backend / Full-stack
- Applied AI / ML
- Enterprise / ERP / Data
- Other role family when evidence supports it
Do not mix every technology into one resume. Lead with the evidence most relevant to the selected role family.
## Step 4 — Application Priority
Use qualitative priority based on:
- eligibility;
- direct evidence for required work;
- project/experience recency and depth;
- role-family alignment;
- application channel (campus, referral, recruiter outreach, direct inbound);
- time cost of the application.
Suggested labels:
- **Apply now** — eligible and most required criteria have direct evidence.
- **Apply with targeted edits** — eligible, but evidence presentation is weak or some preferred criteria are missing.
- **Apply as a stretch** — eligible but one or more important required criteria are indirect or weak.
- **Do not prioritize** — a hard requirement is clearly unmet or the role family is substantially different.
These labels are workflow guidance, not predictions of whether the employer will select the candidate.
## Step 5 — Submission Checklist
Before submitting:
- select the correct role-family resume;
- verify expected graduation is explicit for student/new-grad roles;
- confirm links open and project descriptions match the linked repositories;
- validate PDF text extraction and reading order;
- review auto-populated application fields;
- answer eligibility questions accurately;
- save the job URL, resume version, date, and channel.
## Step 6 — Outcome Learning
Track each eligible application as:
- pending;
- rejected before assessment;
- assessment received;
- rejected after assessment;
- interview received;
- rejected after interview;
- offer.
Diagnose the stage where progression stops:
- mostly pre-assessment rejections → inspect eligibility, role fit, resume evidence, parsing, and channel;
- assessments but few interviews → focus on assessment performance;
- interviews but few offers → focus on technical depth, project defense, and communication;
- stronger outcomes in one role family → concentrate future applications there.
Do not treat a small sample as proof. Use the tracker to form hypotheses and update the strategy.
## Guardrails
- Never predict that a candidate will be shortlisted.
- Never convert keyword overlap into a hiring probability.
- Never recommend misrepresenting graduation status, experience, location, or work authorization.
- Never add technologies solely because they appear in the job description.
- Keep referral/direct/campus channels as parallel strategies rather than promising one channel will work.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |