Job Post Builder

Produces a complete hiring packet — job post, interview guide, and offer letter — from a brief conversation about the role. Optionally routes the offer letter to DocuSign via Claude in Chrome.

Quick start

Invoke when a user says they need to hire someone or produce any hiring document. The skill walks a 6-phase workflow: gather context → research the market → write the job post → draft the interview guide → assemble the offer letter → (optionally) route to DocuSign.

Example trigger:

"We're hiring a senior product manager. Can you put together the job post and interview questions?"

Workflow

1. Gather role context — Ask for role title, responsibilities, qualifications, location, comp, interview process, and offer delivery preference (Word doc vs. DocuSign). Source: conversation / AskUserQuestion.
2. Research comparable posts — Search Google Drive / Desktop for existing JDs and templates; run web search for 3–5 live postings for this role. Sources: file MCP, web search.
3. Write the job post — Draft a market-informed job description using references/job-post-structure.md. Output: [Role]-Job-Post.docx via docx skill.
4. Draft interview guide + scoring rubric — Build a stage-by-stage guide using references/interview-guide-structure.md. Output: [Role]-Interview-Guide.docx via docx skill.
5. Assemble offer letter — Build offer letter with bracketed placeholders using references/offer-letter-template.md. Output: [Role]-Offer-Letter.docx via docx skill.
6. Route to DocuSign (if requested) — Use Claude in Chrome to navigate DocuSign, upload the offer letter, configure the envelope, and save a draft. Requires explicit user approval before the envelope is sent.

Approval gates

This skill performs externally-visible actions in Phase 6. The following rules apply:

• Never send a DocuSign envelope without approval. Save the envelope as a draft and return the URL. The user must review and confirm before Claude clicks Send.
• Never send the Gmail fallback email without approval. If the DocuSign browser flow fails, draft the fallback email and show it to the user before sending.
• Never publish the job post. Produce the .docx file only. Posting to any job board is the user's responsibility.

Phase 6 will not advance past "Save as draft" without the user explicitly confirming they have reviewed the envelope and want it sent.

Phase 1 — Understand the Role

Before researching or writing anything, gather enough context to do it well. Ask the user (via conversation or AskUserQuestion) for:

• Role title — exact title they want to post

• Team / function — who this person reports to and works with

• Key responsibilities — 3–5 things this person will own day-to-day

• Must-have qualifications — hard requirements (years of experience, specific skills, credentials)

• Nice-to-have qualifications — preferred but not required

• Location / remote policy — on-site, hybrid, or fully remote; location if relevant

• Compensation range — salary band if they have one (flag that this needs HR/legal sign-off)

• Existing JD or template? — ask if there's a prior version in Google Drive or on their Desktop to use as a starting point

• Offer letter delivery preference — ask how they'd like the offer letter delivered:

  • Send directly via DocuSign — skill opens DocuSign in Chrome, uploads the letter, sets up the envelope, and saves a draft for review before sending
  • Just the Word doc — skill saves the offer letter as a .docx and stops there; the user handles routing themselves

• Interview process — ask how their hiring process is structured:

  • How many rounds/stages are there?
  • Who conducts each stage? (e.g. recruiter, hiring manager, peer, skip-level, panel)
  • What is each stage meant to assess? (e.g. culture fit, technical depth, cross-functional collaboration)

…