devrel-radar skill (samber): a time-budgeted DevRel watch list

Builds a time-budgeted list of DevRel podcasts, newsletters, communities and events, plus a routine to keep it fresh.

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

devrel-radar builds a personalised watch list of developer relations podcasts, newsletters, practice hubs, communities, conference calendars, data reports and practitioners. After an interview of nine questions asked one at a time, Claude drops what your constraints rule out, ranks the rest by value per attention-minute and fills your weekly time budget. Each entry carries a "what they're selling" flag and a status. It starts from a date-stamped list in references/sources.md and, where Claude can browse, re-checks each source before recommending it.

Good for

Developer advocates and community managers staying current
People catching up on DevRel before a first role
Open-source maintainers doing DevRel alone

Install devrel-radar

Claude Code

Copy this prompt.

Install the devrel-radar 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-radar 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

Builds a personalised, time-budgeted watch list of developer-relations information sources - DevRel podcasts, newsletters, practice hubs, peer communities, conference calendars, ecosystem data reports and practitioners worth following - plus the routine that keeps it verified and fresh. Use whenever a developer advocate, community manager, DevRel lead or OSS maintainer asks for a DevRel radar, how to stay current on developer relations, which DevRel podcasts, newsletters or Slack communities deserve their time, which developer conferences to attend or speak at, who to follow in DevRel, or to refresh a radar built earlier - even if they only say they feel out of the loop. Not for tracking a rival vendor - use samber/developer-relations-skills@devrel-competitor-analysis.

Sections in SKILL.md

Method this skill borrows
Interview
Pillar coverage
B2B and B2C scope
Incentive disclosure
Video
Personalisation workflow
Freshness and ownership check
Periodic refresh routine
Output shape
Failure modes
Measurement
References

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,814 (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: 5 files in the git tree: SKILL.md, 3 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

Nine questions on role, pillars, time, goal, mediums, exclusions, ecosystem, buyer, events
Time, goal, exclusions and events are asked up front because they decide the ranking.
Read · Interview
One verified source per pillar you own, none for pillars you do not
A community-heavy list handed to a docs owner counts as a failed deliverable.
Read · Pillar coverage
Flags what each source sells; does not filter conflicted ones out
The Developer Relations Foundation is named as the one vendor-neutral practice body.
Read · Incentive disclosure
Twelve steps from filtering to confirming the list with you
Includes deleting ruled-out sources, ranking by value per attention-minute, filling about 90 percent of your budget and reserving the rest for one peer community.
Read · Personalisation workflow
Classifies each source as verified-active, verified-stale, dead or unverified
Needs browsing. Without it, Claude delivers the list from the bundled file and says it could not re-verify.
Network · Freshness and ownership check
A quarterly refresh in seven steps; schedules it if your tool supports that
Otherwise it tells you to set a reminder and rerun the skill.
Write · Periodic refresh routine
Weekly core, monthly, annual and bench sections, with totals and a Dropped line
Offers an OPML file of the feed-bearing entries as an optional second artifact.
Write · Output shape

From the official docs

Permissions

Low risk

devrel-radar 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
It may browse the web and schedule a recurring refresh
SKILL.md says to fetch each source to find its newest dated item, and to install a quarterly refresh if the harness supports scheduled routines. It names no scheduler or command, so the mechanism is whatever your harness provides; otherwise it tells you to set a reminder. Decline the schedule if you do not want one. 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 may open the sources it recommends, if your tool allows browsing Claude may schedule a quarterly refresh if your tool supports scheduled routines Writes devrel-context.md when memory lives in a file

Questions

What does devrel-radar do?

It builds a short, personal list of DevRel sources to follow: podcasts, newsletters, practice hubs, communities, events and people. The list fits your weekly time budget and comes with a routine to keep it current.

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. The box shows the whole-set routes the README documents.

Is the source list up to date?

It carries a date on each entry. SKILL.md tells Claude to flag the list for re-verification if it is more than about six months old, to re-check sources when it can browse, and to say so plainly when it cannot.

Does it set up a recurring task?

Possibly. SKILL.md says that if your harness supports scheduled routines, Claude should install a quarterly refresh (its own default cadence, not a standard). It names no scheduler, command or tool for this, so what gets created depends on what your harness offers. If it has none, Claude tells you to set a recurring reminder and rerun the skill. Say no if you do not want a scheduled task.

How is it different from devrel-career?

devrel-radar only curates what to read, watch and attend. devrel-career covers landing and growing a DevRel role. radar's SKILL.md points to career for that.

Is it safe to install?

The skill bundles no scripts. It may browse the web to check sources and may offer to schedule a refresh. 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-radar

samber/developer-relations-skills skills.sh

Sources

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

Show all 4

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