npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

devrel-intern

v1.0.0

Published

A multi-agent DevRel team for Claude Code — content, community, research, advocacy, and analytics.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

zeeshan8281zeeshan8281

Keywords

claude-codeclaude-skilldevreldeveloper-relationsdeveloper-advocacycontentcommunity

Readme

devrel-intern

A multi-agent DevRel team inside Claude Code. One command gives you five specialists — content writer, community manager, technical researcher, developer advocate, and analytics reporter — all briefed on your product and ready to work.

Install

npm install -g devrel-intern

Then restart Claude Code.

Usage

/devrel-intern

First run kicks off a 5-question onboarding interview. Your answers are saved to .devrel-intern/context.md so the team stays briefed across sessions — you never re-explain your product.

After that, just describe the task:

Write a tutorial showing how to stream responses from our API
Respond to this GitHub issue: [paste issue]
Research what competitors are doing for developer onboarding
Put together a hackathon brief for ETHGlobal
Synthesize this NPS feedback into a product brief: [paste data]

The Team

| Agent | What they do | |---|---| | ✍️ Content Writer | Blog posts, tutorials, API docs, changelogs, newsletters, talk abstracts | | 🤝 Community Manager | GitHub issue responses, Discord/Slack/Twitter replies, forum posts | | 🔬 Technical Researcher | Ecosystem trends, competitor DevRel analysis, developer pain point mapping | | 📣 Developer Advocate | Demo scripts, sample app READMEs, onboarding sequences, hackathon briefs | | 📊 Analytics Reporter | Metrics reports, KPI dashboards, developer feedback synthesis |

The coordinator picks the right agent(s) for each task automatically. Multi-step tasks (e.g. product launch) involve multiple agents working in sequence with explicit handoffs.

Team Context

Your product context is saved to .devrel-intern/context.md after the first run. Every agent reads this before working — you get consistent tone, audience awareness, and priority alignment across all output.

To update context mid-project:

update team context — our priorities have changed

Analytics Reporter Note

The Analytics Reporter never makes up numbers. It will ask you to paste real data before generating any report. If you don't have data yet, it produces a blank template clearly marked for you to fill in.

What Gets Saved

Running this skill creates one file in your project:

.devrel-intern/
  context.md    # your team briefing — safe to commit or gitignore

License

MIT