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

## Install

```bash
npx skillstore add samber/devrel-strategy
```

## Metadata

- Status: approved
- Slug: samber-devrel-strategy
- Version: 1.0.1
- Author version: 1.0.1
- Skillstore revision: r1
- Version status: valid
- Tree hash: 07b4f4ee978dc49a664b4a1acbd005f2f509fdeecc38d12945229b5c178524da
- Author: samber
- GitHub username: samber
- License: MIT
- Repository: https://github.com/samber/developer-relations-skills/tree/b8cf857a6069b89252445c82a36fcb9491fd6b20/skills/devrel-strategy
- Ref: bd544b4eceb0db06e15e5c6d3d9859517aa12806
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/samber-devrel-strategy
- Manifest: https://skillstore.pages.dev/api/skills/samber-devrel-strategy/manifest

## Capabilities

- Conduct a guided interview to establish the funding driver, deadline, capacity, budget ownership, and planning horizon.
- Structure a CORE analysis covering community, organization, relationships, and ecosystem.
- Compare program archetypes and select two primary goals plus one secondary goal tied to developer journey problems.
- Prioritize an audience and choose in-house, contractor, agency, or community sourcing for each proposed initiative.
- Define the next staffing capability and its hiring trigger without creating a full organization chart.
- Draft a twelve-section charter with owners, signals, review dates, explicit exclusions, open questions, and an executive narrative.

## Use Cases

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

## Prompt Templates

### 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.
```

## Limitations

- Does not produce tactical content, event plans, a first-90-days execution plan, or a complete measurement framework.
- Does not calculate detailed budgets, reporting lines, or staffing ratios; it refers those decisions to related skills.
- Recommendations depend on accurate user inputs; numeric capacity and prioritization rules are adjustable starting baselines, not validated industry standards.
- Persistent context storage and public-source browsing depend on the host environment; users should control what business information is retained.

## Best Practices

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

## Anti Patterns

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

## Security Audit

- Audited at: 2026-10-25T12:55:18.732\+00:00
- Summary: 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.

## Stats

- Views: 0
- Downloads: 2
- Favorites: 0
- Popularity score: 0