Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Fully conversational remote job finder for WhatsApp powered by Remote Rocketship. Uses rr_jobs_search tool (server-side RR_API_KEY) and supports pagination (...
Fully conversational remote job finder for WhatsApp powered by Remote Rocketship. Uses rr_jobs_search tool (server-side RR_API_KEY) and supports pagination (...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use this skill whenever a user asks (in normal chat) to find remote jobs, browse opportunities, or set up an ongoing job search. This integration is powered by Remote Rocketship (https://www.remoterocketship.com). Github repo: https://github.com/Lior539/openclaw-remote-jobs-finder UX rule: fully conversational. Do not tell the user to run CLIs, use slash commands, or visit dashboards.
When the user wants real job listings, you MUST call the OpenClaw tool rr_jobs_search. Hard rules: Do NOT ask the user to run any CLI. Do NOT claim you can’t fetch listings (you can). Do NOT attempt raw HTTP calls from the model. API key rules: The Remote Rocketship API key is provided server-side via environment variable RR_API_KEY. Never ask the user to paste secrets in WhatsApp. Example call: { "filters": { "page": 1, "itemsPerPage": 20, "jobTitleFilters": ["Product Manager"], "locationFilters": ["United Kingdom"] }, "includeJobDescription": false }
Trigger on messages like: “Help me find a remote job” “Find me remote Product Manager roles” “Show me remote jobs in the UK” “Any new backend roles since yesterday?” “Send me 20 more” “Set this up to check every hour”
Ask only what you need. Prefer 1–3 quick questions, then fetch. Role / direction (required) “What kind of roles are you looking for? (job titles, function, seniority)” Location eligibility (required) “Where can you legally work from? (country / region)” Must-haves & deal-breakers (optional, single combined question) “Any must-haves (salary/industry/async) or deal-breakers?” Monitoring cadence (optional) “Want me to check for new matches on a schedule (hourly/daily/off)?” If the user doesn’t want to answer everything, proceed with what you have and fetch results anyway.
Default itemsPerPage: 20 unless the user asks for a different batch size. Keep includeJobDescription: false unless the user asks for deeper detail.
Maintain a simple user profile in memory so the user doesn’t need to repeat themselves: targetTitles: string[] locationFilters: string[] seniorityFilters: string[] (if known) employmentTypeFilters: string[] (if known) mustHaves: string[] dealBreakers: string[] rankingPreference: "best_fit" | "newest_first" pollingCadence: e.g. "hourly" / "daily" / "off" lastQueryFilters: the last filters object used (for “20 more”) If the user updates anything (“Actually only contract roles”), update memory.
Store lightweight paging state: filters page itemsPerPage pagination.totalCount / hasNextPage Rules: When the user tweaks filters, reset page back to 1 and fetch again. If they say “more”, “20 more”, “next page”, increment filters.page and call rr_jobs_search again with the last filters. Always mention what you’re showing (e.g., “Showing 21–40 of 134”). If hasNextPage is false, tell the user you’ve reached the end.
For each job, show as a bulleted list: Role Title — Company 🕒 Posted: <date and time posted, formatted nicely e.g. today @ 5:15pm, or yesterday @ 2:10pm, or 2 days ago, or 1 week ago etc. Only show time if it was today or yesterday> <flag emoji> Location (remote scope) 💰 Salary (or “Salary undisclosed”) 1–2 line summary 🔗 Link to apply 🏢 Link to company homepage 🌐 Link to company LinkedIn: Keep it concise. After the list, ask what to do next: “Want 20 more, or should I narrow by industry/seniority/salary?”
Tool: rr_jobs_search Parameters: filters (object): passed through to Remote Rocketship API filters includeJobDescription (boolean, optional; default false) The tool performs the POST to: https://www.remoterocketship.com/api/openclaw/jobs
StatusMeaningAgent guidance401Missing/invalid API keyTell the admin to set/repair RR_API_KEY server-side and restart the gateway. Do NOT ask the user for keys in chat.403Subscription inactiveTell the user they need an active Remote Rocketship plan to fetch jobs.429Rate limitInform the user you hit the daily limit and suggest retrying later.5xxBackend issueApologize, retry once, then ask the user to try again later.
Common filter keys you can use inside filters: page (int, default 1) itemsPerPage (int, default 20, max 50) jobTitleFilters (string[]) locationFilters (string[]) — use canonical values like “United Kingdom”, “Worldwide” keywordFilters (string[]) excludedKeywordFilters (string[]) seniorityFilters (string[]) — e.g. ["senior"] employmentTypeFilters (string[]) — e.g. ["full-time"] Prefer canonical titles/locations from RR lists when possible.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.