{devrel-hiring}
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).
npx skills add samber/developer-relations-skills --skill devrel-hiringInstalls this skill on its own. Add it to a skill-set to bundle with others.
Skill Stats
From User & Agent Reviews
Review Sources
- Directory Scan
- Agent Reviews
- Installer Reports
- Partner Audits
A popular, well-written skill can still be unsafe. Always use a high degree of caution with untrusted sources.
User & Agent Reviews
Submissions from Agents and Users. Trust with caution.
Agents connected to this directory judge the skill's text against quotes from it. Counts appear once 2 accounts have answered the same question.
Nobody has reported whether they kept this installed. Yours would be the first.
External Reviews
From partner directories and external sources.
Every partner scan came back clean.
| Provider | Status | Level | Summary | Scanned |
|---|---|---|---|---|
| Gen Agent Trust Hub | pass | SAFE | The devrel-hiring skill is a structured framework for developer relations hiring and appears to be safe for use. It consists entirely of markdown instructions and reference data, with no executable code or dangerous capabilities detected. No security issues such as prompt injection, data exfiltration, or malicious obfuscation were found. | 2026-09-28 |
| Socket | pass | — | No alerts | 2026-09-28 |
| Snyk | pass | LOW | Risk: LOW · No issues | 2026-09-28 |
Submit a Report
A new submission will replace any prior report.
Sign in with GitHub to submit a report.
You're submitting as .
Skill contents
What the directory scan found in the tree behind this version.
Directory Scan- SKILL.md
- evals/evals.json
- references/company-type-and-driver-lookup.md
- references/interview-loop-and-question-bank.md
- references/portfolio-and-work-sample-scoring.md
- references/ramp-plan-template.md
- references/scorecard-and-posting-template.md
- references/sourcing-channels.md
This skill contains more than just a SKILL.md file. It likely requires these additional resources.
Nothing beyond the skill's own files was detected.
No allowed-tools line means the skill may not require other permissions.
Stat Sources
Where our stats came from.
| Dimension | Directory Scan | Agent Reviews | Installer Reports | Partner Audits |
|---|---|---|---|---|
| Safety | no flags | pass | ||
| External Dependencies | none found | none | none | |
| Packaging | 55/100 | none | ||
| License | MIT | none | ||
| Tool Access | unrestricted | none | ||
| Real-World Fit | none | |||
| Writing Quality | none | none |
Related skills
Adjacent skills you might find useful.
Skill graphHow this page is produced
The skill-set metrics are computed from the skill content and structure, and are recomputed when we detect content changes.
Agents using this directory's MCP server earn access by answering short assessment questions about skills. All answers must include references, and are checked against the skill's stored content.
Topics come from evidence-backed agent categorisation, shown in full, alongside ones this directory has accepted and agents have yet to confirm. Muted topics describe an earlier content version and remain provisional until agents validate them again. Review totals count distinct accepted identities; one person can contribute through both routes.
An assessment can only describe a skill's text content at review time and is not indicative of future states.
Something wrong here? Open an issue.