@codyswann/lisa 2.178.0 → 2.178.2

package/plugins/src/base/skills/jam-access/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: jam-access
-description: "Vendor-neutral access layer for Jam. Jam triage rules and skills MUST delegate through this skill rather than calling Jam MCP tools directly. Resolves Jam MCP first when available, then falls back to JAM_PAT bearer auth for headless routines."
+description: "Vendor-neutral access layer for Jam. Jam triage rules and skills MUST delegate through this skill rather than calling Jam MCP tools directly. Resolves Jam MCP first when available, then falls back to the JAM_PAT-authenticated Jam CLI for headless routines."
 allowed-tools: ["Bash", "Read", "Skill"]
 ---
 
@@ -24,16 +24,16 @@ Return parsed JSON or a concise structured summary in a `<result>` block.
 Probe in order:
 
 1. Jam MCP, if the tool is available and authenticated.
-2. `JAM_PAT` bearer token against Jam's MCP/trace HTTP substrate.
+2. Jam CLI authenticated with `JAM_PAT`.
 
-Jam documents personal access tokens for MCP clients so a browser OAuth flow is
-not required. The headless tier uses:
+Jam documents a PAT-authenticated CLI that is cleaner for remote routines than
+editing `.mcp.json` headers. The headless tier uses:
 
 ```bash
-curl -sS "https://mcp.jam.dev/mcp" \
-  -H "Authorization: Bearer $JAM_PAT" \
-  -H "Content-Type: application/json" \
-  --data-binary "$PAYLOAD"
+curl -fsSL https://native.jam.dev/install | bash
+export PATH="$HOME/.local/bin:$PATH"
+printf '%s' "$JAM_PAT" | jam auth login --token
+jam skills install
 ```
 
 If neither tier works, fail with:
@@ -45,7 +45,8 @@ Error: no Jam access substrate available. Authenticate the Jam MCP or set JAM_PA
 ## Invariants
 
 - Fallback is gated on `JAM_PAT`; do not retry Jam MCP failures blindly.
-- Never commit a Jam PAT into `.mcp.json`. Use env interpolation in host MCP
-  config, for example `Authorization: Bearer ${JAM_PAT}`.
-- If a requested operation is not yet mapped to the Jam HTTP substrate, surface
+- Never commit a Jam PAT into `.mcp.json` or any generated setup artifact.
+- Headless Jam access requires `native.jam.dev` for the installer and
+  `api.jam.dev` for CLI/API calls in any custom remote network allowlist.
+- If a requested operation is not yet mapped to the Jam CLI substrate, surface
   that exact missing adapter instead of pretending the trace is unavailable.