agentleFS
ZoolCoderZoolCoder/scoutjobs/skills/upskill/SKILL.md

upskill

Skill4 starsChanged 32 days agoMITView on GitHub

Finds skill gaps between the user's profile and the jobs they track (especially ones they skipped, lost, or scored low on), ranks gaps by market demand, builds a learning plan with concrete resources, and tracks progress in ScoutJobs. Use when the user says "what should I learn", "skill gaps", "learning plan", "upskill", or weekly.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use freehire-search, linkedin-search and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • arafat1023Skill

    freehire-search

    Use this skill to search live software / tech / data / engineering job listings across many countries and markets (and remote) via the freehire.dev aggregator's public API, or to look up a specific posting. It aggregates roles from ~50 ATS platforms into one schema, so a single skill covers many markets — but its faceted filtering (skills, category, seniority) is tuned tech-first, so scope triggers to technical roles. Trigger phrases: find a tech job, software job search, developer jobs, engineering vacancies, data/ML jobs, DevOps roles, remote developer jobs, "are there any <tech role> jobs in <place>", look up this freehire job posting.

    Also in 6 projects that use this

  • arafat1023Skill

    linkedin-search

    Use this skill whenever the user wants to search for jobs in any location or market, find job listings, or look up a specific job posting — in any country, city, or remotely. Invoke for open positions, vacancies, and hiring across any sector or role (software, data, design, marketing, finance, legal, operations, etc.). The location is always supplied explicitly by the user. Trigger phrases: find a job, job search, search for jobs, job openings, vacancies, hiring, positions open, remote jobs, "are there any X jobs in <place>", look up this job posting.

    Also in 6 projects that use this

  • at350Skill

    job-application-assistant

    Runs the end-to-end application pipeline — research a posting, aggressively tailor a one-page .docx resume and a human-voiced cover letter, verify formatting, auto-apply through the browser after approval, and feed approved new bullets back into the bullet bank. Triggers on keywords like: job posting, job application, CV, cover letter, resume, tailor, apply, auto-apply, interview prep, job fit, career.

    Also in 6 projects that use this

  • velasco810Skill

    scrape

    Scrape LinkedIn connections or search results for a person using Playwright

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user reports study time: scoutjobs learn set <id> --hours 1.5.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Upskill

Input: scoutjobs job list --json (all statuses), the posting text per job (posting.md in each application folder), profile.md Skills section, scoutjobs learn list --json, and recent mock results from scoutjobs session list --json.

1. Demand

For every tracked job, extract required and nice-to-have skills from the posting. Normalize names (k8s = Kubernetes, GCP = Google Cloud). Count, per skill: in how many jobs it appears, how many of those were rejected, skipped with a stack signal, or scored under 60 by job-fit. That is the demand signal.

2. Gap

Compare to the profile: Strong = no gap, Working = small gap, Learning or absent = gap. Also add anything mock-interview or interview-debrief logged with --priority 1.

3. Rank

Priority 1: gap present in 3 or more target jobs, or caused a rejection. Priority 2: in 2 jobs or nice-to-have in many. Priority 3: everything else. Respect preferences: a skill tied to a stack_avoid value is not a gap, it is a filter; say so.

Show a heatmap-style table: skill, demand count, your level, priority.

4. Plan

For the top 3 to 5 gaps, propose one resource each (official docs, a well-known course, a book, or a repo to build), an estimated hour budget, and a concrete proof of learning the user can put in their profile (a small project, a certification, a blog post). Search the web for current resources; prefer free and official.

Record:

scoutjobs learn add --skill Kubernetes --priority 1 --demand 7 --resource "https://kubernetes.io/docs/tutorials/" --notes "goal: deploy the scoutjobs dashboard to a local kind cluster"

5. Track

When the user reports study time: scoutjobs learn set <id> --hours 1.5. When done: --status done, then update the profile's Skills section (move the skill to Working or Strong) and tell the user to re-run job-fit on open jobs since the scores will change.

Weekly: scoutjobs learn list is on the dashboard at /learning; the weekly-review skill reads it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.