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

@devmunna/agent-skillkit

v0.1.0

Published

Install production-grade AI agent development skills for your project stack

Readme

Agent Skillkit

Install stack-aware AI agent development skills for Claude Code and Codex.

@devmunna/agent-skillkit copies curated SKILL.md packages into a project, adds shared agent instructions, and keeps installed skills refreshable as the package evolves.

Quick Start

npx @devmunna/agent-skillkit init

The installer asks which agent to support:

  • Claude Code: installs skills to .ai-skills/skills and updates CLAUDE.md
  • Codex: installs skills to .agents/skills and writes shared AGENTS.md

Non-Interactive Use

npx @devmunna/agent-skillkit init --agent codex --profile express-prisma --yes
npx @devmunna/agent-skillkit init --agent claude --agent codex --stack react --stack tailwind --yes
npx @devmunna/agent-skillkit init --agent codex --skill node-base --skill zod-validation --yes

Commands

ai-skills init       # Install skills for a selected agent and stack
ai-skills add        # Add more skills to the configured agents
ai-skills list       # List installed or available skills
ai-skills update     # Refresh installed skills from the current package version
ai-skills validate   # Validate the package skill catalog and files
ai-skills doctor     # Inspect the current project installation

Profiles

Profiles install a tested combination of skills:

  • express-prisma
  • fastify-api
  • next-fullstack
  • react-spa
  • mern
  • node-base

Agent Behavior

The package is designed to reduce token usage and hallucination:

  • Keep SKILL.md files focused on hard rules and activation context
  • Put longer templates and examples in references/
  • Generate AGENTS.md with rules for reading only relevant skills
  • Install reusable workflows under .ai-skills/workflows
  • Provide doctor and validate commands for drift checks

Development

Prerequisites:

  • Node.js 18 or newer
  • npm

Set up the project:

npm install
npm run typecheck
npm run build
npm test

Run the CLI locally while developing:

npm run dev -- init
npm run dev -- list
npm run dev -- doctor

Check what will be published:

npm pack --dry-run

The npm package only publishes the files listed in package.json:

  • dist
  • bin
  • skills

Source files, tests, editor config, and local dependencies are not included in the published package.

Contributing

Contributions are welcome. Please keep changes focused and include validation steps in your pull request.

Recommended workflow:

  1. Fork the repository.
  2. Create a feature branch.
  3. Install dependencies with npm install.
  4. Make your changes.
  5. Run npm run typecheck.
  6. Run npm test.
  7. Run npm pack --dry-run if your change affects published files.
  8. Open a pull request with a short summary and test results.

Adding or Updating Skills

Skills live in skills/<skill-name>/SKILL.md. Larger examples, templates, or optional details should go in skills/<skill-name>/references/.

When adding a skill:

  1. Create a clear SKILL.md with activation context and hard rules.
  2. Move long examples into references/.
  3. Register the skill in the package catalog if needed.
  4. Add or update tests when behavior changes.
  5. Run npm test.

Keep skill files concise so agents can load only the context they need.

Pull Request Checklist

  • The package builds with npm run build.
  • TypeScript passes with npm run typecheck.
  • Tests pass with npm test.
  • New skills include focused instructions and references only where useful.
  • README or docs are updated when commands, profiles, or behavior change.

Release Checklist

Before publishing a new version:

npm test
npm pack --dry-run
npm publish --access public

Use npm pack --dry-run to confirm the package contents and size before release.

License

MIT