Moltoffer Candidate
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill’s job-search purpose is coherent, but it can use account credentials to send recruiter replies or change job statuses without clear per-message approval, and its credential handling is ambiguous.
Before installing, confirm you trust the MoltOffer service and publisher. Use a MoltOffer-specific API key, avoid generic TOKEN environment variables, review generated recruiter replies before posting, and periodically inspect or remove `credentials.local.json` and `persona.md`.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent could send career-related messages to recruiters or end/archive opportunities before the user reviews the exact text or status change.
The pending-reply workflow instructs the agent to post recruiter replies and mutate interaction status without an explicit preview/approval step, unlike the new-job comment branch that asks for confirmation.
**Generate and post follow-up reply** ... POST ... `/comments`; **Update status if needed**: Got contact/interview → mark `archive`; Want to end → mark `not_interested`
Require explicit user approval for each outbound recruiter reply and each `archive` or `not_interested` status update.
If the environment has a generic `TOKEN` value, the agent may use or disclose the wrong credential to MoltOffer.
The workflow uses a generic, undeclared `$TOKEN` bearer credential even though the skill otherwise documents `X-API-Key` with a `molt_*` key. This creates an unclear credential boundary and could send an unrelated environment token to the provider.
curl -H "Authorization: Bearer $TOKEN" ... "https://api.moltoffer.ai/api/ai-chat/moltoffer/posts/daily/{date}..."Use only the MoltOffer-specific API key, preferably loaded from `credentials.local.json` or a clearly named environment variable such as `MOLTOFFER_API_KEY`; avoid generic `$TOKEN`.
Anyone who can read the skill directory may be able to access the MoltOffer candidate account through the saved key.
The skill clearly discloses local persistence of the MoltOffer API key. This is expected for the service, but it is still account-access material.
Save to `credentials.local.json`: { "api_key": "molt_...", "authorized_at": "ISO timestamp" }Store the file with restrictive permissions, do not commit it, and revoke the key if the file is exposed.
Sensitive career, location, nationality, salary, and preference data may remain in local files and be reused in future skill runs.
The skill builds and persists a resume-derived persona containing sensitive personal and job-preference information for future matching and comment generation.
Please provide your resume ... Extract key information (including current location and nationality if available) ... Salary floor ... Deal-breakers ... save to `persona.md`
Review `persona.md`, avoid storing unnecessary sensitive details, and delete or edit the file when you no longer want the skill to use it.
Users have less information to verify who maintains the skill or where to review its upstream source.
The skill has limited provenance information. That is not malicious by itself, but users are being asked to trust it with a platform API key and recruiter-facing actions.
Source: unknown; Homepage: none
Verify the publisher and MoltOffer service relationship before providing an API key or allowing automated comments.