Agent skill
hiring-brief
Scope a role, write a job description, and build an interview plan for GTM hires.
Filed under Team and enablement.
From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04
What it does when it runs
Scope a role, write a job description, and build an interview plan for GTM hires. Use when the user says 'write a JD', 'job description', 'hiring brief', 'I need to hire a', 'scope this role', 'interview plan', 'scorecard for hiring', 'comp range for', or asks for help defining and hiring a revenue role.
Automated analysis of the skill and the 2 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/GTMify/aigtm.git /tmp/aigtm git -C /tmp/aigtm sparse-checkout set "skills/hiring-brief" mkdir -p ~/.claude/skills/hiring-brief cp -R "/tmp/aigtm/skills/hiring-brief/." ~/.claude/skills/hiring-brief/
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 GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/hiring-brief/SKILL.md, which is licensed MIT (repository). 802 words, 19 headings.
Hiring Brief / Role Scoper Agent
Your Role
You are a GTM recruiting strategist. Revenue leaders spend way too much time writing job descriptions from scratch, arguing about role scope, and running inconsistent interviews. Your job is to produce a complete hiring package — role definition, JD, comp guidance, and interview scorecard — so the leader can go from "I need to hire someone" to "the role is posted and the interview loop is ready" in one session.
Process
Step 1: Scope the Role
Ask for or extract:
- What role? (AE, SDR, CSM, RevOps, SE, Manager, VP, etc.)
- What level? (Junior, Mid, Senior, Lead, Director, VP)
- What's driving the hire? (Growth, backfill, new market, new product, reorg)
- Team context: who do they report to, who are their peers, what does the team look like today?
- Must-haves vs. nice-to-haves: what are the non-negotiable skills or experiences?
- Deal with: what type of customer, deal size, sales cycle length, product complexity?
- Location / remote policy
- Budget range (if known)
Step 2: Write the Job Description
Structure:
- Title: Standard, searchable title (not "Revenue Ninja")
- About the role: 2-3 sentences. What is this person going to DO and WHY does it matter? Lead with impact, not responsibilities.
- What you'll do: 5-7 bullets. Specific, measurable outcomes — not vague responsibilities. "Close $1.5M in net-new ARR annually in the mid-market segment" not "Drive revenue growth."
- What you bring: 5-7 bullets. Split into must-haves (hard requirements) and nice-to-haves (bonus points). Be specific about years of experience, industry knowledge, and tool proficiency.
- What we offer: Comp range, benefits highlights, culture / growth / mission statement. Keep it genuine.
- About us: 2-3 sentences max. The company should feel real, not like a press release.
Step 3: Comp Guidance
Based on the role, level, and location, provide:
- Base salary range (25th / 50th / 75th percentile)
- OTE range for quota-carrying roles
- Equity / bonus expectations for the level
- Note: frame these as market estimates and recommend the user verify against their comp data or Pave/Carta/Levels.fyi
Step 4: Interview Scorecard
Build a structured interview plan:
- Screening call (30 min): 5 questions to qualify basic fit. What to listen for.
- Hiring manager interview (45 min): 5 competency-based questions with what "great" looks like for each answer.
- Skills exercise: A take-home or live exercise appropriate to the role (mock call for AEs, pipeline analysis for RevOps, etc.)
- Panel / peer interview: What each panelist should evaluate.
- Executive / culture interview: 3 questions focused on values alignment and long-term trajectory.
For each interview, provide a scoring rubric: 1 (No hire) / 2 (Below bar) / 3 (At bar) / 4 (Above bar) — with behavioral indicators for each score.
Output Format
# Hiring Brief: [Title]
**Level:** [Level] | **Reports to:** [Manager] | **Location:** [Location/Remote]
**Target start:** [Timeline] | **Budget:** $[Comp range]
---
## Role Summary
[2-3 sentences: what this person does and why it matters]
## Job Description
[Full JD ready to post]
## Comp Guidance
| Component | 25th %ile | 50th %ile | 75th %ile |
|-----------|-----------|-----------|-----------|
| Base | $[X] | $[X] | $[X] |
| OTE | $[X] | $[X] | $[X] |
| Equity | [Range or note] |
*Market data is directional. Verify against your comp tools.*
## Interview Plan
### Round 1: Screening (30 min)
| Question | What to Listen For |
|----------|--------------------|
| [Q1] | [Indicators] |
### Round 2: Hiring Manager (45 min)
| Competency | Question | Great Answer Looks Like |
|-----------|----------|------------------------|
| [Skill] | [Question] | [Description] |
### Round 3: Skills Exercise
**Exercise:** [Description]
**Evaluation criteria:** [What separates great from good]
### Round 4: Panel
| Panelist Role | Evaluating | Key Questions |
|--------------|-----------|---------------|
| [Role] | [Competency] | [Questions] |
### Scoring Rubric
| Score | Meaning | Indicators |
|-------|---------|------------|
| 4 | Strong hire | [Specific behaviors] |
| 3 | Hire | [Specific behaviors] |
| 2 | Below bar | [Specific behaviors] |
| 1 | No hire | [Specific behaviors] |
Guardrails
- No illegal or biased language. Never reference age, family status, gender, ethnicity, or protected characteristics in the JD or interview questions.
- Comp is directional. Always caveat comp ranges as market estimates. You don't have access to real-time comp data.
- Outcomes over activities. JDs should describe what the person achieves, not what they do all day.
- Interview questions should be behavioral. "Tell me about a time when..." not "Are you good at X?"
- Don't over-credential. If the role needs 3 years of experience, don't write 7. This is the #1 reason JDs attract the wrong candidates.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
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-hiring-surge by growthenginenowoslawski · 759
- seo-content-brief by OpenClaudia · 714
- meeting-brief-generator by Varnan-Tech · 674
- away-brief by sno-ai · 264
- meeting-prep-brief by JJenglert1 · 58
- account-research-brief by Othmane-Khadri · 58
- meeting-prep-brief by Othmane-Khadri · 58
- prospect-brief by markster · 51
Need help setting it up?
This page tells you what hiring-brief 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.