# DevRel Artifacts Must Match How Developers Consume Information ## Claim The effective DevRel artifact tracks how developers actually discover and consume tools in a given era, not what channel produced results last cycle. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when developer attention genuinely shifts at a platform level — conference talks when developers attended conferences, blog posts when they searched Google, Agent Skills now that they work through coding agents. - Breaks when the claimed new consumption pattern hasn't reached critical mass yet; chasing a channel before developers actually use it produces artifacts nobody finds. - Does not by itself tell you which specific registry or platform to bet on — only that the artifact type, not just its content, needs to match the era. ## Evidence Liran Tal's argument: DevRel cycled through four eras (pre-2020 conference golden age, 2020 pandemic content pivot, 2022 ZIRP revenue pivot, 2024-2026 AI disruption), and in each era the artifact that actually reached developers changed shape, not just its topic. His concrete 2026 claim is that Agent Skills published to registries like skills.sh or tessl.io are becoming the new consumable artifact, displacing blog posts, because developers increasingly discover and evaluate tools through coding agents rather than search or talks. ## Links - [[3. Resources/Permanent Notes/DevRel Maturity Is a Five-Stage Progression Not a Binary State]] — because contrasts: that note periodizes DevRel maturity by organizational stage, this one periodizes it by artifact-audience fit; worth reconciling whether they're describing the same underlying dynamic from two angles - [[3. Resources/MOCs/DevRel MOC]] — because applies-in: direct strategic input to how DevRel content/artifact decisions get made - [[3. Resources/Permanent Notes/A Pitch Earns Coverage by Handing the Reporter Something No Competitor Can]] — applied in: a pitch works when it offers a fact, quote or experience nobody else can (Purdy). ## Tests / falsifiers - Track skills.sh and tessl.io adoption metrics over the next two quarters — if developer discovery through these registries stays negligible, the specific claim (not the general pattern) is wrong for this cycle. - Compare install/adoption rates for developer tools that publish Agent Skills vs. those that only publish documentation, controlling for company size and product category. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/DevRel in 2026 (Thematic Shifts, Product-Centric Advocacy, Coding Agents)]] — reports the four-era history and the Agent Skills claim.