Skip to content
SkilVault
Sign inGet started

devrel-team-structure

Signed by SkilVaultMIT

By samber · original, unchanged · published by SkilVault with credit

Designs the developer relations org - which function DevRel reports to (marketing, product, engineering, CEO, sales) and what that line starves, the shape (centralized, split, embedded, hub-and-spoke), the coverage map across advocacy, community, docs and education, the interlocks with product, docs, support and sales, and the trigger for the next re-org. Use whenever someone asks where DevRel should sit, who DevRel should report to, how to structure or restructure a devrel team, which devrel roles to staff at this size, whether to embed advocates in product teams, why devrel keeps getting pulled into other teams' work, or how devrel and docs divide ownership - even if they only say the team feels wrong. Not the budget split - use samber/developer-relations-skills@devrel-budget-allocation.

Version
v0.1.0
Size
91 KB
Updated
2026-11-20
$ skilvault read --manual devrel-team-structure

Your client verifies the signature before reading. This explicit manual read is available on every plan. Free automatically loads five chosen skills; paid plans automatically load relevant skills across the library.

Files in this version

  • SKILL.mdsha256 ac76de549436532bdfdd1c567b42fd4577d1392ee5a07c6427da40bf686e68b2
  • SKILVAULT_SOURCE.jsonsha256 f37f143a355f970d4503f4563ef2b015ffd5f5031cd62246b707b69574089308
  • THIRD_PARTY_NOTICES.mdsha256 0f1ba03669c66ed599c47b552fa20c7660ae44f067f7fe203a3aa6afdc0c08b0
  • evals/evals.jsonsha256 33610bb5e0471b5b3e86ce3398f136b42127f54c12a5d4173c8de80514890ffe
  • references/org-design-brief-example.mdsha256 23336c410dd5c9115d04c9f4135fbde938d31e224d6e88c230a41edf56bfa937
  • references/reporting-line-tradeoffs.mdsha256 7b39122ce10d02a30c2aacc3c1f6fb87f7a6e03c883ba2ca32e918ecd85a62c5
  • references/sourced-numbers.mdsha256 12c4332db9b94e67764669734984f4871d62277dac216316f5f301755a5f44b9
  • references/team-shapes-and-interlocks.mdsha256 3f9c4c47b63cafd00718a073701d4a2338be5cb2765252b7a1462005c61f437b

The client checks the signature and every file’s fingerprint before use.

Licence and notice

MIT License (MIT). Copyright (c) 2026 Samuel Berthe

The full licence text ships inside the package.

Show full licence text
Copyright (c) 2026 Samuel Berthe

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.