job-description
Skill8 starsChanged 8 months agoMITView on GitHub
When the user needs to write, review, or improve a job posting for a startup role.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- genspark-ai/genofficetheir own version, first seen Oct 25, 2026
- brianshepardpss/structured-hiringtheir own version, first seen Oct 2, 2026
- shawnpang/startup-founder-skillsword for word, first seen Mar 16, 2026
Other versions4 projects use a version of this.
Word for word · 1
- shawnpang/startup-founder-skills★ 331100% same
Edited · 0
None found.
Wrote their own version · 3
- genspark-ai/genoffice★ 12ksame name
- nisarth/claude-skills-store★ 1same name
- brianshepardpss/structured-hiring★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository49 other files it gives its agents.
- accelerator-applicationSkill
- architecture-designSkill
- board-updateSkill
- churn-analysisSkill
- cicd-setupSkill
- code-reviewSkill
- cold-outreachSkill
- community-discoverySkill
- competitive-analysisSkill
- competitor-monitoringSkill
- content-strategySkill
- contract-reviewSkill
- daily-product-digestSkill
- data-roomSkill
- earned-media-outreachSkill
- email-marketingSkill
- employer-brandSkill
- event-hostingSkill
- feedback-synthesisSkill
- founder-thought-leadershipSkill
- fundraising-emailSkill
- interview-kitSkill
- investor-researchSkill
- landing-pageSkill
- launch-strategySkill
- lead-scoringSkill
- market-researchSkill
- mvp-scopingSkill
- onboarding-flowSkill
- partnership-outreachSkill
- pitch-deckSkill
- prd-writingSkill
- privacy-policySkill
- process-docsSkill
- proposal-generationSkill
- review-miningSkill
- roadmap-planningSkill
- sales-scriptSkill
- security-reviewSkill
- sentiment-monitoringSkill
- seo-technicalSkill
- soc2-prepSkill
- social-contentSkill
- sourcing-outreachSkill
- startup-contextSkill
- support-docsSkill
- tech-stack-evalSkill
- terms-of-serviceSkill
- user-research-synthesisSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Gendered language: Avoid "ninja," "rockstar," "aggressive." Use tools like the Gender Decoder or Textio guidelines as a reference.
- Distinctive: line 49
Hidden role: If the job is actually three jobs, split it or be honest about the breadth.
- Distinctive: line 52
Use "you" instead of "the ideal candidate" to feel inviting rather than evaluative.
- Distinctive: line 59
If equity is offered, state the range in percentage or share count and mention the vesting schedule.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Job Description
When to Use
Activate when the user asks to create a new job posting, rewrite an existing one, or get feedback on a draft JD. Also activate when the user is preparing to hire for a new role and needs to define it clearly before sourcing candidates.
Context Required
- From startup-context: Company name, mission statement, stage/funding, tech stack (for eng roles), team size, remote/hybrid/onsite policy, benefits, and equity structure.
- From user: Role title, reporting structure, seniority level, key responsibilities, must-have vs. nice-to-have qualifications, compensation range (or willingness to include one), and hiring timeline.
Workflow
- Clarify the role — Ask the user what problem this hire solves. A JD should start from business need, not a generic title. Confirm level, scope, and team placement.
- Draft the hook — Write a 2-3 sentence opening that connects the company mission to why this role matters right now. Avoid generic openers like "We are looking for a rockstar..."
- Structure the body — Organize into five sections: Mission & Impact, What You'll Do (6-8 bullets), What You Bring (5-7 bullets split into must-have and nice-to-have), What We Offer, and How to Apply.
- Apply anti-pattern checks — Scan the draft for corporate jargon, unrealistic requirement stacking, gendered language, and exclusionary phrasing. Flag and fix.
- Add startup-specific framing — Emphasize ownership, speed of impact, equity upside, learning velocity, and access to leadership. These are startup advantages over big-co offers.
- Review comp and inclusivity — Ensure compensation transparency (range or "we'll share in first conversation"). Confirm language passes inclusive-language guidelines.
- Final polish — Tighten to a scannable length (400-700 words). Ensure the tone matches the company voice from startup-context.
Output Format
A complete, ready-to-post job description in markdown with the following sections:
- Title and location/remote line
- Opening hook (2-3 sentences)
- About Us (3-4 sentences)
- What You'll Do (bulleted list)
- What You Bring (must-haves and nice-to-haves, clearly separated)
- What We Offer (bulleted list)
- How to Apply (1-2 sentences with clear next step)
Frameworks & Best Practices
The HERO Structure
- Hook: Why this role matters to the mission right now
- Expectations: What the person will actually do day-to-day
- Requirements: What they genuinely need to succeed (not a wish list)
- Offer: What the company gives back (comp, equity, growth, culture)
Anti-Patterns to Avoid
- Requirement inflation: Listing 15+ requirements signals you don't know what you need. Keep must-haves to 4-5.
- Corporate jargon: "Synergy," "leverage," "fast-paced environment" are empty. Use concrete language.
- Gendered language: Avoid "ninja," "rockstar," "aggressive." Use tools like the Gender Decoder or Textio guidelines as a reference.
- Years-of-experience gates: "7+ years of React" excludes strong candidates. Prefer demonstrated capability over tenure.
- Hidden role: If the job is actually three jobs, split it or be honest about the breadth.
Inclusive Language Guidelines
- Use "you" instead of "the ideal candidate" to feel inviting rather than evaluative.
- Replace "requirements" with "what you bring" to reduce self-screening by underrepresented candidates.
- Include an explicit encouragement to apply even if not a 100% match (research shows this matters for women and minority applicants).
- State accommodation availability for the interview process.
Compensation Transparency
- Include a salary range. Listings with ranges get significantly more applicants.
- If equity is offered, state the range in percentage or share count and mention the vesting schedule.
- Name benefits explicitly rather than saying "competitive benefits package."
Startup-Specific Framing
- Impact: "You'll be one of the first 10 engineers shaping the product architecture."
- Ownership: "You'll own the entire lifecycle of features, from design through production monitoring."
- Equity: "We offer meaningful equity because early employees take real risk and deserve real upside."
- Growth: "As we scale from 10 to 50, you'll grow into a leadership role if you want it."
Related Skills
interview-kit— After posting the JD, design the interview loop and scorecards for this role.sourcing-outreach— Use the JD as the basis for personalized outreach messages to passive candidates.employer-brand— Ensure the JD tone and content align with your careers page and employer brand narrative.
Examples
Prompt: "We need to hire our first product designer. We're a 12-person B2B SaaS startup, Series A, remote-first."
Good output snippet:
# Product Designer — Remote (US/Canada time zones)
Join Acme as our founding designer and shape the product experience
from the ground up. You won't be handed a pixel-perfect spec — you'll
partner directly with engineering and customers to figure out what to
build and how it should feel.
## What You'll Do
- Own the end-to-end design process for our core B2B platform
- Run discovery calls with customers weekly to ground designs in real workflows
- Build and maintain our design system as the foundation for a future team
- Collaborate async-first with engineering using Figma and Loom
...Prompt: "Review this JD for red flags."
Good output snippet:
Issues found:
1. "Must have 10+ years in Python" — This filters out strong mid-career
candidates. Consider "deep fluency in Python" instead.
2. "Fast-paced environment" — This is vague. Replace with something
concrete: "We ship weekly and iterate based on customer feedback."
3. No salary range listed — Adding a range will increase your applicant
pool significantly.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

