skeptic-cli 0.2.0 → 0.2.1

package/AGENTS.md

@@ -15,6 +15,11 @@ skeptic inspect <url> --interactive --compact
 skeptic run tests/<scenario>.spec.ts --observability --video --trace
 ```
 
+Specs import from the project dependency `skeptic-cli`. A normal `skeptic init`
+writes that dependency to `package.json`; run `npm install` before
+`skeptic run`, or re-run it if specs fail with `Cannot find package
+'skeptic-cli'`.
+
 Use `skeptic observe <url>` when you need a one-off QA capture without writing a
 spec.
 

package/README.md

@@ -27,8 +27,12 @@ skeptic --help
 ## Quick Start
 
 ```bash
+# Install the CLI
+npm install -g skeptic-cli
+
 # Initialize a project
 skeptic init
+npm install
 
 # Discover stable selectors before authoring a test
 skeptic inspect https://example.com
@@ -165,9 +169,13 @@ skeptic run --shard-split 4 --shard-index 1
 skeptic run --watch
 ```
 
-`skeptic tui` is the discoverable interactive entrypoint. `skeptic run` opens
-the same TUI automatically in an interactive terminal when the console reporter
-is active; use `skeptic run --no-tui` for plain console output.
+`skeptic tui` is the discoverable interactive entrypoint, matching Expect's
+explicit `expect tui` model. `skeptic run` is the plain spec runner for scripts,
+CI, and agent-invoked regression checks.
+
+Specs import from `skeptic-cli`, so project dependencies must be installed. A
+normal `skeptic init` writes the dependency into `package.json`; run
+`npm install` once before `skeptic run`.
 
 Important flags:
 

package/agent-skills/skeptic/SKILL.md

@@ -11,13 +11,19 @@ Use Skeptic when a coding agent needs browser evidence: page inspection, TypeScr
 
 ## Choose The Surface
 
+- Human interactive test run: run `skeptic tui`.
 - One-off QA or bug hunt: run `skeptic observe <url> --full-page`.
 - Persistent regression coverage: run `skeptic inspect <url> --interactive --compact --with-playwright-hints`, write a `tests/*.spec.ts`, then run `skeptic run`.
-- Changed-code verification: run `skeptic run --diff` when the project has specs, or use `skeptic generate --diff` to create one.
+- Changed-code verification: run existing specs with `skeptic run`, or use `skeptic generate --diff` to create one first.
 - Agent-integrated browser work: if Skeptic MCP tools are available, use `browser_open`, `browser_snapshot`, `browser_playwright`, `browser_screenshot`, `browser_console_logs`, `browser_network_requests`, `browser_performance_metrics`, `browser_accessibility_audit`, and `browser_close`.
 
 If the `skeptic` binary is not on PATH, try `npx skeptic-cli` or `npx --yes skeptic-cli@latest`.
 
+Specs import from the project dependency `skeptic-cli`. A normal `skeptic init`
+writes that dependency to `package.json`. If specs fail with `Cannot find
+package 'skeptic-cli'`, run `npm install` in the project before re-running
+Skeptic.
+
 ## Fast Loop
 
 ```bash