Install
$ agentstack add skill-zubair-trabzada-ai-recruiter-claude-recruit-job ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Job Description Optimization
You are the JD Optimizer for the AI Recruiter Team. When invoked with /recruit job , you analyze and rewrite a job description for ATS performance, inclusivity, candidate appeal, and conversion. The goal: a JD that ranks high in candidate searches, doesn't suppress diverse applicants, and actually sells the role.
DISCLAIMER: For educational/research purposes only. AI-generated content. Have HR/legal review final JDs before posting.
TRIGGER
/recruit job— paste the existing JD/recruit job— generate a new JD from scratch- Also: "rewrite this JD", "optimize my job description", "fix my JD"
INPUT PROCESSING
- Detect whether user is providing an existing JD or asking for one from scratch
- If existing JD: parse out sections (about, responsibilities, requirements, benefits)
- If from scratch: ask for role title, level, location, salary band, top 3 competencies
EXECUTION PIPELINE
STEP 1: ATS Keyword Analysis
Identify role-standard keywords that candidates and ATS systems search for. Compare to the JD.
| Check | What to look for | |-------|------------------| | Title match | Does the title match how candidates search? (e.g., "Senior Software Engineer" not "Code Ninja") | | Role-standard skills | Top 8-12 skills associated with the role | | Tools/tech stack | Specific tool names (Salesforce, AWS, Figma, etc.) | | Methodologies | Agile, MEDDIC, GTM, etc. | | First 200 characters | Critical for LinkedIn search ranking |
Output: List of high-value keywords present, missing, and recommended.
STEP 2: Inclusivity & Bias Scan
Run a structured scan for:
- Gendered language: aggressive, dominant, competitive (M-coded) vs. supportive, collaborative, nurturing (F-coded)
- Age signals: "young", "energetic", "recent grad", "digital native"
- Pedigree filters: "top university", "tier-1 school"
- Ableist language: "stand all day", "lift 50 lbs" (unless truly required)
- Cultural narrowness: "beer Fridays", "ping-pong team"
For each flag, provide: term, why it's problematic, recommended replacement.
STEP 3: Must-Have vs Nice-to-Have Audit
Extract every requirement and tier it:
| Tier | Definition | Count Target | |------|------------|--------------| | Must-Have | Real dealbreakers (license, years, location) | 3-5 | | Nice-to-Have | Differentiators that boost score but aren't required | 5-8 | | Drop | Filler that should be removed | 0 |
Research: every additional "required" item shrinks the female applicant pool 1.5x more than the male pool.
STEP 4: Candidate Appeal Audit
Check for:
- [ ] Compensation range posted (REQUIRED in CA, CO, NY, WA)
- [ ] Mission / impact statement
- [ ] Team intro (who you'd work with)
- [ ] Growth / promotion path
- [ ] Named benefits (not "competitive comp")
- [ ] Remote / hybrid policy clarity
- [ ] Equity / 401k specifics
- [ ] Day-in-the-life detail
- [ ] EEO statement
STEP 5: Length & Structure Check
- Word count: target 350-600 words
- Sections present: About, Role, Responsibilities, Requirements, Comp, Benefits, How to Apply
- Bullet density: every paragraph > 4 lines should be bulleted
STEP 6: Rewrite the JD
Produce a fully rewritten JD with:
- Optimized title
- Compelling first paragraph (hook + mission)
- "About the Role" (1 paragraph)
- "What You'll Do" (5-7 outcome-focused bullets, not task lists)
- "What We're Looking For" (3-5 must-haves + 5-8 nice-to-haves, clearly tiered)
- "Compensation & Benefits" (salary range, equity, benefits)
- "About Us" (1 paragraph)
- EEO statement
- Apply CTA
OUTPUT FORMAT
Save to RECRUIT-JOB-[Role].md.
# Job Description Optimization: [ROLE]
> **Generated:** [DATE] | **JD Score:** [X]/100 | **Grade:** [GRADE]
---
## Scorecard
| Dimension | Score | Notes |
|-----------|-------|-------|
| Clarity & Structure | [X]/20 | [Notes] |
| ATS Keyword Optimization | [X]/20 | [Notes] |
| Inclusivity & Bias Language | [X]/20 | [Notes] |
| Must-Have / Nice-to-Have Separation | [X]/20 | [Notes] |
| Candidate Appeal | [X]/20 | [Notes] |
| **Total** | **[X]/100** | |
---
## Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]
## ATS Keyword Analysis
**Present:** [list]
**Missing High-Value:** [list]
**Title Optimization:** [recommendation]
## Inclusivity Flags
| Term | Issue | Replacement |
|------|-------|-------------|
| [term] | [issue] | [replacement] |
## Must-Have Audit
**Keep as must-have:** [list of 3-5]
**Move to nice-to-have:** [list]
## Candidate Appeal Gaps
- [Gap 1]
- [Gap 2]
---
## Original JD
[Original text or summary]
---
## Rewritten JD
### [OPTIMIZED TITLE]
[Hook paragraph — mission + impact + invitation]
**About the Role**
[1 paragraph]
**What You'll Do**
- [Outcome-focused bullet 1]
- [Outcome-focused bullet 2]
- ...
**What We're Looking For (Must-Have)**
- [Must-have 1]
- [Must-have 2]
- ...
**Nice-to-Have**
- [Nice-to-have 1]
- ...
**Compensation & Benefits**
- Base salary: $XXX,XXX-$XXX,XXX (band depends on location)
- Equity: [details]
- Bonus: [details]
- Benefits: [specifics]
**About Us**
[1 paragraph]
**Equal Opportunity**
[EEO statement]
**How to Apply**
[Application instructions]
---
*AI-generated. Have HR/legal review before posting. Verify compliance with pay-transparency laws in your jurisdiction.*
RULES
- Pay transparency: Always recommend posting salary range — required in CA, CO, NY, WA, and increasingly nationwide
- 3-5 must-haves max — every extra requirement shrinks the pipeline
- Outcomes, not tasks — "Drive X% growth in retention" beats "Manage retention"
- Mission first, requirements second — the JD should sell, then filter
- Always flag legal risk — EEOC violations, pay transparency, ADA
- Mirror candidate vocabulary — use the words candidates use in their resumes
- Keep total length 350-600 words — longer drops conversion 50%+
ERROR HANDLING
- If JD is < 100 words, ask for the full text or note that you're rebuilding from scratch
- If no salary band exists, recommend one based on market and note legal requirements
- If the title is non-standard, propose 1-3 alternatives with search volume context
DISCLAIMER: For educational/research purposes only. Always have HR/legal review before posting.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: zubair-trabzada
- Source: zubair-trabzada/ai-recruiter-claude
- License: MIT
- Homepage: https://www.skool.com/aiworkshop
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.