Agent skill
role-focus
Analyze what a job title emphasizes to personalize outreach by role
Filed under Outbound email.
From jurjen-gtm-engineer/gtmskills · 55 skill entries · 0 · pushed 2026-10-04
What it does when it runs
Analyze what a job title emphasizes to personalize outreach by role
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/jurjen-gtm-engineer/gtmskills.git /tmp/gtmskills git -C /tmp/gtmskills sparse-checkout set "skills/role-focus" mkdir -p ~/.claude/skills/role-focus cp -R "/tmp/gtmskills/skills/role-focus/." ~/.claude/skills/role-focus/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from jurjen-gtm-engineer/gtmskills/blob/77dc0b3112dbf6cf906dfc3d526b6f7031bf964c/skills/role-focus/SKILL.md, which is licensed MIT (repository). 392 words, 5 headings.
Role Focus Analysis
You are analyzing what a specific job title/role emphasizes to enable role-based personalization.
Input
User provides:
- A job title (e.g., "CTO", "VP of Sales", "Director of Marketing")
- Optionally: company context or job description
Process
-
Analyze Role
Prompt Pattern:
For the role: [JOB TITLE] Describe what this role typically focuses on: 1. Primary responsibilities 2. Key metrics they're measured on 3. Common pain points 4. What they care about when evaluating solutions 5. Decision-making authority (budget, team, strategy) -
Generate Personalization Angles
Based on role focus, suggest:
- Opening lines that resonate
- Pain points to reference
- Metrics to mention
- Tone adjustments
-
Output Format
Role: [Job Title] Primary Focus: - [Focus area 1] - [Focus area 2] Key Metrics: - [Metric 1] - [Metric 2] Common Pain Points: - [Pain 1] - [Pain 2] Decision Authority: - Budget: [Yes/No/Influence] - Team: [Size/scope] - Strategy: [Sets/Executes/Influences] Personalization Angles: - Opening: "As a [role], you're likely focused on [focus area]..." - Pain reference: "Many [roles] tell us [pain point]..." - Metric hook: "If [metric] is a priority..."
Example
Input: CTO
Output:
Role: CTO
Primary Focus:
- Technology strategy and architecture
- Engineering team leadership
- Technical debt vs. innovation balance
- Security and compliance
- Build vs. buy decisions
Key Metrics:
- System uptime/reliability
- Engineering velocity
- Technical debt ratio
- Security incident rate
- Time to market for features
Common Pain Points:
- Scaling infrastructure with growth
- Hiring and retaining engineers
- Legacy system modernization
- Balancing security with speed
- Vendor sprawl and integration complexity
Decision Authority:
- Budget: Yes (technology stack)
- Team: Large (engineering org)
- Strategy: Sets technical direction
Personalization Angles:
- Opening: "As a CTO, you're likely focused on scaling your tech infrastructure while managing complexity..."
- Pain reference: "Many CTOs tell us vendor sprawl is eating into their team's productivity..."
- Metric hook: "If engineering velocity is a priority, you might find this interesting..."
Related Skills
/clean-job-titles- Standardize verbose titles first/ideal-customer-profiles- Match role to ICP/pain-qualified-segment- Role-specific pain indicators
Examples are illustrative. Company names, prices and numbers in them are placeholders or may be out of date, so check the live source before you rely on any detail.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- playbook-new-in-role by growthenginenowoslawski · 739
- playbook-new-in-role by automatewithuday · 1
Need help setting it up?
This page tells you what role-focus does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.