career-path
Skill0 starsChanged 56 days agoMITView on GitHub
Analyse the candidate's career pathways (3–5 years), skill gaps, certification sequencing, and which live jobs advance which path. Use when the candidate asks "what should I aim for", "career path", "where is this going", "what to learn next", "/career-path".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- guillaumesimler/claude_skillstheir own version, first seen Jun 21, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- guillaumesimler/claude_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Run node tools/insights.mjs first and read reports/market-insights-<today>.md — the gap table and years-asked distribution are the evidence …
- Very specific: line 25
Keep it under 3 pages. Then ask the candidate which path resonates and update career-context.md with their answer.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/career-path
Inputs
Run node tools/insights.mjs first and read reports/market-insights-<today>.md — the gap table and years-asked distribution are the evidence base; cite the numbers.
profile/career-context.md, profile/master-resume.md, profile/certifications.md, profile/achievements.md, profile/preferences.json, data/jobs.json (rated jobs), data/pipeline.json. Check what the hunt actually surfaced in the last 30 days — the market data beats theory.
Output: reports/career-path-<today>.md
- Where the candidate is now — one honest paragraph: strengths (Oracle EPM + gen-AI at a Big 4, certified, builds agents, public writing), constraints (~2 years experience, Perth market size, generalist vs specialist tension).
- Three pathways (write each with 12 / 36 / 60-month milestones, typical titles + AU salary ranges you can source, and the "signature proof" needed to move up):
- A. AI engineering / forward-deployed (AI-native firms, BCG X, Palantir-style FDE, consultancies' AI teams).
- B. Oracle EPM/ERP specialist → solution architect (current-employer progression, Oracle partners, in-house at miners).
- C. Strategy/tech consulting generalist (BCG/McKinsey/Bain, Big 4 advisory) with an AI edge. Plus the hybrid most people in the candidate's position actually take, and what optionality each path preserves.
- Gap analysis table — skill → current evidence → gap → how to close (free resource / work project / cert) → which path it unlocks.
- Certification sequence — EDMCS (booked) → Claude Certified Architect Foundations → then decide (OCI Architect? AWS ML? none — projects may matter more). Give dates relative to today and hours per week.
- Portfolio moves — 2–3 public artefacts that would change how recruiters read them (e.g. an open-source MCP server for Oracle EPM; a written case study of the your current employer gen-AI MVP with client anonymised; talks/posts cadence).
- Live roles mapped to paths — from
data/jobs.jsonratings: which current postings advance which path, and which to ignore even if they're easy to get. - Decision points — the 2–3 questions only the candidate can answer (stay at the current employer for promotion vs move now; Perth vs relocate; specialist vs generalist) with the trade-offs laid out neutrally.
Keep it under 3 pages. Then ask the candidate which path resonates and update career-context.md with their answer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

