Install
$ agentstack add skill-getclera-claude-skills-hiring-brief ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Hiring Manager Brief Creator
What This Skill Does
Produces the intake brief that should exist before any search starts — the document that aligns the recruiter and hiring manager on exactly who they're looking for, how they'll find them, and how they'll evaluate. Most bad searches fail at intake: the recruiter sources against a fuzzy target and wastes weeks. This skill forces the target into focus up front.
Process
- Gather the role context: title, team, why the role exists, what success looks like in 6
months, who it reports to, comp band, location/work type.
- Define the ideal candidate profile: must-haves vs. nice-to-haves (kept honest and short), the
shape of the right person (background, slope, the problem they've solved before), and explicit anti-patterns (who looks right but isn't).
- Draft the sourcing strategy: where this person likely is, search angles, target companies,
outreach approach.
- Outline the interview plan: the loop, who's on the panel, what each stage assesses (tie to a
rubric), whether a work trial fits.
- Set the timeline: target dates for shortlist, first interviews, decision.
How to Write a Good Brief
- Force the target into focus. The value is precision. "Someone who's done growth at an early
marketing-tech company and adapts fast" beats "a strong growth person."
- Name the anti-patterns. Defining who looks right but isn't (e.g., "someone who'll just
replay a prior playbook") saves more time than the must-have list.
- Keep must-haves honest. Every fake requirement narrows the funnel and slows the search.
- Tie evaluation to a rubric so the brief connects straight to scoring.
- Make it a working doc, not a formality — the recruiter should be able to start sourcing
directly off it.
Output Format
# Hiring Brief: [Role]
**Team · Reports to · Comp band · Location/type · Why now**
## Success in 6 months
[What this person will have accomplished if it's working.]
## Ideal Candidate Profile
**Must-haves (honest, short):** ...
**Nice-to-haves:** ...
**The shape:** [background / slope / problem they've solved before]
**Anti-patterns (looks right, isn't):** ...
## Sourcing Strategy
[Where they are, target companies, search angles, outreach approach.]
## Interview Plan
| Stage | Who | Assesses (rubric dimension) |
|---|---|---|
[Note whether a work trial fits.]
## Timeline
[Shortlist by · First interviews by · Decision by]
Brief Failure Checklist
A brief FAILS if it:
- ❌ Leaves the target fuzzy ("a strong X") instead of precise
- ❌ Omits anti-patterns, the highest-leverage part of intake
- ❌ Pads must-haves with fake requirements that narrow the funnel
- ❌ Has no sourcing angle the recruiter can act on immediately
- ❌ Defines an interview loop with no link to how candidates get scored
- ❌ Has no timeline, so the search drifts
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: getclera
- Source: getclera/claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.