@lifeaitools/rdc-skills 0.9.14 → 0.9.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.9.14",
+  "version": "0.9.16",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight builds",
   "keywords": [
     "claude-code",

package/skills/status/SKILL.md

@@ -57,11 +57,20 @@ description: >-
    git branch -v
    ```
 
-6. **Infrastructure health** (if MCP available):
+6. **Dev server health (PM2):**
+   SSH into the Coolify server and check PM2 process state:
+   ```bash
+   SSH_KEY=$(curl -s http://127.0.0.1:52437/v/ssh-key-path)
+   ssh -i "$SSH_KEY" -o StrictHostKeyChecking=no root@64.237.54.189 "pm2 jlist 2>/dev/null"
+   ```
+   Parse the JSON array — for each process note `name`, `pm2_env.status` (online/stopped/errored), and `pm2_env.pm_uptime`.
+   If SSH fails or PM2 returns nothing, note "PM2 unreachable" and continue.
+
+7. **Infrastructure health** (if MCP available):
    - Get infrastructure overview or diagnose issues
    - Report any apps with failed builds or down containers
 
-7. **Present as a compact dashboard:**
+8. **Present as a compact dashboard:**
    ```
    ## Open Epics (N)
    <table>
@@ -71,6 +80,9 @@ description: >-
    ## Recent (48h)
    <list>
    
+   ## Dev Servers (PM2)
+   online: studio canvas lifeai ...   stopped: issho-invest
+   
    ## Deployments
    <green/red/yellow status>
    

package/skills/lab-push/SKILL.md

@@ -1,46 +0,0 @@
----
-name: rdc:lab-push
-description: >-
-  Usage `rdc:lab-push <filename>` — push the artifact in this conversation to the Lab prototype viewer. Commits the file to apps/lab/docs/prototypes/ via POST https://lab.dev.place.fund/api/prototypes/push. Viewable immediately at lab.dev.place.fund/proto/<filename>.
----
-
-# rdc:lab-push — Push Artifact to Lab
-
-Push a JSX, TSX, HTML, or JS artifact from this conversation to the Lab prototype viewer at `lab.dev.place.fund`.
-
-## How it works
-
-1. POST `{ filename, content }` to `https://lab.dev.place.fund/api/prototypes/push`
-2. The endpoint commits the file to `apps/lab/docs/prototypes/` on the `develop` branch via the GitHub Contents API
-3. The file is immediately visible at `https://lab.dev.place.fund/proto/<filename>` — no redeploy needed
-
-## Usage
-
-```
-rdc:lab-push <filename>
-```
-
-- `filename` must end in `.jsx`, `.tsx`, `.html`, or `.js`
-- The artifact content comes from this conversation (the most recent code block, or the artifact the user is referring to)
-
-## Steps
-
-1. Identify the artifact content — the most recent code block in this conversation that the user wants to push, or what they explicitly point to
-2. If filename not provided as an argument, derive one from the artifact (e.g. `my-component.jsx`)
-3. Check if the file already exists: GET `https://lab.dev.place.fund/api/prototypes/content?filename=<filename>` — if it returns a `sha`, include it in the push body so GitHub can update rather than reject
-4. POST to `https://lab.dev.place.fund/api/prototypes/push`:
-   ```json
-   { "filename": "<filename>", "content": "<full file content>", "sha": "<sha if updating>" }
-   ```
-5. On success, respond with: `Pushed → https://lab.dev.place.fund/proto/<filename>`
-
-## Error handling
-
-- 422 from push = filename invalid (wrong extension or path traversal attempt)
-- 503 = credential service unavailable on the lab server
-- 502 = GitHub API error — check if the file already exists and a `sha` is needed
-
-## Notes
-
-- This is the only way to get artifacts from claude.ai into the lab without copy-paste
-- Git history in `apps/lab/docs/prototypes/` is the version store — every save is a commit