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-research-flow

v0.1.4

Published

Scaffold a new research-flow or dev-workflow project with Claude Code, gh, and a GitHub Project board wired up.

Readme

create-research-flow

Scaffold a new Research Flow project — an agentic research system with persistent memory, Claude Code skills, and a GitHub Project board for tracking research goals, hypotheses, and findings.

New here? See docs/getting-started.md for a step-by-step setup walkthrough (Node, git, gh, uv, Claude Code) before running the CLI.

Quick start

npx create-research-flow my-project

That's it. The CLI walks you through the rest:

  1. Checks prereqsgit, gh, claude, uv. If any are missing, it offers to install them for you (see Prerequisites).
  2. Verifies gh auth — aborts with gh auth login instructions if not signed in.
  3. Prompts for parent folder, repo name, GitHub owner, visibility (private/public), whether to create a Project board, and an optional first research goal.
  4. Scaffolds: clones the template → initial commit → creates the GitHub repo → pushes → seeds labels → creates the Project board → opens the first issue and adds it to the board → runs uv sync.
  5. Optionally launches claude in the new project directory.

Non-interactive form

npx create-research-flow my-project \
  --owner my-github-username \
  --private \
  --skip-project \
  --skip-install \
  --skip-claude

Prerequisites

| Tool | Why | Install | |---|---|---| | Node 20+ | Runs this CLI | nodejs.org or nvm install 20 | | git | Clones the template, initial commit | macOS: xcode-select --install | | gh | Creates the repo, labels, Project board, first issue | macOS: brew install gh · Linux: see cli.github.com | | claude | Launches Claude Code in the new project | curl -fsSL https://claude.ai/install.sh \| bash | | uv | Installs the Python deps in the new project | curl -LsSf https://astral.sh/uv/install.sh | sh |

If any of gh, claude, or uv are missing when you run the CLI, it will prompt you to install them automatically using the commands above. You can decline and install them yourself.

One-time gh setup

gh auth login                              # interactive: GitHub.com → HTTPS → browser
gh auth refresh -s project,repo,workflow   # ensure scopes for repo + Project board
gh auth status                             # verify

The project scope is required — without it, the Project board step fails (the rest still works).

One-time claude setup

claude   # first run prompts for login / API key

Flags

| Flag | Description | |---|---| | --private / --public | Repo visibility (prompted if omitted) | | --owner <owner> | GitHub owner/org (defaults to authed user) | | --skip-project | Don't create a GitHub Project board | | --skip-install | Don't run uv sync in the new project | | --skip-claude | Don't offer to launch claude at the end |

What you get

After scaffolding, your new project has:

  • The full research-flow template (memory layer, skills, hooks, experiment harness)
  • A GitHub repo at {owner}/{repo} with seeded labels: research-goal, hypothesis, finding, synthesis, maintenance
  • A GitHub Project board Research Flow with columns: Backlog | In Progress | Synthesizing | Done
  • (optional) A first research-goal issue, added to the Project board
  • Python deps installed via uv sync

Troubleshooting

  • Still missing: uv. Restart your shell and rerun. — the uv installer drops the binary into ~/.local/bin, which isn't on PATH until you start a new shell. Open a new terminal and rerun.
  • gh project create fails — your gh token is missing the project scope. Run gh auth refresh -s project.
  • Directory ... already exists. — pick a different project name, or remove the existing folder.
  • No automated installer for git — on Linux, install via your package manager (apt install git, dnf install git, etc.).

Local development

git clone <this-repo>
cd create-research-flow
npm install
npm start -- my-test-project

License

MIT