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

@wocha/skills

v0.1.0

Published

Wocha agent skills for Cursor and AI coding assistants

Readme

@wocha/skills

Agent skills for integrating Wocha authentication with AI coding assistants like Cursor, Claude Code, and GitHub Copilot. Follows the Agent Skills format.

Installation

npx skills add @wocha/skills

Target specific agents:

npx skills add @wocha/skills --agent cursor claude-code github-copilot

From a GitHub repository (development):

npx skills add wocha-dev/wocha/sdks/skills

What happens after install

When you ask your AI assistant to "add Wocha login to my app":

  1. The wocha-quickstart router skill reads package.json, requirements.txt, go.mod, or Gemfile
  2. It detects your framework and selects the matching skill
  3. The assistant follows step-by-step instructions to install the SDK, configure env vars, and wire up auth

You do not pick skills manually — framework detection handles routing.

Available skills (17)

| Skill | Covers | |-------|--------| | wocha-quickstart | Framework detection router | | wocha-nextjs | Next.js App Router — middleware, server helpers, org switching | | wocha-react | React SPA — PKCE, hooks, protected routes | | wocha-vue | Vue 3 — composables, router guards | | wocha-express | Express — JWT validation, permission middleware | | wocha-python | Python — Management API, FastAPI/Django patterns | | wocha-go | Go — Management API, HTTP middleware | | wocha-sdk | Management API (TypeScript, Python, Go) | | wocha-migration | Migrate from Auth0, Clerk, Firebase, Supabase | | wocha-mfa | TOTP, passkeys, backup codes, org enforcement | | wocha-organisations | Multi-tenancy, membership, hierarchy, SSO per org | | wocha-webhooks | Handler setup, signature verification, retries | | wocha-permissions | SpiceDB schema, checks, relationships | | wocha-testing | Mocks, test sessions, Playwright/Cypress E2E | | wocha-cli | All CLI commands and local dev workflows | | wocha-enterprise | SAML SSO, SCIM, admin portal, custom domains | | wocha-feature-flags | Flag creation, evaluation, org/user overrides |

Framework detection

The quickstart router applies these rules (first match wins):

| Detection signal | Skill | |------------------|-------| | package.json has "next" | wocha-nextjs | | package.json has "react" (not Next/RN) | wocha-react | | package.json has "vue" (not Nuxt) | wocha-vue | | package.json has "express" | wocha-express | | requirements.txt has "django" | wocha-python | | requirements.txt has "fastapi" | wocha-python | | go.mod present (HTTP server) | wocha-go | | Gemfile has "rails" | Rails quickstart docs |

See wocha-quickstart.md for the full decision tree.

Example prompts

Add Wocha authentication to my app
Set up Wocha in my Next.js project with protected routes
Migrate from Auth0 to Wocha
Add passkeys and TOTP MFA
Set up SAML SSO for my B2B customers

Documentation

Package exports

Individual skills are importable via subpath exports:

// Node.js — read skill content programmatically
import { readFileSync } from "fs";
import { fileURLToPath } from "url";
import { dirname, join } from "path";

const skillPath = join(
  dirname(require.resolve("@wocha/skills/package.json")),
  "skills/wocha-nextjs.md"
);

Or use named exports: @wocha/skills/wocha-nextjs.

Manifest: @wocha/skills/manifestskills/index.json.