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

@respec-gtc/cli

v0.1.23

Published

CLI for Respec skill management (GovTech)

Downloads

303

Readme

@respec-gtc/cli

CLI for managing shared AI coding skills via Respec.

Install

npm install -g @respec-gtc/cli

Core trust workflow

For repo-native Respec Core adoption, the main pipeline is:

respec lint <repo>
respec migrate <repo>
respec activate <repo>
respec doctor <repo>

Mental model:

  • lint = trust floor
  • migrate = smallest honest rewrite toward the current contract
  • activate = bind the repo to the runtime
  • doctor = reality check after binding

Commands

| Command | Description | |---------|-------------| | respec init | Initialize Respec in a project | | respec pull | Pull skills from remote GitHub repo | | respec push | Push local changes to your user branch | | respec export | Generate rules files from local skills | | respec status | Show local vs remote diff summary | | respec lint | Validate a Respec Core pack or standalone skill tree | | respec migrate | Preview or apply safe legacy Core-manifest rewrites | | respec activate | Write repo-local activation metadata or approved runtime bridge changes | | respec doctor | Diagnose repo/runtime/env issues after lint and activation |

Quick Start

Project initialization

npm install -g @respec-gtc/cli
respec init

Set GITHUB_TOKEN or RESPEC_GITHUB_TOKEN for pull/push/status commands.

Core package workflow

# Inspect current repo/pack state
respec lint /path/to/repo

# Preview legacy-field rewrites without touching files
respec migrate /path/to/repo

# Apply only safe manifest rewrites
respec migrate --write /path/to/repo

# Bind the repo locally
respec activate /path/to/repo

# Confirm reality matches intent
respec doctor /path/to/repo

respec migrate behavior

respec migrate is intentionally conservative.

Safe rewrites currently include:

  • activation.skillPath -> activation.skill_dir
  • add missing activation.assistant_contract
  • synthesize missing compatibility fields from contract_version

If the manifest contains risky semantic mismatches — for example an impossible compatibility window or contract claims that contradict each other — the command stops at review-required instead of inventing new truth.