fastpass-cli 0.1.0 → 0.1.1

package/README.md

@@ -1,6 +1,6 @@
 # fastpass
 
-Cloudflare Access in 60 seconds. No enterprise jargon.
+Cloudflare Access in 60 seconds.
 
 ## What you want → What it does
 
@@ -16,7 +16,7 @@ Cloudflare Access in 60 seconds. No enterprise jargon.
 ## Quickstart
 
 ```sh
-npx fastpass
+npx fastpass-cli
 ```
 
 That's it. The interactive wizard walks you through everything.
@@ -25,40 +25,40 @@ That's it. The interactive wizard walks you through everything.
 
 ```sh
 # Protect with email login (zero config)
-npx fastpass protect staging.myapp.com --auth email --allow "me@gmail.com"
+npx fastpass-cli protect staging.myapp.com --auth email --allow "me@gmail.com"
 
 # Protect with GitHub login, allow anyone at your company
-npx fastpass protect staging.myapp.com --auth github --allow "*@company.com"
+npx fastpass-cli protect staging.myapp.com --auth github --allow "*@company.com"
 
 # Protect with GitHub login, restrict to a GitHub org
-npx fastpass protect staging.myapp.com --auth github --allow "org:my-github-org"
+npx fastpass-cli protect staging.myapp.com --auth github --allow "org:my-github-org"
 
 # Protect with Google login, allow everyone (just require login)
-npx fastpass protect admin.myapp.com --auth google --allow "everyone"
+npx fastpass-cli protect admin.myapp.com --auth google --allow "everyone"
 
 # List protected domains
-npx fastpass list
+npx fastpass-cli list
 
 # Remove protection
-npx fastpass remove staging.myapp.com
+npx fastpass-cli remove staging.myapp.com
 
 # Overview dashboard — team, apps, IdPs, recent activity
-npx fastpass status
+npx fastpass-cli status
 
 # Recent access events (last 25)
-npx fastpass logs
+npx fastpass-cli logs
 
 # Filter events to one domain, last 10
-npx fastpass logs staging.myapp.com --limit 10
+npx fastpass-cli logs staging.myapp.com --limit 10
 
 # Events since a specific date
-npx fastpass logs --since 2025-01-15
+npx fastpass-cli logs --since 2025-01-15
 
 # Detailed config for a specific app
-npx fastpass inspect staging.myapp.com
+npx fastpass-cli inspect staging.myapp.com
 
 # Interactive app picker
-npx fastpass inspect
+npx fastpass-cli inspect
 ```
 
 ## Prerequisites
@@ -98,7 +98,7 @@ If you already use wrangler:
 
 ```sh
 npx wrangler login
-npx fastpass
+npx fastpass-cli
 ```
 
 > **Note:** Wrangler's default OAuth token does not include Access scopes. If you use `wrangler login` for deploying Workers but get permission errors from fastpass, you'll need a dedicated API token (Option A). The wrangler OAuth scopes cover Workers, KV, D1, Pages, etc. — but not Cloudflare Access.
@@ -128,7 +128,7 @@ Under the hood, fastpass calls the Cloudflare API to:
 3. **Create an Access Application** on your domain with an allow policy
 4. Your domain now shows a login page before granting access
 
-All of this maps to Cloudflare's [Zero Trust Access](https://developers.cloudflare.com/cloudflare-one/policies/access/) product — fastpass just removes the jargon and manual steps.
+All of this maps to Cloudflare's [Zero Trust Access](https://developers.cloudflare.com/cloudflare-one/policies/access/) product — fastpass just removes the complexity.
 
 ## FAQ
 
@@ -142,7 +142,7 @@ Run `protect` again on the same domain with a different `--auth` flag, or config
 fastpass detects existing identity providers and reuses them.
 
 **How do I see what's going on?**
-Run `npx fastpass status` for an overview, `npx fastpass logs` for recent events, or `npx fastpass inspect <domain>` for detailed app config.
+Run `npx fastpass-cli status` for an overview, `npx fastpass-cli logs` for recent events, or `npx fastpass-cli inspect <domain>` for detailed app config.
 
 **How do I manage users/policies after setup?**
 Use the [Cloudflare Zero Trust dashboard](https://one.dash.cloudflare.com).

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "fastpass-cli",
-  "version": "0.1.0",
-  "description": "Cloudflare Access in 60 seconds. No enterprise jargon.",
+  "version": "0.1.1",
+  "description": "Cloudflare Access in 60 seconds.",
   "type": "module",
   "bin": {
     "fastpass": "./bin/fastpass.js"

package/skill/fastpass-skill.md

@@ -22,13 +22,13 @@ You are helping the user set up Cloudflare Access on their domain using the `fas
 ### Interactive mode
 Run the wizard and let the user answer prompts:
 ```bash
-npx fastpass
+npx fastpass-cli
 ```
 
 ### One-liner mode
 If the user has already told you the domain, auth method, and who should have access:
 ```bash
-npx fastpass protect <domain> --auth <email|github|google> --allow "<rule>"
+npx fastpass-cli protect <domain> --auth <email|github|google> --allow "<rule>"
 ```
 
 Allow rules:
@@ -39,22 +39,22 @@ Allow rules:
 
 ### List protected domains
 ```bash
-npx fastpass list
+npx fastpass-cli list
 ```
 
 ### Remove protection
 ```bash
-npx fastpass remove <domain>
+npx fastpass-cli remove <domain>
 ```
 
 ### Status dashboard
 ```bash
-npx fastpass status
+npx fastpass-cli status
 ```
 
 ### View recent access logs
 ```bash
-npx fastpass logs [domain] --limit 25 --since 2025-01-15
+npx fastpass-cli logs [domain] --limit 25 --since 2025-01-15
 ```
 
 Options:
@@ -64,7 +64,7 @@ Options:
 
 ### Inspect app configuration
 ```bash
-npx fastpass inspect [domain]
+npx fastpass-cli inspect [domain]
 ```
 
 If no domain is provided, shows an interactive picker. Displays: domain, type, session duration, allowed identity providers (resolved to names), and policy rules translated to plain English.
@@ -87,6 +87,6 @@ When the user asks to protect a domain, gather these three things:
 2. **Auth method** — email (easiest), github, or google
 3. **Access rule** — who should be allowed in
 
-Then construct and run the appropriate `npx fastpass` command.
+Then construct and run the appropriate `npx fastpass-cli` command.
 
 If the user is unsure, recommend **email** auth — it requires zero external setup.

package/src/cli.js

@@ -14,7 +14,7 @@ export function run() {
 
   program
     .name('fastpass')
-    .description('Cloudflare Access in 60 seconds. No enterprise jargon.')
+    .description('Cloudflare Access in 60 seconds.')
     .version('0.1.0');
 
   // Default action (no subcommand) — run the protect wizard