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

@vgopal1290/email-outreach-skill

v1.1.0

Published

An approval-gated workflow skill for customer, sponsor, and partnership outreach. Installs itself into Claude Code and Codex CLI.

Readme

Email Outreach Skill

An approval-gated outreach workflow for researching a user-defined number of qualified customers or sponsors, selecting a template direction, tracking campaign data, and choosing a compliant delivery method.

Installing the package puts the skill where coding agents already look for it, so there is no manual copy step.

Install

For every project on your machine:

npm install -g @vgopal1290/email-outreach-skill

For one project only:

npm install --save-dev @vgopal1290/email-outreach-skill

Restart any running agent session afterwards so it re-scans its skills directory.

What gets written

| Agent | Global install | Project install | | --- | --- | --- | | Claude Code | ~/.claude/skills/email-outreach/ | <project>/.claude/skills/email-outreach/ | | Codex CLI | $CODEX_HOME/skills/email-outreach/ (default ~/.codex) | <project>/.codex/skills/email-outreach/ | | Anything reading AGENTS.md (Cursor, Copilot, Gemini CLI, Amp, …) | — | a managed block in <project>/AGENTS.md pointing at the skill |

Both Claude Code and Codex CLI read the same SKILL.md format and load it on demand, so the skill activates when the conversation matches its description — outreach, sponsorship, cold email, campaign research — without being invoked by name. Agents that have no skills directory get a short pointer block in AGENTS.md, delimited by BEGIN/END markers; content outside those markers is never modified.

Existing skill directories that this package did not create are left alone (pass --force to overwrite them).

If the skill did not install itself

Some setups block dependency lifecycle scripts: pnpm and Yarn Berry do by default, as does npm install --ignore-scripts. Run the installer directly:

npx @vgopal1290/email-outreach-skill install --global   # or: install

CLI

npx @vgopal1290/email-outreach-skill <command> [options]

Commands
  install      Copy the skills into the agent directories (default)
  uninstall    Remove skills this package installed
  status       Show where the skills are currently installed
  path         Print this package's skills directory

Options
  --global           Install for the current user
  --project [dir]    Install into a project directory (default: current directory)
  --no-agents-md     Do not touch the project's AGENTS.md
  --force            Overwrite skill directories this package did not install
  --dry-run          Report what would change without writing

With no scope flag, a directory containing package.json or .git is treated as a project; otherwise the install is global.

Automatic install behaviour

The postinstall step is deliberately conservative. It does nothing when the package is running from a source checkout rather than an install, when CI is set, or when npm reports no install directory — and a failure there prints a warning instead of breaking your install.

| Variable | Effect | | --- | --- | | EMAIL_OUTREACH_SKILL_SKIP_INSTALL=1 | Skip the automatic install entirely | | EMAIL_OUTREACH_SKILL_SCOPE=global\|project | Override scope detection | | EMAIL_OUTREACH_SKILL_NO_AGENTS_MD=1 | Leave AGENTS.md alone | | EMAIL_OUTREACH_SKILL_FORCE_INSTALL=1 | Run even under CI |

Uninstall

npx @vgopal1290/email-outreach-skill uninstall --global   # or: uninstall
npm uninstall -g @vgopal1290/email-outreach-skill

Uninstall removes only directories carrying this package's install marker, and strips its managed block out of AGENTS.md.

Contents

  • skills/vg_stack-email-outreach/SKILL.md — the skill instructions
  • bin/email-outreach-skill.mjs — installer CLI
  • scripts/installer.mjs, scripts/postinstall.mjs — install logic