[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A3DYR7DX133EFQ055CQHSR":3,"skill-same:01M7A3DYR7DX133EFQ055CQHSR":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7A3DYR7DX133EFQ055CQHSR","dev-instance",null,"Run the current worktree as a production-shaped local dev instance — core, Slack, web UI, admin, portal, on a real Pi LLM + Postgres — reachable in Slack as your own bot. Each developer uses their own set of Slack apps from their own machine's pool store, so many worktrees (yours and a teammate's) can run reachable at once without colliding. Use when asked to \u002Fdev-instance, \"spin this up so I can QA it in Slack\", or \"let me test your branch end to end\".","LNdme\u002FSUniv","LNdme","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224572198?v=4","01M7A3DPMXT60BVWPK0X7PMGCZ","01M7A3DPNJRTKYPJVQNHNCWE0W",1,"MIT","https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fdev-instance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dev-instance\ndescription: Run the current worktree as a production-shaped local dev instance — core, Slack, web UI, admin, portal, on a real Pi LLM + Postgres — reachable in Slack as your own bot. Each developer uses their own set of Slack apps from their own machine's pool store, so many worktrees (yours and a teammate's) can run reachable at once without colliding. Use when asked to \u002Fdev-instance, \"spin this up so I can QA it in Slack\", or \"let me test your branch end to end\".\n---\n\n# dev-instance\n\n`dev-instance` runs the current worktree as a full, production-shaped stack on your\nmachine and makes it reachable in Slack as one of _your_ bots. It is the way to QA a\nbranch end to end: real LLM turns, a real sandbox, a real local Postgres (empty by\ndefault; opt in to prod data), and the real Slack\u002Fweb\u002Fadmin surfaces.\n\nUse the repo-root launcher (a thin wrapper over the TypeScript CLI in `scripts\u002Fdev\u002F`;\nevery command accepts `--json` for machine-readable output):\n\n```bash\nbash scripts\u002Fdev-instance.sh up\nbash scripts\u002Fdev-instance.sh status\nbash scripts\u002Fdev-instance.sh down\nbash scripts\u002Fdev-instance.sh doctor\nbash scripts\u002Fdev-instance.sh canary\nbash scripts\u002Fdev-instance.sh restart [child]\nbash scripts\u002Fdev-instance.sh logs [child] [-f]\n```\n\n`npm run dev-instance`, `npm run dev-instance:status`, `npm run dev-instance:down`, and\n`npm run dev-instance:doctor` are equivalent. The Codex-visible skill copy lives at\n`.codex\u002Fskills\u002Fdev-instance\u002FSKILL.md`; keep the two skill descriptions equivalent.\n\n## What `up` Starts\n\n`up` claims one free Slack app slot from **this machine's** pool store (see \"Slack reach\"\nbelow), then spawns a **per-slot supervisor daemon** that owns the production-shaped stack:\n\n- core API + workers\n- Slack Socket Mode plugin (connected as the claimed app's bot)\n- web UI surface\n- admin surface\n- portal front door proxying `\u002Fweb-ui\u002F` and `\u002Fadmin\u002F`\n\nThe supervisor restarts crashed children with backoff, waits for a port to actually free\nbefore respawning (no more EADDRINUSE), health-probes everything every 10s, and writes a\nheartbeat so slot reclaim can tell \"actively in use\" from \"abandoned\".\n\n**`up` only prints success after proving the bot is reachable**: the Slack socket must be\nthe app's _only_ connection (`num_connections == 1`, read from the hello frame) and — when\nthe slot has a `CANARY_CHANNEL` — a posted canary message must arrive back over that same\nsocket. If another machine\u002Fworktree holds a connection to the app (the classic \"boots LIVE\nbut deaf\" failure), `up` detects it, flags the slot for 30 minutes, and auto-rotates to the\nnext one, reporting the thief's hello host. A canary that never returns on a clean socket\nmeans a stale Slack app; `up` flags and rotates past that too.\n\n**Re-running `up` on a live instance is a reload, not a no-op**: it re-reads your shell\nenv, dev.env, and `.env`, diffs against what the children are running, and does a rolling\nrestart + re-verification when anything changed (`--force` to restart regardless,\n`--rotate` to move to a different Slack app).\n\nOpen the portal URL printed by the CLI. Direct web\u002Fadmin URLs are also printed for\ndebugging, but the portal URL is the prod-like path.\n\n## Sandbox: local Docker by default\n\nThe agent's `execute` sandbox runs as a **local Docker container** (`SANDBOX_BACKEND=local`)\nwhen the worktree's code supports it — no cloud credential, no tunnel, no microVM cold\nstarts, and the sandbox reaches core's self-API at `host.docker.internal` directly. Build\nthe image once per machine with `npm run sandbox:local:build` (the CLI warns if it's\nmissing or stale). Use local Docker unless you are specifically testing the cloud path.\n\nFor prod-parity QA, pass `--sandbox \u003Cbackend>` to run against your deployment's real\nsandbox provider instead. That path validates the provider credential and opens a tunnel\nso the remote sandbox can call back to your local core, so it needs whatever that provider\nrequires; the local backend needs nothing but Docker.\n\n## Slack reach: your apps vs a teammate's\n\nThis is the part people get wrong, so it's worth stating plainly.\n\nA Slack app's **Socket Mode** connection is single-owner: if two running instances point\nat the _same_ app, Slack load-balances inbound messages between them and each instance\nsilently loses half. So the rule is **one live instance per Slack app**.\n\nThe way we keep out of each other's way is simple: **every developer has their own set of\nSlack apps**, listed as `poolN.env` files in their **own machine's** pool store\n(`~\u002F.config\u002Fqm\u002Fslack-pool`). `up` claims the first free slot on _this_ machine and boots\nthat app's bot; the script prints its `@handle`. You QA by DMing that bot in\n`example.slack.com`.\n\n- **Your machine** (Alice's): the pool holds `pool1.env … pool10.env`, which are the apps\n  `bot1 … bot10`. So up to 10 worktrees can run reachable at once here; each `up` grabs\n  the next free slot, `down` frees it. DM whichever `@botN` the script printed.\n- **A teammate's machine** (e.g. Carol's): a _different_ set of apps in _their_ local pool\n  store. Their instances claim their apps; yours claim yours. You never collide, because you\n  are never pointing at the same app — and there is no shared registry, no `#worktree`\n  prefix, and no relay to coordinate. Each of you just DMs your own bot.\n\nThe per-machine pool lease (an atomic lock per slot) also stops two worktrees on the _same_\nmachine from grabbing the same slot. Before connecting, `up` sweeps the machine for\norphaned processes still holding the slot's Slack app token (e.g. a plugin another\nworktree's teardown missed) and kills them. If every slot is taken, `up` reclaims one —\nbut **never a slot whose supervisor heartbeat is fresh**: an actively used instance can't\nbe stolen mid-QA; only dead\u002Flegacy leases fall back to the old not-today \u002F 4-hour rule.\n\nTo add capacity, mint more Slack apps from `src\u002Fslack\u002Fmanifest.json` (one Socket Mode\napp each, with `connections:write` for the app-level token) and drop a `poolN.env`\ncontaining `SLACK_BOT_TOKEN` (`xoxb-`), `SLACK_APP_TOKEN` (`xapp-`), and `HANDLE` into your\npool store. The boot canary picks its channel automatically: a channel named `dev-canary`\nif the bot is in one, else a `ci-*` throwaway it is in — never a human channel — and the\ncanary message is deleted right after it round-trips. `CANARY_CHANNEL=\u003Cchannel id>` in the\nslot env overrides. With no eligible channel at all, `up` prints `delivery unverified` (or\nfails under `--strict`).\n\nA forgotten instance cleans itself up: after 8 hours with no Slack events and no CLI\nactions the supervisor tears itself down and frees the slot\n(`DEV_INSTANCE_IDLE_HOURS` overrides; `0` disables).\n\n## Real by Default\n\nThe dev instance should exercise the real system:\n\n- real LLM: needs a model credential for the harness you run. Core supports several\n  (`HARNESS=pi|opencode|codex|claude`); the launcher picks one from the credentials it\n  finds and honours an explicit `HARNESS`. Set the key your chosen harness expects, or\n  pass `DEV_INSTANCE_ALLOW_MOCK=1` for a deliberate no-model wiring check\n- real durability: uses `DATABASE_URL` when supplied; otherwise starts\u002Freuses a local\n  Docker Postgres container and runs core with `SESSION_STORE=postgres` and\n  `RUN_STORE=postgres`\n- production data is never copied into a dev instance\n- captured model context: request capture is on unless overridden, so you can read back what the model was actually sent\n- fast local edits: runs Node surfaces with `--watch` and serves the web UI through\n  Vite HMR on the dev surface instead of a separate browser build loop\n- stale pool recovery: `status` shows each deploy's start time and age; if all pool\n  apps are taken, `up` reclaims a slot not started today or older than 4 hours\n- local admin seed: for a self-provisioned local DB, empty `admin_grants` are seeded\n  from `DEV_INSTANCE_ADMIN_PRINCIPAL` or the local OS user; explicit `ADMIN_GRANTS`\n  still wins\n- local portal auth: the launcher sets a localhost-only portal auth bypass, signing in\n  as `DEV_INSTANCE_ADMIN_PRINCIPAL`, the first `ADMIN_GRANTS` principal, the first\n  durable `org_admin` in Postgres, or the local OS user. Production portal auth remains\n  real OIDC.\n\nOnly use escape hatches for deliberate wiring checks — this is how you ask for _less_ than\nthe full real stack when a test doesn't need it:\n\n```bash\nDEV_INSTANCE_ALLOW_MOCK=1 bash scripts\u002Fdev-instance.sh up\nDEV_INSTANCE_ALLOW_MEMORY=1 bash scripts\u002Fdev-instance.sh up\nDEV_INSTANCE_WATCH=0 bash scripts\u002Fdev-instance.sh up\nDEV_INSTANCE_RECLAIM_STALE=0 bash scripts\u002Fdev-instance.sh up\n```\n\n## Env Discovery\n\nThe launcher reads values from, in priority order: exported shell env, the machine-global\n`~\u002F.config\u002Fqm\u002Fdev.env`, your login shell (for a model credential exported there), and this\nworktree's `.env` (seeded from the main checkout in linked worktrees). Slack pool tokens\ndefault to `~\u002F.config\u002Fqm\u002Fslack-pool`.\n\nWhen a cloud sandbox backend is configured it also validates that provider's access at\nstartup, refreshes a stale provider token from the provider CLI's own logged-in session\nwhere it can, and — if a tunnel binary is present — opens a quick tunnel so sandbox\nself-API calls can reach your local core. None of that runs on the default local backend.\n\n## After Startup\n\nReport the slot, portal URL, Slack handle, and log directory. To test Slack-specific\nbehavior, DM the printed `@\u003Chandle>` (on Alice's machine that's one of `@bot1 … @bot10`)\nin `example.slack.com`; for admin and web behavior, open the printed portal URL. Tear down\nwith `bash scripts\u002Fdev-instance.sh down` when QA is finished.\n\n## Troubleshooting\n\n**Start with `dev doctor` (or `doctor --json`).** It runs the checks that used to take a\ndebugging session by hand — socket exclusivity (`num_connections`), a live canary\nround trip, env\u002Fgit drift since boot, per-child health and restart counts, stale leases,\nport squatters, machine-wide token orphans, Docker daemon — and prints a ranked diagnosis\nwith a remedy per finding. `doctor --fix` applies the safe ones (child restarts).\n\n**Bot never replies to a DM (silent bot).** The new `up` catches the two big causes at\nboot: another live connection to the same app (auto-rotates, names the thief's host) and a\nstale Slack app whose events never arrive (canary fails → flags the slot and rotates). If\ndeafness appears mid-session, the 10s health probe logs `DEGRADED: num_connections=N` in\n`supervisor.log` and the periodic canary flags delivery loss; `dev canary` gives you an\non-demand proof either way. `dev up --rotate` moves to a fresh slot.\n\nFor a slot flagged `canary-failed`, the app itself is stale and needs rebuilding (~5 min):\nat api.slack.com **signed into the example workspace** (the dev console is\nper-workspace-identity — use \"Sign in to another workspace\" if it lists the wrong one):\nCreate New App → From a manifest → paste `src\u002Fslack\u002Fmanifest.json` (give it a unique\n`name` and bot `display_name`; old handles stay taken) → Install to Workspace → Basic\nInformation → App-Level Tokens → Generate with the `connections:write` scope. Write the Bot\ntoken (`xoxb-…`) and app-level token (`xapp-…`) into `poolN.env`, delete `poolN.flag.json`,\nthen run `up` again. (If you own the existing app, just reinstalling it also works.)\n\nTwo smaller gotchas: a freshly-created bot isn't in Slack's \"New message\" people search for a\nminute or two — open its DM deterministically via `conversations.open` (bot token + your user\nid) and navigate to `app.slack.com\u002Fclient\u002F\u003Cteam-id>\u002F\u003CD-channel-id>`. And the browser's Slack\nlogin drops easily during long automated sessions; re-authenticating is a Google SSO you have\nto complete yourself.\n","# dev-instance\n\n`dev-instance` runs the current worktree as a full, production-shaped stack on your\nmachine and makes it reachable in Slack as one of _your_ bots. It is the way to QA a\nbranch end to end: real LLM turns, a real sandbox, a real local Postgres (empty by\ndefault; opt in to prod data), and the real Slack\u002Fweb\u002Fadmin surfaces.\n\nUse the repo-root launcher (a thin wrapper over the TypeScript CLI in `scripts\u002Fdev\u002F`;\nevery command accepts `--json` for machine-readable output):\n\n```bash\nbash scripts\u002Fdev-instance.sh up\nbash scripts\u002Fdev-instance.sh status\nbash scripts\u002Fdev-instance.sh down\nbash scripts\u002Fdev-instance.sh doctor\nbash scripts\u002Fdev-instance.sh canary\nbash scripts\u002Fdev-instance.sh restart [child]\nbash scripts\u002Fdev-instance.sh logs [child] [-f]\n```\n\n`npm run dev-instance`, `npm run dev-instance:status`, `npm run dev-instance:down`, and\n`npm run dev-instance:doctor` are equivalent. The Codex-visible skill copy lives at\n`.codex\u002Fskills\u002Fdev-instance\u002FSKILL.md`; keep the two skill descriptions equivalent.\n\n## What `up` Starts\n\n`up` claims one free Slack app slot from **this machine's** pool store (see \"Slack reach\"\nbelow), then spawns a **per-slot supervisor daemon** that owns the production-shaped stack:\n\n- core API + workers\n- Slack Socket Mode plugin (connected as the claimed app's bot)\n- web UI surface\n- admin surface\n- portal front door proxying `\u002Fweb-ui\u002F` and `\u002Fadmin\u002F`\n\nThe supervisor restarts crashed children with backoff, waits for a port to actually free\nbefore respawning (no more EADDRINUSE), health-probes everything every 10s, and writes a\nheartbeat so slot reclaim can tell \"actively in use\" from \"abandoned\".\n\n**`up` only prints success after proving the bot is reachable**: the Slack socket must be\nthe app's _only_ connection (`num_connections == 1`, read from the hello frame) and — when\nthe slot has a `CANARY_CHANNEL` — a posted canary message must arrive back over that same\nsocket. If another machine\u002Fworktree holds a connection to the app (the classic \"boots LIVE\nbut deaf\" failure), `up` detects it, flags the slot for 30 minutes, and auto-rotates to the\nnext one, reporting the thief's hello host. A canary that never returns on a clean socket\nmeans a stale Slack app; `up` flags and rotates past that too.\n\n**Re-running `up` on a live instance is a reload, not a no-op**: it re-reads your shell\nenv, dev.env, and `.env`, diffs against what the children are running, and does a rolling\nrestart + re-verification when anything changed (`--force` to restart regardless,\n`--rotate` to move to a different Slack app).\n\nOpen the portal URL printed by the CLI. Direct web\u002Fadmin URLs are also printed for\ndebugging, but the portal URL is the prod-like path.\n\n## Sandbox: local Docker by default\n\nThe agent's `execute` sandbox runs as a **local Docker container** (`SANDBOX_BACKEND=local`)\nwhen the worktree's code supports it — no cloud credential, no tunnel, no microVM cold\nstarts, and the sandbox reaches core's self-API at `host.docker.internal` directly. Build\nthe image once per machine with `npm run sandbox:local:build` (the CLI warns if it's\nmissing or stale). Use local Docker unless you are specifically testing the cloud path.\n\nFor prod-parity QA, pass `--sandbox \u003Cbackend>` to run against your deployment's real\nsandbox provider instead. That path validates the provider credential and opens a tunnel\nso the remote sandbox can call back to your local core, so it needs whatever that provider\nrequires; the local backend needs nothing but Docker.\n\n## Slack reach: your apps vs a teammate's\n\nThis is the part people get wrong, so it's worth stating plainly.\n\nA Slack app's **Socket Mode** connection is single-owner: if two running instances point\nat the _same_ app, Slack load-balances inbound messages between them and each instance\nsilently loses half. So the rule is **one live instance per Slack app**.\n\nThe way we keep out of each other's way is simple: **every developer has their own set of\nSlack apps**, listed as `poolN.env` files in their **own machine's** pool store\n(`~\u002F.config\u002Fqm\u002Fslack-pool`). `up` claims the first free slot on _this_ machine and boots\nthat app's bot; the script prints its `@handle`. You QA by DMing that bot in\n`example.slack.com`.\n\n- **Your machine** (Alice's): the pool holds `pool1.env … pool10.env`, which are the apps\n  `bot1 … bot10`. So up to 10 worktrees can run reachable at once here; each `up` grabs\n  the next free slot, `down` frees it. DM whichever `@botN` the script printed.\n- **A teammate's machine** (e.g. Carol's): a _different_ set of apps in _their_ local pool\n  store. Their instances claim their apps; yours claim yours. You never collide, because you\n  are never pointing at the same app — and there is no shared registry, no `#worktree`\n  prefix, and no relay to coordinate. Each of you just DMs your own bot.\n\nThe per-machine pool lease (an atomic lock per slot) also stops two worktrees on the _same_\nmachine from grabbing the same slot. Before connecting, `up` sweeps the machine for\norphaned processes still holding the slot's Slack app token (e.g. a plugin another\nworktree's teardown missed) and kills them. If every slot is taken, `up` reclaims one —\nbut **never a slot whose supervisor heartbeat is fresh**: an actively used instance can't\nbe stolen mid-QA; only dead\u002Flegacy leases fall back to the old not-today \u002F 4-hour rule.\n\nTo add capacity, mint more Slack apps from `src\u002Fslack\u002Fmanifest.json` (one Socket Mode\napp each, with `connections:write` for the app-level token) and drop a `poolN.env`\ncontaining `SLACK_BOT_TOKEN` (`xoxb-`), `SLACK_APP_TOKEN` (`xapp-`), and `HANDLE` into your\npool store. The boot canary picks its channel automatically: a channel named `dev-canary`\nif the bot is in one, else a `ci-*` throwaway it is in — never a human channel — and the\ncanary message is deleted right after it round-trips. `CANARY_CHANNEL=\u003Cchannel id>` in the\nslot env overrides. With no eligible channel at all, `up` prints `delivery unverified` (or\nfails under `--strict`).\n\nA forgotten instance cleans itself up: after 8 hours with no Slack events and no CLI\nactions the supervisor tears itself down and frees the slot\n(`DEV_INSTANCE_IDLE_HOURS` overrides; `0` disables).\n\n## Real by Default\n\nThe dev instance should exercise the real system:\n\n- real LLM: needs a model credential for the harness you run. Core supports several\n  (`HARNESS=pi|opencode|codex|claude`); the launcher picks one from the credentials it\n  finds and honours an explicit `HARNESS`. Set the key your chosen harness expects, or\n  pass `DEV_INSTANCE_ALLOW_MOCK=1` for a deliberate no-model wiring check\n- real durability: uses `DATABASE_URL` when supplied; otherwise starts\u002Freuses a local\n  Docker Postgres container and runs core with `SESSION_STORE=postgres` and\n  `RUN_STORE=postgres`\n- production data is never copied into a dev instance\n- captured model context: request capture is on unless overridden, so you can read back what the model was actually sent\n- fast local edits: runs Node surfaces with `--watch` and serves the web UI through\n  Vite HMR on the dev surface instead of a separate browser build loop\n- stale pool recovery: `status` shows each deploy's start time and age; if all pool\n  apps are taken, `up` reclaims a slot not started today or older than 4 hours\n- local admin seed: for a self-provisioned local DB, empty `admin_grants` are seeded\n  from `DEV_INSTANCE_ADMIN_PRINCIPAL` or the local OS user; explicit `ADMIN_GRANTS`\n  still wins\n- local portal auth: the launcher sets a localhost-only portal auth bypass, signing in\n  as `DEV_INSTANCE_ADMIN_PRINCIPAL`, the first `ADMIN_GRANTS` principal, the first\n  durable `org_admin` in Postgres, or the local OS user. Production portal auth remains\n  real OIDC.\n\nOnly use escape hatches for deliberate wiring checks — this is how you ask for _less_ than\nthe full real stack when a test doesn't need it:\n\n```bash\nDEV_INSTANCE_ALLOW_MOCK=1 bash scripts\u002Fdev-instance.sh up\nDEV_INSTANCE_ALLOW_MEMORY=1 bash scripts\u002Fdev-instance.sh up\nDEV_INSTANCE_WATCH=0 bash scripts\u002Fdev-instance.sh up\nDEV_INSTANCE_RECLAIM_STALE=0 bash scripts\u002Fdev-instance.sh up\n```\n\n## Env Discovery\n\nThe launcher reads values from, in priority order: exported shell env, the machine-global\n`~\u002F.config\u002Fqm\u002Fdev.env`, your login shell (for a model credential exported there), and this\nworktree's `.env` (seeded from the main checkout in linked worktrees). Slack pool tokens\ndefault to `~\u002F.config\u002Fqm\u002Fslack-pool`.\n\nWhen a cloud sandbox backend is configured it also validates that provider's access at\nstartup, refreshes a stale provider token from the provider CLI's own logged-in session\nwhere it can, and — if a tunnel binary is present — opens a quick tunnel so sandbox\nself-API calls can reach your local core. None of that runs on the default local backend.\n\n## After Startup\n\nReport the slot, portal URL, Slack handle, and log directory. To test Slack-specific\nbehavior, DM the printed `@\u003Chandle>` (on Alice's machine that's one of `@bot1 … @bot10`)\nin `example.slack.com`; for admin and web behavior, open the printed portal URL. Tear down\nwith `bash scripts\u002Fdev-instance.sh down` when QA is finished.\n\n## Troubleshooting\n\n**Start with `dev doctor` (or `doctor --json`).** It runs the checks that used to take a\ndebugging session by hand — socket exclusivity (`num_connections`), a live canary\nround trip, env\u002Fgit drift since boot, per-child health and restart counts, stale leases,\nport squatters, machine-wide token orphans, Docker daemon — and prints a ranked diagnosis\nwith a remedy per finding. `doctor --fix` applies the safe ones (child restarts).\n\n**Bot never replies to a DM (silent bot).** The new `up` catches the two big causes at\nboot: another live connection to the same app (auto-rotates, names the thief's host) and a\nstale Slack app whose events never arrive (canary fails → flags the slot and rotates). If\ndeafness appears mid-session, the 10s health probe logs `DEGRADED: num_connections=N` in\n`supervisor.log` and the periodic canary flags delivery loss; `dev canary` gives you an\non-demand proof either way. `dev up --rotate` moves to a fresh slot.\n\nFor a slot flagged `canary-failed`, the app itself is stale and needs rebuilding (~5 min):\nat api.slack.com **signed into the example workspace** (the dev console is\nper-workspace-identity — use \"Sign in to another workspace\" if it lists the wrong one):\nCreate New App → From a manifest → paste `src\u002Fslack\u002Fmanifest.json` (give it a unique\n`name` and bot `display_name`; old handles stay taken) → Install to Workspace → Basic\nInformation → App-Level Tokens → Generate with the `connections:write` scope. Write the Bot\ntoken (`xoxb-…`) and app-level token (`xapp-…`) into `poolN.env`, delete `poolN.flag.json`,\nthen run `up` again. (If you own the existing app, just reinstalling it also works.)\n\nTwo smaller gotchas: a freshly-created bot isn't in Slack's \"New message\" people search for a\nminute or two — open its DM deterministically via `conversations.open` (bot token + your user\nid) and navigate to `app.slack.com\u002Fclient\u002F\u003Cteam-id>\u002F\u003CD-channel-id>`. And the browser's Slack\nlogin drops easily during long automated sessions; re-authenticating is a Google SSO you have\nto complete yourself.\n",{"name":5,"description":7},"main","0ec1548c4ee09bdd34556c95adba28e98014fe13",".codex\u002Fskills\u002Fdev-instance",0,"https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv","https:\u002F\u002Fgithub.com\u002FLNdme","Code, Startup, Innovation","2026-11-12 20:56:27",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add LNdme\u002FSUniv --skill dev-instance",{"tool":37,"command":38},"bunx","bunx skills add LNdme\u002FSUniv --skill dev-instance",{"tool":40,"command":41},"pnpm","pnpm dlx skills add LNdme\u002FSUniv --skill dev-instance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fdev-instance\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",182,"https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fdev-instance\u002Fagents\u002Fopenai.yaml",[52,59,67,74,81,88],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7A3HDC3JGX00FD71DXQ3ZHB","use-shared-credential","When you need to call a service the org has a SHARED credential for (a SERP\u002Fsearch key, a paid-API key, a data-vendor feed, a Git remote) — and the platform has told you that credential is available to this conversation — make the call BY PROXY through the credential broker. You never see the secret; the core stamps it onto the outbound request for you.","https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002Fskills-seed\u002Fuse-shared-credential\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7A3HAP05FJJT3N54W3MKZPH","taste-skill","Design taste and process for anything a person will look at in a browser — landing page, dashboard, prototype, deck. The default design driver for a browsable artifact, with an anti-slop playbook for the visual language.","https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002Fskills-seed\u002Ftaste-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002Fskills-seed\u002Ftaste-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7A3H6FDDJY6GFTKDNN9Y76F","publish","Publish a long-lived internal web app, site, or dashboard from the agent computer. Scope-bound (only the owner's scope, plus whoever you share it with, can reach it), immutable versions with rollback, a stable friendly link. No public URL.","https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002Fskills-seed\u002Fpublish\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7A3H34CF5J86QMAX3FX4X5T","popular-web-designs","54 real-world design systems (Stripe, Linear, Vercel, Notion, Apple…) as ready-to-paste HTML\u002FCSS — exact colors, typography, components, and spacing for styling a page after a known brand.","https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002Fskills-seed\u002Fpopular-web-designs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7A3H0Z7SNWP9VXPZBTY59ZZ","morning-digest","Assemble and deliver one short morning digest for the person who owns the cron — what changed overnight in the sources they already connected, and what it means for their day.","https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002Fskills-seed\u002Fmorning-digest\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7A3GXSXPNKHRNC7M6KC6BV5","memory","Deliberately search, add to, or curate your long-term memory with the `memory` tool — beyond the automatic recall\u002Fcapture every turn already does. Use when asked who someone is or what they're working on, when you learn a durable fact worth keeping now, or when your notebook holds stale or wrong entries you should clean up.","https:\u002F\u002Fgithub.com\u002FLNdme\u002FSUniv\u002Fblob\u002Fmain\u002Fskills-seed\u002Fmemory\u002FSKILL.md",[],[]]