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

@skill-graveyard/core

v0.3.0

Published

Internal building blocks for the skill-graveyard / mcp-graveyard CLIs. No semver-stability promise.

Readme

@skill-graveyard/core

Internal building blocks shared between skill-graveyard and mcp-graveyard.

No semver-stability promise. This package is published because npm workspaces require shared dependencies to be installable from the registry, not because the API is intended for external consumption. Breaking changes can land in any version. If you depend on it directly, pin exactly.

End users — install one of the CLIs instead:

npx skill-graveyard      # audit your installed Claude Code skills
npx mcp-graveyard        # audit your configured MCP server tools

What's in it

  • parseToolCalls<T>(filepath, projectKey, predicate, build) — generic streaming JSONL parser for Claude Code session logs. Picks out tool_use items matching a caller-supplied predicate, pairs them with their tool_result, and returns typed call records. Used by both CLIs to extract their respective tool-call shapes.
  • parseSession(filepath, projectKey) — thin skill-flavored adapter over parseToolCalls, kept for backward compatibility with skill-graveyard's pre-monorepo signature.
  • findSessionFiles(projectsDir, sinceMs) — discovers .jsonl session files newer than a cutoff mtime.
  • resolveClaudePaths(claudeDir?) — derives the standard Claude Code home layout (~/.claude/projects/, ~/.claude/plugins/, ~/.agents/skills/, etc.) with optional override.
  • findGitRoot(start), discoverInstalledSkills(...), discoverProjectScopedSkills(...) — discovery primitives for skill-graveyard's audit (not used by mcp-graveyard).
  • KNOWN_TOOLS, isKnownTool(name) — case-insensitive set of built-in Claude Code tool names. Used by mcp-graveyard suggest to flag tool/server confusion.
  • estimateTokens(text), TOKENIZER_NAMEcl100k_base tokenizer wrapper (Anthropic doesn't ship a public Claude tokenizer; this is a 5-15% drift proxy).

Development

npm install
npm run build --workspace=@skill-graveyard/core
npm run typecheck --workspace=@skill-graveyard/core
npm test --workspace=@skill-graveyard/core

Tests use real fs against os.tmpdir() fixtures. No mocking. The whole purpose of this package is correctly walking real Claude Code install layouts; mocked filesystem tests would defeat the point.

Repository

Source lives at https://github.com/sfrangulov/skill-graveyard in packages/core/. Issues, PRs, and full development docs all live there.

License

MIT