devrel-strategy
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-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «devrel-strategy». Illustrative scenario: one advocate, strong signups, weak second-use activation, and a ten-week executive review deadline.
Ожидаемый результат:
- Direction: enablement-first, subject to confirming the sponsor and capacity.
- Initial initiative: improve the quickstart. Owner: advocate. Signal: second successful use. Review: week eight.
- Sourcing: retain technical decisions and review internally; exclude a new agency pipeline because setup exceeds the deadline.
- Excluded: conference sponsorship and a new community venue until activation improves.
Использование «devrel-strategy». Illustrative scenario: enterprise technical evaluations stall; the revenue leader sponsors two DevRel practitioners.
Ожидаемый результат:
- Driver: sales enablement. Sponsor: revenue leader.
- Direction: evaluation-support for platform engineers whose deployments require an approver.
- Candidate initiatives: scoped proof-of-concept material, reference architectures, and reusable security and licensing answers.
- Next capability: technical writing, triggered by a sustained review backlog.
- Open question: establish the evaluation drop-off baseline before selecting a success target.
Аудит безопасности
Безопасно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.
Факторы риска
⚙️ Внешние команды (21)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/samber-devrel-strategy/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/samber-devrel-strategy?utm_source=security_passport_badge)Значок HTML
<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>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
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Цитата BibTeX
@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}
}CITATION.cff
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"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Start a funded program
Identify the sponsor, audience, initial priorities, and capacity limits before committing to new developer relations activities.
Refocus an overloaded team
Replace an expanding activity list with a small set of funded initiatives, clear exclusions, and a justified next capability.
Prepare for an executive review
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.
Лучшие практики
- Confirm the funding owner, deadline, capacity, and budget scope before selecting activities.
- Connect every initiative to a primary goal, named owner, observable signal, and review date.
- Label assumptions and adjustable baselines, and review the charter when the sponsor or product context changes.
Избегать
- Copying a large company by spreading a small team evenly across all four pillars.
- Treating a calendar of posts, events, and community launches as a strategy without observed developer problems.
- Outsourcing technical judgment, incident communication, or advocacy voice to increase output.
Часто задаваемые вопросы
What does this skill produce?
What information should I provide?
Does it create detailed budgets or dashboards?
Are its numeric rules industry benchmarks?
Does it require web access or save business context?
Can I use it with Claude, Codex, or Claude Code?
Сведения для разработчиков
Автор
samberЛицензия
MIT
Версия автора
v1.0.1
Ревизия Skillstore
r1
Ссылка
bd544b4eceb0db06e15e5c6d3d9859517aa12806
Актуальность поддержки
25.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов