devrel-radar

Builds a time-budgeted, verified watch list of developer-relations sources and practitioners.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/developer-relations-skills --skill devrel-radar-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devrel-radar
Source: https://github.com/samber/developer-relations-skills/tree/main/skills/devrel-radar
Command: npx skills add https://github.com/samber/developer-relations-skills --skill devrel-radar-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developer-relations practitioners drown in podcasts, newsletters, communities, and conferences, while the field's canon quietly goes stale: agencies wind down, domains get resold, and conferences change organisers. This Skill curates a personalised, time-budgeted watch list of DevRel sources, verifies each one for freshness and ownership, and installs a quarterly refresh routine so the list stays alive. ## Core Features & Use Cases - Interview-driven personalisation: A nine-question interview captures role, owned pillars, weekly time budget, mediums, ecosystem, segment, and event intent, then filters and ranks sources by value per attention-minute. - Freshness and ownership verification: Every candidate is classified as verified-active, stale, dead, or unverified using dated items and organiser checks, with rules for parked domains, resold URLs, 403s, and evergreen reference works. - Incentive disclosure and refresh routine: Each entry carries a what-they're-selling flag, and a quarterly refresh re-resolves URLs, drops unread sources, and re-ranks against new constraints. - Use Case: A new developer advocate with 90 minutes a week and a bike commute asks what to follow; the Skill halves commute audio costs, reserves a peer-community slot, covers every owned pillar, and delivers a dated watch list with a bench of substitutes. ## Quick Start Ask the assistant to build you a DevRel radar, stating your role, the pillars you own, your weekly time budget, and your preferred mediums.

Frequently Asked Questions about devrel-radar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a DevRel reading and listening list that fits my schedule?

Answer a short interview about your role, owned pillars, weekly time budget, and preferred mediums. The Skill filters verified sources, ranks them by value per attention-minute, fills your budget to about 90 percent, and reserves the rest for one peer community.

Which DevRel podcasts, newsletters, and communities are still active?

The Skill verifies each source by fetching its newest dated item and classifying it as active, stale, dead, or unverified. Podcast feeds are preferred over homepages for dates, and dead or resold domains are hard-removed rather than recommended.

Can I get a DevRel source list without web access?

Yes. The Skill delivers the list from its bundled, date-stamped source references with each entry's recorded status, states clearly that nothing could be re-verified, and hands you a four-step manual check with the freshness thresholds to apply yourself.

Why won't it rank DevRel people or channels by follower count?

Follower and subscriber counts measure reach in an adjacent audience and are largely unobservable in this field. The Skill ranks people by cross-surface recurrence, such as appearing as podcast host, conference speaker, and hub author, each tied to a fetchable verifying surface.

How often should a DevRel watch list be refreshed?

The Skill installs a quarterly refresh that re-resolves every URL, re-runs freshness and ownership checks, drops sources you stopped reading, and re-ranks against new constraints. The event calendar refreshes twice a year because CFP deadlines land months before events.

When should I not use this DevRel radar skill?

Do not use it to track a rival vendor; that is competitive analysis, which belongs to the devrel-competitor-analysis skill. It also does not replace a monitoring service, since nothing alerts you when a source dies between refresh runs.