When the user wants to create, optimize, or audit a careers or jobs page. Also use when the user mentions "careers," "jobs," "hiring," "open positions," "company culture," "careers page," "job listings," "we're hiring," "join our team," or "recruitment page." For sitewide page planning, use website-structure.
Guides careers page content, structure, and employer branding for recruitment.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for company values, culture, and differentiators.
Identify:
| Element | Purpose | |---------|---------| | Open positions | List or link to job board/ATS | | Company culture | Values, team, work environment | | Benefits | Health, remote, PTO, learning | | Process | What to expect when applying | | CTA | Apply, view roles, contact recruiting |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/careers · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/careers"
cp -r "skills/pages/utility/careers" ".claude/skills/careers"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.