📦

devrel-strategy

Name: devrel-strategy
Author: samber

v1.0.1 Inhaltsrevision r1 Sicher ⚙️ Externe Befehle

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.

Unterstützt: Claude Codex Code(CC)

🥉 79 Bronze

Maintain this Skill? Claim it 🥉 79 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage

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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/samber-devrel-strategy.md Signiertes manifest GET /api/skills/samber-devrel-strategy/manifest Signiertes lockfile GET /api/skills/samber-devrel-strategy/lockfile

Testen

„devrel-strategy“ wird verwendet. Illustrative scenario: one advocate, strong signups, weak second-use activation, and a ten-week executive review deadline.

Erwartetes Ergebnis:

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“ wird verwendet. Illustrative scenario: enterprise technical evaluations stall; the revenue leader sponsors two DevRel practitioners.

Erwartetes Ergebnis:

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.

Sicherheitsaudit

Sicher

v1 • 25.10.2026 Versionsbericht öffnen

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.

Gescannte Dateien

1,100

Analysierte Zeilen

Prüfelemente

Falschmeldungen ignoriert

Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.

Geprüft von: codex

Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen

Berichtslink kopieren

https://skillstore.io/skills/samber-devrel-strategy/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-devrel-strategy/security.svg)](https://skillstore.io/skills/samber-devrel-strategy?utm_source=security_passport_badge)

HTML-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>

Einbettungskarte

<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>

Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

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-Zitat

@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-Score

Warum dieser Score Evidenzvertrauen: Mittel

Architektur

100

Wartbarkeit

Inhalt

Gemeinschaft

100

Spezifikationskonformität

Was Sie erstellen können

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.

Diese Prompts ausprobieren

Begin the strategy interview

We are starting DevRel for [product] with [team capacity]. Interview me one question at a time to establish our funding driver and constraints.

Compare program directions

Our sponsor wants [outcome] by [date]. Developers struggle at [journey step]. Compare feasible program archetypes for [capacity] and explain their trade-offs.

Choose sourcing and staffing

Our chosen direction is [archetype], with initiatives [list]. Compare sourcing options, retain credibility-sensitive work internally, and propose the next capability with its trigger.

Build and challenge the charter

Using [program context], develop our charter section by section. Check goal traceability, capacity, sourcing, exclusions, and review triggers. Label assumptions and adjustable baselines.

Bewährte Praktiken

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.

Vermeiden

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.

Häufig gestellte Fragen

What does this skill produce?

It produces a short DevRel charter covering position, funding, goals, audience, priorities, sourcing, staffing, exclusions, open questions, executive messaging, and review.

What information should I provide?

Provide your product, adoption path, sponsor, team capacity, existing assets, budget scope, deadline, and constraints. The skill asks clarifying questions.

Does it create detailed budgets or dashboards?

No. It assigns one signal per initiative and refers detailed budget allocation, measurement frameworks, and organization design to related skills.

Are its numeric rules industry benchmarks?

No. Capacity limits and goal counts are adjustable starting baselines. Historical survey figures require attribution and should not become automatic targets.

Does it require web access or save business context?

Browsing is optional for checking public references. It requests context storage in available memory or a local file; avoid retaining sensitive information.

Can I use it with Claude, Codex, or Claude Code?

The skill declares support for all three. Available browsing and persistence features depend on the host environment.