Post Job

**Judgment:** A mature, high-utility hiring skill that significantly streamlines public job posting and LinkedIn distribution, but with meaningful privacy and dependency considerations due to its reliance on the Fuku AI relay service. **What it does well** - Posts a job to 20+ boards plus LinkedIn using a single tool (`post_job`), returning Job ID and application URL. - Offers follow-up tools (`check_linkedin_status`, `check_linkedin_status_auto`) to track when the LinkedIn listing goes live. - Strong documentation and clear workflow guidance (including required background monitoring via a spawned sub-agent). - Sensible validation: email format, minimum title/description length, city matching, strict jobId format, sanitization against prompt/log injection. **Key risks & limitations** - **Third‑party dependency:** All postings go through Fuku AI’s infrastructure; if their service is down, posting and/or LinkedIn sync can fail. - **Privacy & data exposure:** Job title, description, company, location, and the resume‑receiving email are transmitted to Fuku AI and may appear in public postings—unsuitable for confidential roles or sensitive details. - **Brand control:** Jobs appear under Fuku AI’s LinkedIn relay accounts, not the user’s official company page; may not meet branding or compliance requirements. - **Lifecycle control:** Editing/deleting postings must be done via Fuku AI support, not directly from this skill. - **Agent integration requirement:** For the best UX, the calling agent must correctly implement the background monitor pattern (via `sessions_spawn` or an equivalent), or users won’t be auto-notified of the LinkedIn URL. **Recommended scenarios** - Public, non-sensitive hiring where wide distribution and speed matter more than fine-grained control over each board. - Startups, small businesses, and independent recruiters who want a “fire-and-forget” way to get roles onto many boards and LinkedIn. - Agent workflows that turn a user’s natural-language “post a job” request into structured tool calls and then proactively update the user when LinkedIn sync completes. **Use with caution when** - Roles are confidential (executive, security-sensitive, internal transfers) or involve non-public business details. - Strict branding, compliance, or data residency policies prohibit using third‑party relay accounts or exposing a specific email address publicly. - Your OpenClaw environment cannot support background monitoring; in that case, build explicit manual polling flows around `check_linkedin_status`.