developer-relations
v0.3.2Developer-relations / DevRel team — agents (developer-advocate, devrel-content-engineer, developer-community-manager) for the developer experience of a product with an API/SDK: time-to-first-success (getting-started) audits, sample-app and SDK-quickstart design, a DX content strategy, conference talks + CFP abstracts, community health, DX metrics (activation funnel), and the product-feedback loop that fixes the product instead of writing around it. skills, a knowledge bank with Mermaid decision trees (advocate-vs-docs-vs-community, fix-the-product-or-document-it, content-format choice), best-practices, templates, commands, and an advisory anti-pattern hook. Distinct from technical-writing-docs (reference docs), marketing-operations (demand gen), and product-management (what to build). Requires ravenclaude-core@>=0.7.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install developer-relations for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install developer-relations@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/developer-relations/.
Plugin files
├── .claude-plugin/plugin.json├── skills/community-health-review/SKILL.md├── skills/conference-talk-and-cfp/SKILL.md├── skills/devrel-content-strategy/SKILL.md├── skills/getting-started-audit/SKILL.md└── skills/sample-app-design/SKILL.md
Included Skills5
Diagnose a developer community by the metrics that matter — answered-question rate, time-to-first-response, returning contributors, and sentiment — not member or follower count. Use to assess a forum/Discord/Discussions/Stack Overflow presence and design ops that fix unanswered questions.
Shape a conference talk and write a CFP abstract that gets accepted and lands — lead with the attendee takeaway (what they can DO afterward), state concrete takeaways, match the track, and keep it engineer-to-engineer not a product pitch. Use when proposing or preparing a developer-conference talk.
Choose content formats and a calendar for an activation goal — format follows the goal (getting-started for first success, sample app for the value path, guide for a concept, talk for reach), not the trendy channel. Use when planning DevRel content tied to the activation funnel.
Measure and shorten time-to-first-success — walk the getting-started path from a clean state, time it, rank friction points by where developers drop off, and make a fix-or-document call on each. Use whenever you need to know how good (or bad) onboarding really is.
Spec a sample app or SDK quickstart that demonstrates the real value path as production-grade, runnable code — it runs from a clean checkout, handles errors, pins versions, and has no hardcoded secrets. Use when designing or reviewing sample code that developers will copy verbatim.
Plugin manifests1
{
"name": "developer-relations",
"version": "0.3.2",
"description": "Developer-relations / DevRel team — agents (developer-advocate, devrel-content-engineer, developer-community-manager) for the developer experience of a product with an API/SDK: time-to-first-success (getting-started) audits, sample-app and SDK-quickstart design, a DX content strategy, conference talks + CFP abstracts, community health, DX metrics (activation funnel), and the product-feedback loop that fixes the product instead of writing around it. skills, a knowledge bank with Mermaid decision trees (advocate-vs-docs-vs-community, fix-the-product-or-document-it, content-format choice), best-practices, templates, commands, and an advisory anti-pattern hook. Distinct from technical-writing-docs (reference docs), marketing-operations (demand gen), and product-management (what to build). Requires ravenclaude-core@>=0.7.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"developer-relations",
"devrel",
"developer-advocacy",
"developer-experience",
"dx",
"time-to-first-success",
"getting-started",
"sample-app",
"sdk-quickstart",
"developer-community",
"dx-metrics",
"activation-funnel",
"product-feedback-loop",
"developer-content"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.7.0"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[developer-relations on Agent Plugins Marketplace](https://pluginsmp.com/plugins/developer-relations)