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

create-invokta-capability

v0.3.0

Published

Create a standalone Invokta atomic capability package.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

vinilanavinilana

Keywords

Readme

create-invokta-capability

Create a standalone TypeScript package that publishes one atomic Invokta capability through defineExportedCapability.

Commands

create-invokta-capability <project-directory>
  [--package-manager npm|pnpm|yarn] [--no-install]
create-invokta-capability --help
create-invokta-capability --version

The npm initializer shorthand resolves to this package:

npm create invokta-capability@latest my-capability

Creation is non-interactive. The target must be a relative absent or empty real directory. Existing files and symbolic-link path components are refused and never overwritten.

The invoking package manager is inferred from npm_config_user_agent, with npm as the fallback. Use --package-manager to choose explicitly or --no-install to generate files without starting a package manager or performing network I/O.

Generated project

.agents/skills/develop-invokta-project/SKILL.md
.agents/skills/develop-invokta-project/agents/openai.yaml
.gitignore
README.md
package.json
src/capability.ts
src/index.ts
test/capability.test.ts
tsconfig.json
tsconfig.test.json

The generated develop-invokta-project skill teaches an agent to preserve the atomic publication boundary, evolve capability contracts with RED/GREEN/REFACTOR, and prove consumption through importCapability and engine.invoke. Its metadata includes a ready-to-use $develop-invokta-project prompt.

The private ESM starter pins @invokta/core to the creator version and exports one deterministic example capability. Its test composes that export into an engine and invokes it through engine.invoke. Generated files are project-owned and are never updated in place.

The creator does not publish the package, discover dependencies, start an adapter, or execute a capability.

Exit codes

| Code | Meaning | | --- | --- | | 0 | Help, version, or project creation succeeded | | 1 | Target safety, filesystem creation, or dependency installation failed | | 2 | Arguments, project path, or project name were invalid |

Creator diagnostics use TARGET_INVALID, TARGET_UNSAFE, TARGET_NOT_EMPTY, SCAFFOLD_CONFLICT, WRITE_FAILED, or INSTALL_FAILED. Rejected arguments, environment values, child errors, stacks, and causes are not included.