Design a Focused Developer Relations Charter
Developer relations teams can spread limited capacity across activities without a clear business purpose. This skill guides interviews and decisions into a focused, reviewable charter.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "devrel-strategy" from https://skillstore.io/skills/samber-devrel-strategy.md and its manifest at https://skillstore.io/api/skills/samber-devrel-strategy/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "devrel-strategy". Illustrative scenario: one advocate, strong signups, weak second-use activation, and a ten-week executive review deadline.
Expected outcome:
Using "devrel-strategy". Illustrative scenario: enterprise technical evaluations stall; the revenue leader sponsors two DevRel practitioners.
Expected outcome:
All 39 static findings are false positives from business terminology, Markdown formatting, and related-skill references. No evidence found of executable commands, reconnaissance, data exfiltration, or prompt injection in the five reviewed files. The skill requests task-context persistence and optional public-source browsing, both related to its strategy workflow.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/samber-devrel-strategy/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/samber-devrel-strategy?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/samber-devrel-strategy?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-devrel-strategy/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/samber-devrel-strategy.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>samber. (2026). devrel-strategy security audit report (audit version 1) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/samber-devrel-strategy/audits/1@techreport{samber-samber-devrel-strategy-2026,
author = {samber},
title = {devrel-strategy security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-devrel-strategy/audits/1},
note = {Author version 1.0.1}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "devrel-strategy security audit report (audit version 1)"
version: "1.0.1"
type: report
authors:
- name: "samber"
date-released: "2026-10-25"
url: "https://skillstore.io/skills/samber-devrel-strategy/audits/1"
identifiers:
- type: other
value: "skillstore:samber-devrel-strategy:audit:1"
description: "Skillstore immutable audit report identifier"
Identify the sponsor, audience, initial priorities, and capacity limits before committing to new developer relations activities.
Replace an expanding activity list with a small set of funded initiatives, clear exclusions, and a justified next capability.
Connect program investment to observable developer problems and prepare an executive narrative with review dates and unresolved assumptions.
We are starting DevRel for [product] with [team capacity]. Interview me one question at a time to establish our funding driver and constraints.
Our sponsor wants [outcome] by [date]. Developers struggle at [journey step]. Compare feasible program archetypes for [capacity] and explain their trade-offs.
Our chosen direction is [archetype], with initiatives [list]. Compare sourcing options, retain credibility-sensitive work internally, and propose the next capability with its trigger.
Using [program context], develop our charter section by section. Check goal traceability, capacity, sourcing, exclusions, and review triggers. Label assumptions and adjustable baselines.
Author
samberLicense
MIT
Author version
v1.0.1
Skillstore revision
r1
Ref
bd544b4eceb0db06e15e5c6d3d9859517aa12806
Maintenance freshness
10/25/2026
Usage
0 downloads · 0 views
File structure
Write Clear Go Documentation
Go projects often have incomplete comments, examples, and contributor guidance that slow adoption and maintenance. This skill provides structured guidance for writing, reviewing, and organizing documentation that matches Go conventions.
Optimize Go Performance With Profiling
Go services often slow down from allocations, GC pressure, I/O waits, or inefficient hot paths. This skill maps profiling signals to focused Go performance fixes and benchmark validation.
Stay Current with the Go Ecosystem
Go developers can lose time sorting through scattered news, communities, and learning sources. This skill provides a focused directory and practical update routine.
Build Go Collection Pipelines with samber/lo
Manual Go collection transformations can become repetitive and difficult to optimize. This skill applies samber/lo helpers while explaining package choice, compatibility, errors, and performance tradeoffs.
Build Reliable Go CLI Commands
Go CLI projects often become inconsistent around command structure, validation, hooks, output, and tests. This skill provides practical Cobra patterns for predictable commands and maintainable test suites.
Improve Go Error Handling
Go error paths often lose context, duplicate logs, or expose internals. This skill gives Claude, Codex, and Claude Code concrete rules for safer Go errors.
Build Healthy Online Communities
by ncklrs
Community teams often lack a structured plan for activation, engagement, governance, and measurement. This skill provides practical frameworks for building sustainable member programs.
Draft and Schedule Social Posts with TimeToPost
by melmayssonowen
Managing platform-specific posts requires consistent wording, account selection, and approval. This skill guides TimeToPost MCP drafting, timing recommendations, and scheduling after explicit user approval.
Plan a Product Launch That Builds Momentum
by coreyhaines31
Launch planning becomes difficult when teams lack a clear sequence, audience strategy, and readiness criteria. This skill creates a phased plan from validation through post-launch adoption.
Manage Gmail with Google Workspace CLI
by googleworkspace
Managing Gmail through API commands requires accurate resource names and parameters. This skill guides Claude and Codex through supported Gmail CLI workflows.
Build a compliant email reactivation program
by aaron-he-zhu
Lapsed subscriber lists can reduce deliverability and create consent risk. This skill designs a staged win-back program with fresh consent signals and clear suppression outcomes.
Design a lifecycle email sequence
by aaron-he-zhu
Email teams often lack a clear lifecycle map and send too frequently. This skill creates flow plans with timing, exits, and safeguards before copywriting begins.