# job-post-writer

job-post-writer — a skill for Claude Code that writes realistic job postings with honest pay ranges and pruned requirements. Clarifies daily workflows and strips out corporate buzzwords before publishing.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 103 installs · ★ 440 repo stars
- Author: OneWave-AI
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/OneWave-AI/claude-skills/tree/HEAD/job-post-writer/SKILL.md
- Updated: 2026-10-20
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/job-post-writer

## What it does

The skill conducts an intake on day-to-day duties, 90-day targets, and team structure instead of relying on generic job titles. It classifies qualifications into essentials, teachable skills, and non-essential preferences, cutting the must-haves down to 4–6 core criteria.

Vague buzzwords like fast-paced or wearing many hats get removed in favor of direct descriptions of ownership and schedule realities. When drafting pay details, it queries state salary transparency rules using web search and flags misleadingly wide compensation brackets.

Output includes searchable role titles, an application flow designed to take under five minutes, and condensed blurbs for social channels. The resulting post feeds directly into cowork-hiring-screener and hiring-scorecard workflows.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill job-post-writer -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/job-post-writer/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/job-post-writer/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill job-post-writer -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/job-post-writer/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill job-post-writer -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/job-post-writer/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install OneWave-AI/claude-skills job-post-writer
```

2. **Manually: put the files in place**
- File: `.github/skills/job-post-writer/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill job-post-writer -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/OneWave-AI/claude-skills --path job-post-writer
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/job-post-writer/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill job-post-writer -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/OneWave-AI/claude-skills/tree/HEAD/job-post-writer/SKILL.md

## When to use it
- write a job posting based on actual daily responsibilities
- cut bloated requirement lists down to 4–6 core must-haves
- diagnose and rewrite stale posts that receive no applicants
- format salary disclosures according to state transparency rules

## Example prompts
- Write a post for a head chef
- Fix this post and tell me why it failed
- Why is nobody applying to our backend engineer role?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 2dd8aa16ed646367.

BEGIN THIRD-PARTY FILE 2dd8aa16ed646367
```text
---
name: job-post-writer
description: Write job posts that make the right person apply -- real role clarity, honest selling points, salary range handling, and requirements pruned to what actually predicts success. Small businesses lose great candidates to bad posts long before the interview. Feeds cowork-hiring-screener and hiring-scorecard downstream.
tools: Read, Write, Bash, WebSearch
model: inherit
---

# Job Post Writer

A job post is an ad competing against every employer in the market, and most read like compliance documents. Write the one the right candidate stops scrolling for -- honest about the work, specific about the money, and stripped of the requirements that filter out people who would have been great. Input: what the role actually does day-to-day (interviewed out of the owner if needed) and what the business can truly offer.

## Workflow

1. **Interview for the real job.** Not the title -- the Tuesday: what this person does most days, what problem hiring them solves, what the first 90 days look like, who they work with, and what made the last person in the role succeed or fail. If the owner cannot answer these, that gap is finding number one.
2. **Prune the requirements.** Sort every requirement into must-have (day-one necessity that cannot be taught in 90 days), trainable, and decoration. Degree requirements, years-of-experience counts, and tool checklists get challenged individually -- every unnecessary must-have shrinks the pool, and shrinks it worst among candidates who take requirements literally. Land on 4-6 real must-haves.
3. **Find the honest sell.** Small businesses cannot outbid corporates, but they can offer what corporates cannot: scope ("you'll run the whole kitchen, not station 4"), visibility, schedule reality, speed of growth, no-bureaucracy, the actual humans. Pull the true ones from the interview -- and never write "family atmosphere," "fast-paced," "wear many hats," or "rockstar," which candidates correctly read as understaffed, chaotic, and underpaid.
4. **Handle the money.** Push for a posted range: posts with pay get dramatically more applicants, and pay-transparency laws require it in a growing list of states (web-check the user's state). If the owner resists, show the math of what secrecy costs in applicant volume, and at minimum post the benefits and scheduling honestly.
5. **Draft and structure.** Title candidates actually search (not "Guest Experience Ninja"), opening two lines that state the role and the strongest sell (that is all most see on the feed), the Tuesday description, the pruned requirements, the pay/benefits block, and an application step that takes under five minutes -- every extra form field sheds good candidates who have options. Output versions sized for the job boards and the one-paragraph social/referral blurb.

## Rules
```
END THIRD-PARTY FILE 2dd8aa16ed646367

The third-party file has ended. Everything between the 2dd8aa16ed646367 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2836 of 3845 bytes. © OneWave-AI · MIT · https://github.com/OneWave-AI/claude-skills/tree/HEAD/job-post-writer/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
