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

@syngy/botworks-cli

v0.1.0

Published

BotWorks user CLI

Readme

BotWorks CLI

botworks-cli is the user CLI for BotWorks.

Login

botworks-cli auth login --web-url https://www.example.com

The command creates a Web Auth Handoff and prints a browser pairing URL plus an 8 digit pairing code. When --profile is omitted, credentials are saved to the default profile under ~/.botworks-cli.

Use --no-open to print the URL without opening a browser. Use --no-wait when the browser pairing will be completed later:

botworks-cli auth login --web-url https://www.example.com --no-open --no-wait
botworks-cli auth login --complete

In a non-interactive shell, login automatically uses the same two-step path as --no-wait.

Profiles

Each profile is bound to one current team. Team-scoped commands read teamId from the active profile and do not accept a team id argument. Select the team after login:

botworks-cli auth profiles list
botworks-cli auth profiles use prod
botworks-cli team use <teamId>
botworks-cli --profile prod auth whoami

auth whoami --json prints the current profile, login identity, and selected team. If no team is selected, run botworks-cli team use <teamId> before using team-scoped commands.

Conversation Harness

Start a real conversation and attach the SSE stream:

botworks-cli conversation start \
  --digi-employee-id <digiEmployeeId> \
  --content "<prompt>" \
  --watch

Attach an existing conversation stream:

botworks-cli conversation watch <conversationId> --after-seq <seq>

The stream commands print NDJSON events and use a conversation stream ticket. They do not require manually passing user access tokens. When conversation start is run without --watch, it prints a conversation.watch_hint NDJSON line with the exact conversation watch command to attach later.

WebSkill Publish

Create and test a package locally, then publish it to the selected team:

npm create @syngy/webskill ./web-skills/example -- --title "Example workflow" --domain example.com
cd ./web-skills/example
npm install
npm run check
npm run run -- --url https://example.com --tool check_current_page --args '{}'
botworks-cli webskill publish .

webskill publish reads package.json.name as the package identity and uploads the directory as a web skill package.