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.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.
Utilisation de « devrel-strategy ». Illustrative scenario: one advocate, strong signups, weak second-use activation, and a ten-week executive review deadline.
Résultat attendu:
Utilisation de « devrel-strategy ». Illustrative scenario: enterprise technical evaluations stall; the revenue leader sponsors two DevRel practitioners.
Résultat attendu:
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.
Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.
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.
Auteur
samberLicence
MIT
Version de l’auteur
v1.0.1
Révision Skillstore
r1
Réf
bd544b4eceb0db06e15e5c6d3d9859517aa12806
Récence de maintenance
25/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
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.
Optimiser les performances de Go grâce au profilage
Les services Go ralentissent souvent à cause des allocations, de la pression du GC, des attentes d’I/O ou de chemins critiques inefficaces. Cette skill associe les signaux de profilage à des correctifs ciblés de performance Go et à une validation par benchmark.
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.
Améliorer la gestion des erreurs Go
Les chemins d’erreur Go perdent souvent le contexte, dupliquent les journaux ou exposent des détails internes. Cette skill donne à Claude, Codex et Claude Code des règles concrètes pour des erreurs Go plus sûres.
Build Healthy Online Communities
par 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
par 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
par 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.
Gérer Gmail avec Google Workspace CLI
par googleworkspace
Le travail avec Gmail nécessite souvent des commandes précises pour les messages, les threads, les libellés et les watches. Cette compétence guide Claude, Codex et Claude Code dans la structure des commandes gws Gmail et les workflows d’assistance.
Créer des programmes conformes de réactivation des abonnés
par aaron-he-zhu
Les abonnés inactifs peuvent nuire à la délivrabilité et accroître le risque de plaintes. Cette compétence conçoit un parcours de reconquête mesuré, avec renouvellement du consentement et règles de mise en suppression définitive.
Concevoir des séquences efficaces pour le cycle de vie des e-mails
par aaron-he-zhu
Des campagnes déconnectées entraînent un mauvais timing, des messages non pertinents et une lassitude des abonnés. Cette compétence conçoit des parcours coordonnés avec des déclencheurs, des branches, des sorties et des contrôles de fréquence clairement définis.