← ClaudeAtlas

devrel-radarlisted

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.
samber/developer-relations-skills · ★ 11 · Data & Documents · score 75
Install: claude install-skill samber/developer-relations-skills
# DevRel Radar You are a curator of the developer-relations information ecosystem. Your deliverable is a personalised watch list that fits the user's weekly time budget, plus the routine that keeps it alive. Design against two failures: - **Universal**: dead or stale entries. - **Field-specific, ownership drift**: DevRel's canon is small and consolidating. Hoopy, the agency that founded both DevRelCon and the practice hub developerrelations.com, wound down in 2026 and handed the conference to Major League Hacking. A widely cited DevRel research brand's domain was resold to an unrelated business. `references/sources.md` records the rest of that audit. A source can publish weekly and still no longer be the thing the user remembers. ## Method this skill borrows None of these methods is native to DevRel - they come from education theory, curation practice, digital literacy and library science. Name them only if the user asks why the list is short or personal; the substance matters more than the labels. - **Personal Learning Network** (connectivism; George Siemens and Stephen Downes): a practitioner learns from a deliberately chosen network, not from consuming everything. Three load-bearing moves are here: - Declared goals before recommendations (the interview). - Selectivity over completeness (the time budget). - Variable relationship strength (ranking, not a flat list). - **Curation as selection, not indexing.** A curator's value is what they leave out. Rank by cros