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

@theokit/skills

v0.4.1

Published

Installs the TheoKit ecosystem agent skills into every AI coding tool you use — Claude Code, OpenAI Codex, Gemini CLI, GitHub Copilot, Zed, Devin Desktop — on Windows, macOS and Linux. Zero dependencies; links where that follows your lockfile, copies wher

Readme

@theokit/skills

Installs the TheoKit ecosystem's agent skills into whichever AI coding tools you actually use, on Windows, macOS and Linux.

npx @theokit/skills

That is the whole thing. It detects the tools configured in your project, writes the skills where each one reads them, and tells you what it did.

Why this is not one adapter per tool

Surveying the vendor documentation on 2026-08-20 produced one finding that shrinks the problem:

.agents/skills/ is read by OpenAI Codex, Gemini CLI, GitHub Copilot, Zed and Devin Desktop. Claude Code is the holdout — its documentation says plainly that it reads .claude/, and the request for .agents/ support is unanswered.

So two directories serve six tools. A third, .github/skills/, is the only path the github.com-side Copilot surfaces (Chat, code review) read; they ignore .agents/.

| Target | Directory | Serves | | --- | --- | --- | | agents | .agents/skills/ | OpenAI Codex, Gemini CLI, GitHub Copilot, Zed, Devin Desktop | | claude | .claude/skills/ | Claude Code, GitHub Copilot in VS Code | | github | .github/skills/ | GitHub Copilot on github.com (Chat, code review) |

Modelling this as a per-tool adapter list would write the same bytes five times and then require five copies to be kept in step. The unit here is the location, not the tool.

Linked, or copied — and why you are told which

A link is the better artifact: it makes the installed skill follow your lockfile, so npm update @theokit/skills updates the instructions instead of leaving last year's copy that your agent obeys with the same diligence as a current one.

A link is only valid where the source outlives the process. Run through npx, this package lives in a temporary npm cache that gets pruned, and a link into it is a link into nothing — silently, since the agent simply finds no skill. So:

  • Linked when this package is a dependency of your project (npm i -D @theokit/skills) and you install in project scope.
  • Copied otherwise, and whenever the filesystem refuses a link.

On Windows the link is a junction, which needs no Administrator rights and no Developer Mode — unlike a symlink, which needs one of them. Elsewhere it is a relative symlink, so moving the tree does not break it. Every failure falls back to copying, and the output says which mode you got: a silent downgrade would make "installed" mean two different things with no way to tell them apart.

This is verified rather than asserted — the suite runs on ubuntu-latest, macos-latest and windows-latest, and the end-to-end test spawns the real installer in a real temporary project on each.

Keeping it honest: --check

npx @theokit/skills --check

Exits non-zero when what is installed no longer matches this package: never installed, installed from a different version, or installed and since deleted. Three states rather than a boolean, because the fixes differ.

Put it in CI. An instruction file that has gone stale is followed exactly as diligently as a current one, and nothing else surfaces the divergence — which is the most-cited criticism of shipping instruction files at all, and the reason this command exists.

Options

--global            install for your user instead of this project
--force             replace what is already there
--copy              copy even where linking would work
--dry-run           print the plan, write nothing
--target=<id>       agents | claude | github   (repeatable; default: detected)
--skill=<name>      install one skill (repeatable; default: all)

Re-running is a no-op. .theokit-skills.json records what landed, from which version, in which mode; it is small, sorted and meant to be committed.

CLAUDE_CONFIG_DIR is honoured, because Claude Code honours it — installing into ~/.claude when you have relocated your config writes a directory the tool never reads.

What ships

Every skill in the TheoKit ecosystem lives under skills/. Today that is theokit-sdk, which covers Agent.create / Agent.prompt, Tool.create with Zod, streaming SDKMessage events, run.wait / cancel, MCP servers, subagents, cron, memory and context, disposal, and the TheokitAgentError hierarchy.

The content is generated from @theokit/sdk's own per-module sources and gated against drift, so a bad sync cannot publish a skill teaching a removed API or a subpath that does not exist.

License

Apache-2.0.