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

claude-pro-kit

v0.1.0

Published

A collection of production-ready Claude Code agents, skills, and commands for SEO, vibe/copy, and marketing teams.

Readme

Claude Code Kit

A collection of production-ready Claude Code agents, skills, and commands for SEO, vibe/copy, and marketing teams.


What's in the Box

| Kit | Orchestrator | Specialists | Commands | |-----|-------------|-------------|----------| | SEO | seo-lead | on-page-auditor, keyword-researcher, content-brief-writer | /seo-audit, /rewrite-meta | | Vibe | vibe-lead | tone-aligner, microcopy-editor | /vibe-check, /microcopy-audit | | Marketing | growth-lead | email-sequence-writer, social-post-crafter | /launch-kit, /re-engage |


Quick Start (Installation & Usage)

1. Install into your project

Open your project terminal and run:

npx -y claude-pro-kit init --kit all

Or install a single kit:

npx -y claude-pro-kit init --kit seo

(Or via GitHub directly: npx -y github:shubhranshu03/claudeagents init --kit all)

2. Fill in your project context in CLAUDE.md

Open CLAUDE.md in your project root and replace the placeholders with your project's details.

3. Open Claude Code and run commands

claude

Run any slash command directly in terminal:

> /seo-audit https://yourwebsite.com "project management software"
> /vibe-check src/components/SignupModal.tsx "friendly and direct"
> /launch-kit "Product Name, Target Audience, Goal, 2026-11-01"

Repository Structure

kits/
  seo/.claude/
    agents/     # seo-lead, on-page-auditor, keyword-researcher, content-brief-writer
    skills/     # on-page-audit-checklist, keyword-cluster-builder
    commands/   # seo-audit, rewrite-meta
  vibe/.claude/
    agents/     # vibe-lead, tone-aligner, microcopy-editor
    skills/     # tone-parameter-setter, microcopy-pattern-library
    commands/   # vibe-check, microcopy-audit
  marketing/.claude/
    agents/     # growth-lead, email-sequence-writer, social-post-crafter
    skills/     # launch-timeline-builder, audience-brief-extractor
    commands/   # launch-kit, re-engage
bin/
  install.js    # npx installer script
scripts/
  validate.js   # validates frontmatter, section structure, line counts & cross-references
STANDARDS.md    # kit standards & rules
CREDITS.md      # authorship and license
README.md       # documentation

Validation (for Contributors)

Run before submitting changes to verify all agents, skills, and commands match standards:

node scripts/validate.js

Exit code 0 = all checks pass. Exit code 1 = list of errors to fix.


Standards Summary

All files follow strict rules in STANDARDS.md:

  • Agents: 40–90 lines · YAML frontmatter with name/description/tools/model · 5 required sections
  • Skills: 40–100 lines · 5 required sections including real worked example and binary checklist
  • Commands: 15–40 lines · names agents and skills by exact filename · ends with output template
  • Global: no invented stats · no copied content · lowercase-hyphen names · all cross-references must resolve

License

See CREDITS.md.