careers page generator

careers page generator

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.

المهارة نفسها

# Pages: Careers

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.

## Initial Assessment

**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:
1. **Audience**: Job seekers, passive candidates
2. **Open roles**: List or link to ATS
3. **Employer brand**: Culture, benefits, perks

## Best Practices

### Essential Elements

| 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 |

### Structure

- **Hero**: Employer value proposition; "Join us"
- **Open roles**: List or embed; filter by department/location
- **Why us**: Culture, benefits, growth
- **Team**: Photos, quotes, diversity
- **Process**: Application steps

### SEO

- Target "company name careers," "jobs at company"
- Schema: JobPosting for each role
- Internal links from About, Home

## Output Format

- **Structure** outline
- **Employer brand** messaging
- **Open roles** section approach
- **SEO** metadata and schema

## Related Skills

- **about-page-generator**: Culture and team overlap
- **schema-markup**: JobPosting schema
- **title-tag, meta-description, page-metadata**: Careers page metadata

كيف تثبتها

Claude Code / Claude Desktop

1. Create a folder named after the skill inside your skills directory:
   - Claude Code: `~/.claude/skills/<skill-name>/`
   - A project-local skill: `<project>/.claude/skills/<skill-name>/`
2. Save the text below as `SKILL.md` in that folder, keeping the
   `---` frontmatter block at the top — the `name` and `description`
   fields are what make the skill discoverable.
3. Restart Claude Code, or run `/skills` to confirm it is listed.

The skill loads only when its `description` matches what you are doing,
so a precise description matters more than a long body.

هل نجحت معك؟

من أين جاءت

kostja94 MIT الأصل

2025 kostja94