Vertical Hr Recruiting
Domain-knowledge primer for the HR & recruiting vertical (ATS, onboarding, workforce scheduling, engagement). Applied by architect/pm during spec authoring so they aren't naive about hiring pipelines, the admitted offer→onboard data-carry gap, EEO/I-9 compliance, and shift-coverage rules. Stops the four products from being specced as generic CRUD when the domain has hard legal and workflow constraints.
Install
npx skills add jeremybrasher/grokbot-skills --skill vertical-hr-recruitinggit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/vertical-hr-recruiting ~/.claude/skills/vertical-hr-recruitingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Vertical: HR & recruiting — don't spec it naive The incumbents (Workable, BambooHR, Greenhouse, Lever, Zoho Recruit, Manatal) have trained buyers to expect a hiring pipeline that *works*. A generic CRUD app fails the moment it meets EEO law, I-9 timing, or the offer→onboard handoff. **Read this before speccing any of the four products — the domain has hard constraints, not just forms.** ## 1. Domain vocabulary - **ATS** — applicant tracking system; the system of record for hiring. - **Requisition (req)** — an approved open role. Hiring happens *against a req*, not in a vacuum. Reqs have an approval workflow (hiring manager → finance/HR). - **Pipeline stages** — `applied → screen → interview → offer → hired` (plus `rejected` / `withdrawn`). Stages are **configurable per req** — engineering and sales hire differently. - **Candidate vs applicant** — an *applicant* applied to a specific req; a *candidate* is a person in your talent pool who may map to many applications over time. Don't conflate them. - **Sourcing** — proactively finding candidates (vs inbound applications). - **Structured interview + scorecard** — pre-defined questions + a rubric each interviewer scores. Reduces bias and legal exposure vs freeform notes. - **Offer letter** — formal terms; triggers the offer→onboard transition on acceptance. - **EEO data** — voluntary race/gender/veteran/disability self-ID, collected for reporting, **segregated from hiring decisions** (see §2).
Details
- Skill name
vertical-hr-recruiting- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/vertical-hr-recruiting/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Vertical Hr Recruiting skill do?
Domain-knowledge primer for the HR & recruiting vertical (ATS, onboarding, workforce scheduling, engagement). Applied by architect/pm during spec authoring so they aren't naive about hiring pipelines, the admitted offer→onboard data-carry gap, EEO/I-9 compliance, and shift-coverage rules. Stops the four products from being specced as generic CRUD when the domain has hard legal and workflow constraints.
How do I install the Vertical Hr Recruiting skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill vertical-hr-recruiting. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Vertical Hr Recruiting popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Vertical Real Estate
38jeremybrasher/grokbot-skills
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain wedge, and the must-model entities. Applied during spec authoring so the architecture reflects how real estate actually works — not a generic CRUD assumption.
Vertical Home Services
38jeremybrasher/grokbot-skills
Domain-knowledge pack for home & field services (HVAC, plumbing, cleaning, landscaping) — the trades vocabulary, non-obvious pricing/dispatch rules, and field-crew realities a builder must know so home-services products aren't speced naive. Covers the four products this niche ships (dispatch, quoting, field-booking, reviews), how they wedge against ServiceTitan / Jobber / Housecall Pro, and the must-model entities (price book, membership, job window, multi-option quote). Applied by architect/pm during spec authoring so the schema and flows reflect how a trades shop actually runs, not a generic
Vertical Retail
38jeremybrasher/grokbot-skills
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder and cart recovery), the must-model entities (Product→Variants matrix, channel-aware InventoryLevel, ReorderRule, PricingRule, AbandonedCart), and what a naive build gets wrong (no variant model, single-channel inventory, reorder without lead-time/safety-stock). Applied by architect/
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.