devrel-hiring skill (samber): build the DevRel posting, scorecard and interview loop

Builds a DevRel job posting, scorecard, interview loop, portfolio score and 30-60-90 ramp for a hiring manager.

Installs: 12.9K; on skills.sh
Stars: 7; on GitHub
Files: 7; besides SKILL.md
Updated: Nov 2026; last repo commit

devrel-hiring helps an employer hire into a developer relations role. After an interview of up to ten questions, Claude builds four artefacts in order: a role scorecard and posting, an interview loop with a question bank, a portfolio and work-sample evaluation, and a 30-60-90 ramp plan. It checks the posting against two named failure patterns, "gatekeeper" and "pit trap", and asks you to validate each artefact before the next. Candidates should use devrel-career instead.

Good for

Hiring managers opening a developer advocate or community manager role
Founders hiring their first DevRel person
Recruiters and panels designing a DevRel interview loop

Install devrel-hiring

Claude Code

Copy this prompt.

Install the devrel-hiring skill in Claude Code. Run this command:

/plugin marketplace add samber/developer-relations-skills
/plugin install developer-relations-skills@developer-relations-skills

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Install the whole set, not one skill: the README says the skills reference each other, so picking one leaves those pointers going nowhere. The repo tree holds 93 skill folders (the kickoff skill's text says 65). Fourteen of them bundle .py or .sh files; devrel-hiring bundles none. The tree holds no hooks, agents or MCP config files.

From the project README. Source.

What's in the skill

When it loads

Employer-side DevRel hiring - writes the job posting and outcome-based scorecard, designs the interview loop and question bank across the field's formats (presentation round, take-homes, DevRel-opinion round), scores a portfolio against the six-signal rubric, designs a paid work sample instead of unpaid spec work, and builds a 30-60-90 ramp anchored on a friction log. Splits by company type and funding driver. Use when the user asks how to hire a developer advocate, write a DevRel job posting, design a loop for a community manager or educator, evaluate a candidate's portfolio, or plan a ramp. Do NOT use for candidate-side prep (samber/developer-relations-skills@devrel-career) or org design (samber/developer-relations-skills@devrel-team-structure).

Sections in SKILL.md

Interview
Reading the answers
Workflow
Company type and funding driver
Quality gate
Common failure modes
Reference

Key facts

Author: Samuel Berthe (named in SKILL.md metadata and the plugin manifest)
License: MIT (LICENSE file, SKILL.md and plugin.json agree)
Installs on skills.sh: 12,868 (Nov 2, 2026)
GitHub stars: 8 for the whole samber/developer-relations-skills repo (Nov 2, 2026)
Last repo commit: Nov 1, 2026
Audits on skills.sh: Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass
What it includes: 8 files in the git tree: SKILL.md, 6 reference files and evals/evals.json. No scripts.
Part of: The developer-relations-skills plugin: 93 skill folders in the git tree
Works in: Claude Code and Claude.ai plugin marketplaces, Codex, Cursor and Gemini CLI, as the README documents

What it includes

Up to ten questions; the last three (deadline, reuse, effort) reorder the plan
Company type, role target, funding driver, go-to-market motion, coding depth, team stage, compensation stance, deadline, one-off or reusable, and interviewer hours.
Read · Interview
A mission line, 3-8 quantified outcomes and 5-7 weighted competencies
The posting is self-audited against the gatekeeper and pit-trap patterns before it goes out.
Write · Artefact 1: scorecard and posting
Picks 3-5 formats and writes a question bank mapped to the scorecard
Interviewers score independently with an evidence note before any debrief, and scores are combined mechanically against pre-set weights.
Write · Artefact 2: interview loop
Scores shipped public work on a six-signal rubric
A thin portfolio gets a scored, paid work sample instead of unpaid spec work.
Write · Artefact 3: portfolio and work sample
Day 30 friction log, day 60 shipped artefact, day 90 owned program slice
Anchored on the friction log, which devrel-career recommends as a portfolio piece.
Write · Artefact 4: 30-60-90 ramp
Eleven checks the four artefacts must pass before delivery
Includes: no unpaid spec work when a public portfolio exists, and a real compensation stance instead of "competitive".
Read · Quality gate
Ten defects, each with one mandatory fix
Examples: gatekeeper posting, pit-trap posting, a generic engineering job template, and one blended gut score after a debrief.
Read · Failure modes

From the official docs

Permissions

Low risk

devrel-hiring is interview and planning instructions with no scripts, and it may save notes to devrel-context.md. Our advice: check that file before you commit it.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It may save notes to devrel-context.md
SKILL.md tells Claude to keep task and project context in devrel-context.md when memory lives in a file, or in the memory system your tool already uses. Check the file before you commit it. github.com
The whole-set install adds 93 skills, 14 with scripts
The README says to install every skill. The git tree has 93 skill folders, and 14 of them hold .py or .sh files. This skill bundles no scripts and the tree holds no hooks, agents or MCP config files. github.com

Technical details

Turning on read-only	SKILL.md describes no read-only mode.
Sign-in and keys	SKILL.md names no account, key or token.
Scopes	Claude drafts a posting, scorecard, question bank and ramp plan in the conversation Candidate details you paste, such as resumes or portfolio links, go into the conversation Writes devrel-context.md when memory lives in a file

Questions

What does devrel-hiring do?

It builds the four documents a hiring manager needs for a DevRel role: a scorecard and posting, an interview loop with question bank, a portfolio and work-sample evaluation, and a 30-60-90 ramp plan. It works through them one at a time with your sign-off.

How do I install it?

Use the install box at the top. The README says to install every skill in the repo, because the skills point to each other and a single install leaves those pointers going nowhere. The box shows the whole-set routes the README documents.

How is it different from devrel-career?

devrel-hiring is for the employer: posting, scorecard, loop and ramp. devrel-career is the candidate's side of the same table: portfolio, interview prep and offer evaluation. Each tells you to switch if you asked the wrong one.

Does it tell me what pay-transparency law applies?

No. SKILL.md says never to invent a jurisdiction's legal requirement and to confirm current pay-transparency rules for the hiring location before publishing.

Does it need an API key?

SKILL.md names no API key, account or script. The skill folder holds Markdown and one evals file, with no scripts.

Is it safe to install?

The skill bundles no scripts. It works from what you tell Claude, so candidate names or resumes you paste go into your conversation. The whole-set install adds 93 skills, some of which bundle scripts; the permissions section has the count.

Information

updated Nov 2, 2026

Repository: samber/developer-relations-skills
Folder: skills/devrel-hiring

samber/developer-relations-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4

devrel-hiring SKILL.md · github.com
README · github.com
LICENSE · github.com
devrel-career file · github.com