Written to be self-selecting, not just accurate.
The tool that turns a generic job posting into one that attracts the specific people who'd succeed in the role, by naming the real texture of the work, including the parts most postings leave out.
Most job descriptions are written to be defensible, not effective: broad enough to sign off on, generic enough to describe a hundred similar postings elsewhere. That's exactly why they attract everyone and filter nobody.
This tool describes the real work, including the hard parts, writes the specific details that make the right candidate think that's me, and challenges every requirement that would filter out someone who'd actually succeed.
Same role, written to filter on purpose.
Same hire, same requirements, run two ways.
A 20-person startup is hiring its first dedicated customer support lead, a role previously handled ad hoc by the founder.
You ask Claude to write a job description. You get a clean, professional posting: responsibilities, requirements, a line about a fast-paced environment.
It could describe the same role at a hundred other startups, and it says nothing about the actual first weeks: reading an unresolved backlog with several genuinely upset customers and no existing playbook.
It writes the specific details that do the actual filtering:
- →"You'll be building the playbook, not following one"
- →"Some early weeks are more cleanup than strategy"
- →A requirement for prior SaaS experience challenged and moved to nice-to-have, since a strong candidate from elsewhere would still be considered
The finished posting states plainly in the opening line that there's no process yet and this person builds it, which repels candidates who want a defined role and attracts exactly the ones who don't.
The cold version described the job. This filtered for the person who'd actually want it.
- ✦Founders and hiring managers defining a role for the first time
- ✦Teams whose postings have attracted the wrong applicants before
- ✦Anyone reusing a job description template that hasn't been touched in years
- →job-description.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to
~/.claude/skills/ - →job-description-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
- →A README inside the zip with install steps for Claude, ChatGPT, Gemini, and the API
What it does with a real question.
I need a job description for a Customer Success Manager at a 40-person software company. The role handles about 35 mid-market accounts, owns renewals, and works closely with product. We have had a lot of unsuitable applicants who want a pure support role. Salary range is $70,000 to $85,000.
Your posting has one job: make the support-seekers opt out. Your applicant problem comes from the title, not the candidates. "Customer Success Manager" reads as friendly help-desk work to anyone skimming, so the first line of the posting has to say what the role is: you own the commercial relationship with 35 mid-market accounts, including the renewal number. Lead with that, and put the sentence that does the filtering near the top: "This is not a ticket-queue role. Support handles tickets; you handle whether these accounts stay and grow."
Then describe the real texture, including the hard parts. You'll be the person a customer calls when they're thinking about leaving, you'll carry a renewal target, and you'll go to product with specific account evidence and argue for fixes. Some of those conversations will be uncomfortable, and naming that will repel exactly the people you're trying to avoid.
On requirements, cut years-of-experience and industry filters. Ask instead for demonstrated ownership of renewals or a commercial outcome, and comfort working with a product team as a peer. Move "SaaS background" to a nice-to-have.
Put the $70,000 to $85,000 range in the posting. Candidates who want pure support rarely respond to a number paired with a renewal quota.
Next move: draft the opening three sentences today, starting with what the person owns and ending with what they don't do, and test them on someone who isn't in your company.
The full Tool runs the whole procedure and writes the complete deliverable, not this excerpt.
Written by claude-sonnet-5-5 with this Tool loaded, 2026-10-11. Checked automatically for length and for copied framework text.
No subscription · free updates within v1.x
Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable
Before you buy.
How is this different from just asking Claude directly?
Asked cold, Claude writes a clean, generic posting that could describe the same role anywhere. This describes the real texture of the work including its hard parts, writes the specific details that self-select the right candidate, and challenges every requirement that would filter out someone who could actually do the job.
Will this work with ChatGPT, Gemini, and other LLMs?
Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.
Can I share this with my team?
It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Tool itself in the hands of a whole team, email hello@authority.md about team licensing.
What if it doesn't work for me?
If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.
Job Description is a hiring-copy tool. Not employment-law advice; consult HR or counsel on what requirements and preferences are lawful for your role and jurisdiction.