jobwatch@1.2.3
VERIFIED· install onlyPublisher claims: "Autonomous job-market watcher for OpenClaw. On a cron schedule it monitors the career pages of companies the user has EXPLICITLY configured, judges each posting against the user's own job profile (visa / seniority / red lines) with an LLM, pushes strong matches, digests the rest daily, and archives postings into a knowledge base; it also tracks the user's application status and answers questions about their own watched jobs. PRIVACY & CAPABILITIES (see the Privacy & Data Flow section): this skill collects and stores a personal job-seeking profile (resume text, visa needs, seniority, red lines); sends watched URLs and job-description text to third-party services (Firecrawl / Jina scrapers, an OpenAI-compatible LLM endpoint, and a 2brain knowledge base); reads host OpenClaw / Telegram credentials only when the user opts in (JOBWATCH_ALLOW_HOST_CREDS=1); and registers a recurring cron job — every autonomous action happens only after an explicit onboarding consent step. Use ONLY when the user clearly wants automated job monitoring for their own search — not on casual mention of jobs. Trigger when the user asks to set up or run job monitoring, to watch specific companies' careers pages, reports their own application update, or asks about their own watched/matched jobs. Triggers — imperative requests only; a bare mention of jobs, careers or 求职 must NOT activate this skill: 'set up jobwatch for me', 'start job monitoring for my search', 'watch <company>'s careers page for me', 'I applied to <specific job>', 'jobwatch top jobs this week', '帮我设置求职监控', '开启求职监控', '帮我盯 <公司> 的岗位', '我投了 <职位>'. If the user is only discussing or asking about jobs in general, do not activate. Before the first onboarding question — and before any profile data is collected, any credential is read, or any cron job is registered — state what the skill will collect and send, and get an explicit yes." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-10 and scored it 81/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
# Least privilege: by default this skill reads only the keys you put in HOME/.env.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.this variable the skill reads only the .env file you filled in yourself.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`HOME/.env`. Reusing the OpenRouter key already stored in OpenClaw, or the Telegram config inFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.in your own `.env` over host reuse; the narrower the grant, the smaller the blast radius.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose..env — faster and steadier)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"https://api.telegram.org/bot{token}/sendMessage",Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.# outside this skill's own .env when JOBWATCH_ALLOW_HOST_CREDS=1; see common.py.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raise RuntimeError(f"{name} not set in .env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.for env_file in (ROOT / ".env", SKILL_DIR / ".env"):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Load ROOT/.env into os.environ (existing env wins)."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- twobrain 2brain 知识库（需要 .env 里的 TWOBRAIN_* key）Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.fill in HOME/.env (see the skill's env.example); wait until they finish before continuing.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"JOBWATCH_ALLOW_HOST_CREDS=1. Unset it to keep this skill to its own .env.",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Returns (items, errors). One source failing doesn't kill the others (失败隔离)."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.