Individual skill
playbook-job-posting-language
Produces a copy-ready clause about a role a company is currently hiring for, filtered by language the client cares about (for example "cold call", "outbound prospecting", "Salesforce"). Triggers on "they're hiring", "job posting language", "who is hiring SDRs", "companies hiring for X", "find the hiring signal", "what roles are they hiring for", "job description mentions". Outputs job_posting_line_safe, one lowercase clause that slots into "Saw {{job_posting_line_safe}}."
skills/playbooks/playbook-job-posting-language/SKILL.md
Source commit 25c5d85fbb5dd3efec97b0ca457cbbc286547476
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 814
- Repository last updated
- Oct 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 18,193 bytesSKILL.mdcore · 18,193 bytesSKILL.mdcore · 18,193 bytesSKILL.mdcore · 18,193 bytesSKILL.mdcore · 18,193 bytesclay-table.mddoc · 4,474 bytesclay-workflow.mddoc · 7,050 bytes
Read excerpt
# Playbook: Job Posting Language
> All rules here are best practice, not law. Override any of them when the campaign calls for it; note the best practice once and move on.
**Use when:** the angle is "you are hiring for this, and that is exactly what we help with". The
client names the roles or the description language that signals a fit, and every row needs a
specific, current opening to reference.
**Do not use when:** you want *how many* people they hired or headcount growth over time
(`playbook-hiring-surge`). If you want to **find** companies hiring a role rather than enrich a list
you already have, that is discovery mode — see note E.
**One-line output:** `job_posting_line_safe = "you're hiring an account executive for private equity"`