If you use OpenClaw, Remoet is now one command away.
openclaw skills install @remoet/remoet
That drops the Remoet skill into your OpenClaw setup. From there, ask your agent to "set up Remoet" and it walks you through the rest: generate a free API key at the agent door of onboarding, export REMOET_API_KEY, and wire up the MCP server with openclaw mcp set. Once that's done, the agent can search the whole job board, find companies by tech stack, star the ones that fit, pull a filtered list from your shortlist, manage your profile through conversation, and run the daily job search loop without you bouncing between tabs.
The skill has been rewritten more than once since it first landed (version 1.4.1 is what's live on clawhub.ai/remoet/remoet, so an install today gets the current one). The account is free, needs no credit card, and there are no tiers to climb. The whole setup conversation takes about two minutes.
What you can actually do
The pitch in one line: instead of clicking around a job board, you talk to your agent and it talks to Remoet on your behalf.
Find companies by stack. Ask your agent "which companies use Rails plus React plus Postgres" and get a real list back. Remoet scrapes and enriches the tech stack of every company on the platform from the roles it is hiring for, not recruiter-tagged keywords on job postings, so the matching is grounded in reality.
Search the whole board. search_jobs reads the open catalogue at remoet.dev/jobs. Every company, no star needed and none consumed. It filters on free text, tech stack (any of them, or every one on the same role), company, location, remote policy, seniority and minimum salary, and sorts by newest or salary. As of September you don't even need an account for this one: point any MCP client at the server and search. The key is for the parts that are yours, the profile, the stars, the saved jobs.
Curate your shortlist by starring. A star doesn't lock any job behind it: you can already search every role with none. What it does is put a company on watch, so its new roles land in your feed, in the roundup email (daily, weekly on Mondays or monthly, whichever you pick) and in get_starred_jobs, and the three-technology teaser opens up into the full stack. Starring is free; unstarring draws from a monthly budget, so it isn't something to click around with.
Work your shortlist. get_starred_jobs runs the same filters over the companies you starred, so "senior, remote, above 90k, from my list" is one question rather than a scan. The open board is how you look around; your shortlist is what keeps coming to you.
Manage your profile by talking. Update your summary, add a work experience, add a project, edit a link. The classic "I should update my profile but I never do" problem solves itself when the cost of an update drops to one sentence.
A killer first-session demo. Paste your CV. Have the agent populate your profile, search the board for roles that match it, star the companies worth hearing from again, and pull the filtered list from your new shortlist. All in one conversation. Cold start to running job feed in five minutes.
Why this matters more than another directory listing
OpenClaw is the biggest AI agent on GitHub. ClawHub is its skill registry, the place where OpenClaw users go to find new capabilities. If you are the kind of developer who runs an agent every day, ClawHub is where your tools live. Putting Remoet there makes the platform discoverable to exactly the audience that benefits most: developers who want their agent to handle the boring half of looking for work.
It is also a different audience from our existing user base, most of whom found us through search or word of mouth. ClawHub installs are agent-native by default. They show up with their stack already in their head, an agent already configured, and an expectation that everything works through conversation. That is the user we built the platform for.
What does not work yet (be honest with your agent)
A few things to know so your agent does not promise you something the platform cannot deliver:
Most jobs are external scrapes. The agent finds the job and hands you the link, you apply on the company's site like always. Internal applications, end to end through Remoet, only work for companies posting directly via the partner system.
Application records are not an agent surface yet. Save the role and attach a note ("applied Tuesday, referred by X") so it stays on file. The application-record tools exist in the code but are not listed to agents.
No GitHub integration yet. Your tech stack is what is in your Remoet profile, not what is in your repos. Populate the profile first, the rest gets smarter.
The board covers cleared ATS platforms only. Lever, Greenhouse, Ashby, Recruitee and Workable. A company hiring somewhere else does not turn up in the scrape.
Anything that is yours still needs the key. Searching is open, but your profile, your stars and your saved jobs are not, so the skill still asks for
REMOET_API_KEYwhen it installs.
What I want from you
If the install works smoothly, ping me on Discord with your prompt and what the agent came back with. The stories that come out of real users running the daily loop end up in everything we write next.
If something breaks on install, auth, or any of the tools, also ping me. Rough edges on a distribution channel surface when real people walk the path, and I would rather hear it from you than from a silent abandon.
Plug in. Tell me what changes.
