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.
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
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.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
正在使用「devrel-strategy」。 Illustrative scenario: one advocate, strong signups, weak second-use activation, and a ten-week executive review deadline.
預期結果:
正在使用「devrel-strategy」。 Illustrative scenario: enterprise technical evaluations stall; the revenue leader sponsors two DevRel practitioners.
預期結果:
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.
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
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.
作者
samber授權
MIT
作者版本
v1.0.1
Skillstore 修訂
r1
引用
bd544b4eceb0db06e15e5c6d3d9859517aa12806
維護新鮮度
2026/10/25
使用量
0 次下載 · 0 次瀏覽
檔案結構
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.
透過剖析最佳化 Go 效能
Go 服務經常因記憶體配置、GC 壓力、I/O 等待或低效率的熱點路徑而變慢。此技能會將剖析訊號對應到聚焦的 Go 效能修正與基準測試驗證。
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.
改善 Go 錯誤處理
Go 錯誤路徑經常遺失脈絡、重複記錄日誌，或暴露內部實作。這項技能為 Claude、Codex 和 Claude Code 提供具體規則，以實作更安全的 Go 錯誤處理。
Build Healthy Online Communities
由 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
由 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
由 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.
使用 Google Workspace CLI 管理 Gmail
由 googleworkspace
Gmail 工作經常需要針對郵件、對話串、標籤和 watch 的精確命令。此技能會引導 Claude、Codex 和 Claude Code 使用 gws Gmail 命令結構與輔助工作流程。
建立合規的訂閱者再啟用計畫
由 aaron-he-zhu
不活躍的訂閱者可能損害郵件送達率，並增加投訴風險。此技能會設計審慎的召回路徑，包括重新取得同意及最終抑制規則。
設計有效的電子郵件生命週期序列
由 aaron-he-zhu
彼此脫節的行銷活動會造成時機不佳、訊息不相關，以及訂閱者疲乏。此技能可設計協調一致的流程，並提供明確的觸發條件、分支、退出條件與頻率控制。