docs: update skills and plugin.json for 0.3.0 agentsview integration

Add --source agentsview examples and DB path resolution docs to all
three skill files. Bump plugin.json version from 0.2.0 to 0.3.0.

Author: jakeefr

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "prism",
   "description": "Session intelligence for Claude Code — find why your sessions fail and fix them",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "author": { "name": "jakeefr" },
   "license": "MIT",
   "repository": "https://github.com/jakeefr/prism"

skills/prism-advise/SKILL.md

@@ -41,6 +41,15 @@ For a different project:
 prism advise --project <path>
 ```
 
+From an agentsview database (real API token counts, richer data):
+```bash
+prism advise --source agentsview
+prism advise --source agentsview --agentsview-db /path/to/sessions.db
+```
+
+DB path resolution: `AGENTSVIEW_DATA_DIR` → `AGENT_VIEWER_DATA_DIR` → `~/.agentsview/sessions.db`.
+Note: `--project` cannot be used with `--source agentsview`.
+
 ## Interpreting the output
 
 PRISM prints recommendations with four action types:

skills/prism-analyze/SKILL.md

@@ -32,7 +32,7 @@ Once confirmed installed, proceed with the analysis.
 
 ## Usage
 
-Run the analysis:
+Run the analysis (reads JSONL from ~/.claude/projects/ by default):
 ```bash
 prism analyze
 ```
@@ -67,6 +67,25 @@ This prints each project name, session count, and last-active timestamp.
 Use it when the user asks what projects PRISM has data for, or to confirm
 that sessions are being recorded.
 
+## Agentsview data source
+
+If the user has [agentsview](https://github.com/wesm/agentsview) installed,
+PRISM can read from its SQLite database instead of raw JSONL. This gives
+real API token counts and agentsview's own health scores alongside PRISM's.
+
+```bash
+prism analyze --source agentsview
+prism analyze --source agentsview --agentsview-db /path/to/sessions.db
+prism analyze --source agentsview --json
+```
+
+DB path resolution when `--agentsview-db` is not specified:
+`AGENTSVIEW_DATA_DIR` env → `AGENT_VIEWER_DATA_DIR` env → `~/.agentsview/sessions.db`
+
+Use `--source agentsview` when the user mentions agentsview, asks for real
+token counts, or wants richer session data. Use the default (no flag) when
+they just want a quick analysis from raw session files.
+
 ## What PRISM shows
 - Health scores (A-F) across 5 dimensions per project
 - Token efficiency: CLAUDE.md re-read costs, compaction frequency

skills/prism-dashboard/SKILL.md

@@ -36,6 +36,14 @@ Generate the dashboard without opening a browser:
 prism dashboard --no-open
 ```
 
+From an agentsview database (real API token counts, health score cross-reference):
+```bash
+prism dashboard --source agentsview --no-open
+prism dashboard --source agentsview --agentsview-db /path/to/sessions.db --no-open
+```
+
+DB path resolution: `AGENTSVIEW_DATA_DIR` → `AGENT_VIEWER_DATA_DIR` → `~/.agentsview/sessions.db`.
+
 The dashboard is written to `~/.claude/prism/dashboard.html`. Tell the
 user the exact path so they can open it in their browser.
 
@@ -58,4 +66,4 @@ On most systems this is:
 - The dashboard regenerates every time `prism analyze` or
   `prism dashboard` runs. Reload the browser page after a new analysis.
 - No data leaves the machine. The dashboard reads from local session
-  files only.
+  files (or the agentsview SQLite DB with `--source agentsview`) only.