MAX-526: fix Claude plugin install flow

.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "ship",
       "description": "Health-check 30+ CLIs/tokens before you deploy, then run the full GTM pipeline: validate → strategy → awareness → launch → measure.",
-      "version": "0.2.0",
+      "version": "0.3.0",
       "author": {
         "name": "maxtechera",
         "url": "https://github.com/maxtechera"

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ship",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Credentials preflight + GTM pipeline. Health-check 30+ CLIs/tokens, then execute idea → validate → market → sell → measure.",
   "author": {
     "name": "maxtechera",
@@ -10,6 +10,6 @@
   "repository": "https://github.com/maxtechera/ship",
   "license": "MIT",
   "keywords": ["credentials", "preflight", "gtm", "ship", "launch", "deploy", "health-check", "pipeline"],
-  "skills": ["credentials/SKILL.md", "ship-engine/SKILL.md", "supervisors/engine/SKILL.md"],
+  "skills": "./skills/",
   "hooks": {}
 }

README.md

@@ -7,7 +7,8 @@
 
 Claude Code:
 ```
-/plugin marketplace add maxtechera/ship
+claude plugin marketplace add maxtechera/ship
+claude plugin install ship@ship
 ```
 
 OpenClaw:
@@ -40,14 +41,23 @@ A 9-agent GTM team boots on first run. The coordinator reads your Linear tickets
 
 ### Claude Code
 ```
-/plugin marketplace add maxtechera/ship
+claude plugin marketplace add maxtechera/ship
+claude plugin install ship@ship
 ```
 
+This adds the `maxtechera/ship` marketplace, then installs the `ship` plugin from it.
+
 ### Update
 ```
 claude plugin update ship@ship
 ```
 
+### Verify
+```bash
+/credentials
+/ship
+```
+
 ### OpenClaw
 ```bash
 clawhub install ship

skills/credentials/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: credentials
+version: "0.3.0"
+description: "Health-check 30+ CLIs and API tokens before you deploy. Agent-executed preflight using the ship credentials registry."
+argument-hint: ''
+allowed-tools: Bash, Read
+homepage: https://github.com/maxtechera/ship
+repository: https://github.com/maxtechera/ship
+author: maxtechera
+license: MIT
+user-invocable: true
+triggers:
+  - credentials
+  - credentials check
+  - check credentials
+  - check tokens
+---
+
+# credentials
+
+Health-check the CLI tools and API tokens your agents depend on. Run before every deploy, before team creation, and before any pipeline stage that needs external access.
+
+## How to run
+
+```bash
+python3 credentials/scripts/check_local.py
+```
+
+Useful variants:
+
+```bash
+python3 credentials/scripts/check_local.py --quiet
+python3 credentials/scripts/check_local.py --fix
+python3 credentials/scripts/check_local.py --only "github,railway,vercel,openai,anthropic"
+```
+
+## Required references
+
+Before acting, read these repo files as needed:
+
+- `credentials/SKILL.md`
+- `credentials/registry/core.yml`
+- `credentials/scripts/check_local.py`
+
+## Output expectations
+
+- Report missing tools or tokens clearly.
+- Prefer actionable fix commands.
+- Block deploy work when required credentials are missing.

skills/ship/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: ship
+version: "0.3.0"
+description: "GTM pipeline with team mode. /ship spawns coordinator + executor + critic team, renders a live dashboard, and routes active runs by stage."
+argument-hint: 'ship (dashboard + team), ship create "<idea>", ship status [RUN-ID], ship run <RUN-ID>'
+allowed-tools: Bash, Read, Write
+homepage: https://github.com/maxtechera/ship
+repository: https://github.com/maxtechera/ship
+author: maxtechera
+license: MIT
+user-invocable: true
+triggers:
+  - ship
+  - ship create
+  - ship status
+  - ship run
+---
+
+# ship
+
+Run `/ship` once. A coordinator team spawns, the dashboard renders, and work starts moving.
+
+Use this skill when the user wants to create, resume, or inspect a GTM run.
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `/ship` | Spawn the coordinator team and render the live dashboard |
+| `/ship create "<idea>"` | Create a new run ticket, preflight credentials, and hand off to the engine |
+| `/ship status [RUN-ID]` | Read the active run, stage, last update, and blockers |
+| `/ship run <RUN-ID>` | Resume an existing run |
+
+## Required references
+
+Before acting, read these repo files as needed:
+
+- `SKILL.md`
+- `engine/WORKFLOW.md`
+- `credentials/registry/core.yml`
+- `supervisors/engine/SKILL.md`
+- `content/engine/SKILL.md`
+
+## Notes
+
+- Run credential preflight before deploy actions.
+- Use orchestrator-style verification before advancing stages.
+- Keep the dashboard and run state aligned with the active Linear ticket.