@prowl-ai/prowl-skill 0.5.5 → 0.5.6

package/CHANGELOG.md

@@ -1,5 +1,52 @@
 # Changelog
 
+## v0.5.6 — 2026-08-16
+
+Package `@prowl-ai/prowl-skill` 0.5.6 · plugins `prowl` 0.4.3 (unchanged), `prowl-cli`
+0.2.6.
+
+The last open item from the `/skill-audit` run, and the tail the CLI's own release left
+behind.
+
+### Added
+
+- **`test/evals/`** — the audit's item 8. `triggers.json` carries twenty queries with
+  the split written down and held fixed; `scenarios.json` carries six behavioural
+  scenarios, three per skill; `fixtures/` holds the inputs.
+
+  **Ten of the twenty queries should fire nothing**, and those are the ones worth
+  having. They are near-misses against skills that actually sit beside these two: an
+  SEO audit of your *own* site, a Google Ads audit of your *own* account, competitor
+  *UI* research, building an MCP server. A skill that wins a prompt it should lose is
+  as much a defect as one that never fires, and it is the harder one to notice because
+  it produces an answer.
+
+  Four of the six scenarios encode something that already went wrong or already costs
+  money: `execution_mode` rather than `tier`, discovery before a metered call, a
+  prompt-injection fixture with the payload in an HTML comment, and a scenario that
+  hands the agent a live-looking `prowl_` key to see whether it protects it.
+
+- **`test/evals_test.js`** — ten checks on the *shape* of that data: the negatives are
+  really half the set, the split is stated rather than inferred, both skills appear on
+  both sides of it, no fixture is named `SKILL.md`.
+
+  **It cannot tell you the skills pass, and says so.** There is no runner; the queries
+  go to a model. The README states in its own words that the evals have never been run,
+  and a test asserts that sentence is still there — because prose drifts, and the
+  pressure to delete it arrives the first time somebody wants a green.
+
+- **`check:cli` notices a version that is no longer latest.** A **note**, never a
+  failure: the command surface may be identical, so it is not a falsehood. This
+  repository was in exactly that state an hour ago — the CLI published `0.2.1` while
+  the page still documented `0.2.0`, every check green, the page quietly pointing at a
+  version `npm install` no longer gives you.
+
+### Fixed
+
+- `metadata.documents_cli` and the page's own sentence now say `0.2.1`, which is what
+  npm serves as `latest`.
+
+## v0.5.5 — 2026-08-16
 ## v0.5.5 — 2026-08-16
 
 Package `@prowl-ai/prowl-skill` 0.5.5 · plugins `prowl` 0.4.3, `prowl-cli` 0.2.5.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prowl-ai/prowl-skill",
-  "version": "0.5.5",
+  "version": "0.5.6",
   "description": "The Prowl plugin: install/usage skills, the hosted MCP config, and the live status widget that makes a running Prowl call, its progress and its cost visible in the terminal. This package is the installer CLI.",
   "keywords": [
     "prowl",

package/plugins/prowl-cli/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "prowl-cli",
   "displayName": "Prowl CLI",
   "description": "Prowl CLI skill: drive the 448-tool Prowl market-intelligence catalog from the shell with @prowl-ai/cli — no MCP server required.",
-  "version": "0.2.5",
+  "version": "0.2.6",
   "author": {
     "name": "Prowl",
     "email": "support@prowl.chat",

package/plugins/prowl-cli/.codex-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "prowl-cli",
   "displayName": "Prowl CLI",
-  "version": "0.2.5",
+  "version": "0.2.6",
   "description": "Prowl CLI skill: drive the 448-tool Prowl market-intelligence catalog from the shell with @prowl-ai/cli — no MCP server required.",
   "author": {
     "name": "Prowl",

package/plugins/prowl-cli/skills/prowl-cli/SKILL.md

@@ -5,11 +5,11 @@ license: MIT
 compatibility: Requires Node.js 18+, the `@prowl-ai/cli` npm package (installed globally or run via npx) and a Prowl API key; speaks MCP protocol 2025-06-18 to prowl.chat over the network.
 metadata:
   author: prowl.chat
-  version: "0.2.5"
+  version: "0.2.6"
   # The @prowl-ai/cli release this page describes. NOT the plugin version above:
   # they are different things that happened to both read 0.2.x, and nothing
   # compared them until scripts/check-cli.js did.
-  documents_cli: "0.2.0"
+  documents_cli: "0.2.1"
 ---
 
 # Prowl CLI — market intelligence from the shell
@@ -26,8 +26,8 @@ Prowl API keys (`prowl_...`) are **billing-bearing** — treat them as secrets a
 npm install -g @prowl-ai/cli
 ```
 
-**This page documents CLI `0.2.0`**, which is what npm serves as `latest`. On `0.1.1`
-or older only `auth`, `tools`, `call`, `analyze`, `wallet` and `version` exist and
+**This page documents CLI `0.2.1`**, which is what npm serves as `latest`. On `0.1.1` or
+older only `auth`, `tools`, `call`, `analyze`, `wallet` and `version` exist and
 everything else answers `Unknown command` — `prowl version` says which you have.
 
 Every command, flag, exit code and default below was read out of the published