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

@sa-ar/skillflow

v0.1.0

Published

Local-first agentic workflow orchestrator for engineering blueprints — plan any feature before touching code.

Readme

skillflow

Local-first agentic workflow orchestrator for engineering blueprints — plan any feature before touching code.


TL;DR quickstart

Requires Node.js ≥ 18

# 1. Install
npm install -g skillflow

# 2. Navigate to your git repo
cd my-project

# 3. Set up skillflow in the project
skillflow init

# 4. Plan a feature
skillflow run --name "My feature"

skillflow will interview you about the feature, then produce a full spec in docs/features/my-feature/CONTEXT.md, PRD.md, EDGE_CASES.md, PLAN.md, and GIT_STRATEGY.md.

Once the plan is ready, implement it:

skillflow implement --slug my-feature

If something goes wrong at any step, re-run npm install -g skillflow and try again. If a planning run was interrupted, use skillflow resume to pick up where you left off.


How it works

flowchart TD
    A([skillflow run --name]) --> B[Load .skillflowrc]
    B --> C[Load workflow]
    C --> D[grill-me\nDiscover feature context]
    D --> E[write-a-prd\nGenerate PRD.md]
    E --> F[edge-case-matrix\nGenerate EDGE_CASES.md]
    F --> G[prd-to-plan\nGenerate PLAN.md]
    G --> H[git-strategy\nGenerate GIT_STRATEGY.md]
    H --> I[(docs/features/slug/)]
    I --> J([skillflow implement --slug])
    J --> K[Dev harness\nClaude Code session]
    K --> L[(Code changes in repo)]

Each arrow is a call to the configured harness (default: Claude Code). You stay in the loop at every checkpoint — review, revise, or approve before the next step runs.


Installation

Global install (recommended)

npm install -g skillflow

Installs the skillflow binary globally. Works with any project.

Ephemeral — no install

npx skillflow <command>

Runs skillflow without a global install. Slower on first use (downloads on each invocation).

Local development / contributing

git clone [email protected]:Sa-ar/skillflow.git
cd skillflow
npm install
npm run build
npm link          # makes `skillflow` available globally from this clone

Node version

Node.js ≥ 18 is required. Check your version:

node --version

skillflow init

Sets up your project with default skills, workflows, and a .skillflowrc config file:

skillflow init          # project-level setup (copies skills + workflows)
skillflow init --global # write only ~/.skillflowrc (harness config, no files)
skillflow init --force  # overwrite existing files with bundled defaults

It is safe to run skillflow init more than once without --force — existing files are left untouched.


Docs

| Topic | File | |---|---| | Complete command reference (flags, examples, artifact locations) | docs/commands.md | | Configuration reference (all .skillflowrc keys) | docs/configuration.md | | Harness deep-dive (annotated script, invocation mechanics) | docs/harness.md | | Skills (directory layout, discovery, authoring) | docs/skills.md | | Workflows (step types, customization, composition) | docs/workflows.md | | Contributing (PR guide, tests, extension points) | CONTRIBUTING.md |