agentleFS
velasco810velasco810/claude-code-linkedin/skills/scrape/SKILL.md

scrape

Skill1 starsChanged 7 months agoMITView on GitHub

Scrape LinkedIn connections or search results for a person using Playwright

  • Installs packages

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use freehire-search, ios-sync and 10 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

  • Saqlain-811Skill

    ios-sync

    Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)

    Also in 6 projects that use this

  • ShreyRaviSkill

    setup-gbrain

    Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. One command from zero to "gbrain is running, and this agent can call it." Use when: "setup gbrain", "connect gbrain", "start gbrain", "install gbrain", "configure gbrain for this machine". (gstack)

    Also in 8 projects that use this

  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 10 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 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

  • +3 more from ShreyRavi
  • +1 more from Saqlain-811

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 25 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:

    If $2 is empty, omit the --url flag so the scraper uses its default URL for the type.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 25 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

LinkedIn Scraper

Scrape LinkedIn profiles from a connections page or search results page.

Arguments

  • $0 — Person name (used as output folder, e.g. "eduardo", "aum")
  • $1 — Type: connections (infinite scroll) or search (paginated)
  • $2 — LinkedIn URL to scrape (optional; uses default if omitted)

Steps

  1. Install dependencies (if not already installed):
cd ${CLAUDE_SKILL_DIR}/../.. && npm install --silent 2>&1 | tail -3
  1. Run the scraper:
cd ${CLAUDE_SKILL_DIR}/../.. && node scrape-connections.js --name "$0" --type "$1" --url "$2"

If $2 is empty, omit the --url flag so the scraper uses its default URL for the type.

  1. Report results — After the scraper finishes, read the metadata:
cat ${CLAUDE_SKILL_DIR}/../../output/$0/meta.json

Report:

  • Number of profiles scraped
  • Output file path
  • Timestamp
  1. Suggest next step:

To analyze and rank these profiles, run: /linkedin:analyze $0 "<your ranking criteria>"

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.