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

find-customer-orchestrator

v0.1.1

Published

Install Francesco's Codex prospect-to-demo workflow on Windows

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

kappaemmekappaemme

Keywords

codexskillprospectingclaude-codevercel

Readme

Find Customer Orchestrator

Skill Codex e registro locale per cercare attività senza sito ufficiale, preparare un brief verificato per Claude Code /design, creare una demo e pubblicare una preview Vercel. Francesco sceglie il cliente e invia personalmente il messaggio. Il registro controlla i follow-up dopo quattro giorni.

Installazione su Windows

Servono Node.js, Python, Claude Code, Vercel CLI e Codex già configurati. In PowerShell:

npx.cmd --yes find-customer-orchestrator@latest install

Il comando crea %USERPROFILE%\Documents\FindCustomerAutomation e installa le tre skill in %USERPROFILE%\.codex\skills. Non sovrascrive cartelle già esistenti. Aprire la cartella del progetto in Codex e riavviare l'app per caricare le skill.

Per aggiornare un'installazione esistente senza perdere registro, demo, template o skill di ricerca:

npx.cmd --yes find-customer-orchestrator@latest upgrade

Il comando aggiorna solo la skill orchestratrice e le istruzioni del progetto, salvando una copia dei file precedenti. Se il progetto è in un'altra cartella, aggiungere --project "C:\percorso\cartella".

cd "$env:USERPROFILE\Documents\FindCustomerAutomation"
py scripts\workflow.py list

La ricerca usa local-client-prospector e, quando utile, first-customer-finder. La skill find-customer-orchestrator coordina brief, Claude /design, verifica e preview. WORKFLOW.md descrive le regole operative. Il comando /design va provato nella CLI di Claude sul PC Windows prima di usarlo con un cliente reale; non è stato ancora verificato in quella configurazione.

Il pacchetto non invia messaggi Instagram, non effettua deploy di produzione e non elimina preview senza la conferma esplicita di mancata risposta.