Loading video...

Video Failed to Load

Go Home

A guy on Reddit got so fed up with scrolling LinkedIn for internships that he built his own job search engine with Claude Code. The tool is called Pinloop. It's an open-source CLI, and he built it with Claude Code too. Here's how it works: → It pulls millions...

18,719 views • 7 days ago •via X (Twitter)

14 Comments

Vaibhav Sisinty's profile picture
Vaibhav Sisinty7 days ago

The agent installs it and walks you through setup. 🔗

Ram Pathath's profile picture
Ram Pathath7 days ago

linkedin scroll hell as a product brief. love that he shipped the cli with the same tool that was hunting the jobs

RavenWarrior's profile picture
RavenWarrior7 days ago

Good we’re sick of paying for every website.

Odera Joseph 🇳🇬 🇵🇭's profile picture
Odera Joseph 🇳🇬 🇵🇭7 days ago

Nice loop. Pulling the shortlist to you beats another tab-heavy job hunt.

Vaibhav Sisinty's profile picture
Vaibhav Sisinty6 days ago

I share tools & Information like this daily in our free AI WhatsApp community. 200,000+ people already in. Join for free :

@PlayOnPoet's profile picture
@PlayOnPoet6 days ago

A race the the bottom

Julian's profile picture
Julian7 days ago

I did this all running locally though, most of it is python scripts than my local model compares my CVs to job descriptions if there's a title match. It sometimes misses, but so far it's scanned 23 million jobs.

AI First Solopreneurs's profile picture
AI First Solopreneurs6 days ago

This is the solopreneur loop done right. Week of pain on LinkedIn, then ship an open-source CLI with Claude Code. Real users of the pain, not a demo.

devender reddy pulyala's profile picture
devender reddy pulyala7 days ago

With Pinloop pulling hourly data from over 50 hiring systems, scraping blocks could quickly cut off the pipeline, leaving it unclear how the tool bypasses rate limits.

Samuel Hu's profile picture
Samuel Hu7 days ago

the hourly refresh is the part that gets real fast. i tried the same shape with Greenhouse once and the first run died on a 429 after 60 pages, so i had to add backoff before trusting the shortlist.

mao mao's profile picture
mao mao7 days ago

Great example of AI lowering the cost of a useful first version. The product lesson after search works is the feedback loop: narrow the ranking and filters until one specific audience gets an answer faster than LinkedIn.

Michał Stankiewicz's profile picture
Michał Stankiewicz7 days ago

🤜🏻🤛🏻

The AI Therapist's profile picture
The AI Therapist7 days ago

Pinloop proves Claude Code isn't just for fixing bugs; it's a legit full-stack partner. Building that CLI takes some serious prompt engineering finesse. He didn't just ask, he architected.

Devansh Chaudhary's profile picture
Devansh Chaudhary6 days ago

Got Instinct to do the same thing to look for clients who want AI content services. Works so well

Related Videos

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,502 views • 3 months ago

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

Yarchi

818,556 views • 3 months ago