[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JDQMM2ECZ8EXXJW02JWEP3":3,"skill-same:01M6JDQMM2ECZ8EXXJW02JWEP3":98},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6JDQMM2ECZ8EXXJW02JWEP3","mission-control",null,"Deploy, configure, and troubleshoot Mission Control (OpenClaw\u002FAppie fleet dashboard). Use when setting up MC, fixing access issues, or managing gateways.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Ffleet\u002Fmission-control\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[31,32,33,34,5,35,36,37,38,39,40,41,42,43,44,45,46,47],"mission","control","mission control","configure","fleet","mc","up","use","openclaw","access","nextjs","gateways","issues","deployment","deploy","troubleshoot","dashboard","2026-11-10 10:12:30",false,"---\nname: mission-control\ndescription: Deploy, configure, and troubleshoot Mission Control (OpenClaw\u002FAppie fleet dashboard). Use when setting up MC, fixing access issues, or managing gateways.\ntags: [fleet, dashboard, mission-control, nextjs, deployment]\n---\n\n# Mission Control — Fleet Dashboard\n\nOpen-source agent orchestration dashboard (Next.js 16, builderz-labs fork with Weblyfe skin). **Canonical deployment runs on `appie-mc-1` (Hetzner), NOT the Mac Mini.** Systemd service `mission-control`, port 3000, tailnet-only via `tailscale serve`.\n\nThe Mac Mini runs the **heartbeat** (`mc-heartbeat-manifest.py`, `~\u002Fclawd\u002Ftools\u002F`) that pushes agent status to MC-1. Local MC clones on the mini are planning\u002Fstaging copies only — never run production tasks against them.\n\n## Access\n\n- **Canonical URL:** `https:\u002F\u002Fappie-mc-1.tail61f54b.ts.net` (tailnet-only)\n- **Tailnet IP:** `100.107.179.3` (reachable via appie-2 hop if MagicDNS is off on mini)\n- **Access pattern:** `ssh appie-2 \"curl -s http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\"`\n- Default creds: see `references\u002Fcredentials.md`\n\n## Deploy model (NEVER edit `\u002Fopt\u002Fmission-control` directly on mc-1)\n\nMC-1 uses a gated wave-deploy with auto-rollback. The full process, branch naming conventions, and verification checklist are in `references\u002Fmc-deploy-handoff.md`. Key rules:\n- Hardlink copy (`cp -al`) to `\u002Fopt\u002Fmc-build`, overlay changed source files, build with pnpm, atomic swap → `systemctl restart`\n- Backup DB before every deploy\n- Verify: health 200, correct BUILD_ID, agents ≥21, `\u002Fapi\u002Fknowledge\u002Fgraph source=cognify-kb`\n- Preserve `.env.local` across deploys (contains FLEET_MEMORY_URL, LOCAL_LLM_API_KEY, MC_DISPATCH_MODEL, etc.)\n\n## Heartbeat (Mac Mini → MC-1)\n\nThe fleet heartbeat daemon lives on the Mac Mini at `~\u002Fclawd\u002Ftools\u002Fmc-heartbeat-manifest.py` (301 lines, Python 3). It POSTs agent status (crons, skills, integrations) to MC-1's `\u002Fapi\u002Fagents\u002F\u003Cagent>\u002Fheartbeat` endpoint every 60s.\n\n**Mac Mini agents run via launchd (60s interval):**\n- `com.weblyfe.mc-heartbeat-appie1` — Appie-1\n- `com.weblyfe.mc-heartbeat-opus` — Appie-Opus\n- `com.weblyfe.mc-heartbeat-appie4` — Appie-4 (CFO, separate Hermes instance)\n\n**Remote agents run via systemd timer (60s):**\n- Appie-2 (Hetzner): `\u002Fetc\u002Fsystemd\u002Fsystem\u002Fmc-heartbeat-appie2.{service,timer}` — runs `\u002Fopt\u002Fmc-heartbeat-manifest.py --agent Appie-2`\n- Appie-3 (Hetzner): same pattern via appie-2 hop — `\u002Fopt\u002Fmc-heartbeat-manifest.py --agent Appie-3`\n\n**Critical script detail — `MC_TAILSCALE_IP`:** The script's IP fallback must point to MC-1's Tailscale IP (`100.107.179.3`). If the Mac Mini has MagicDNS off, the script falls back to a direct HTTPS connection to this IP. A wrong IP here (e.g., the mini's own `100.101.29.56`) causes SSL errors on every heartbeat.\n\n**Sync to remote agents after script changes:**\n```bash\nscp ~\u002Fclawd\u002Ftools\u002Fmc-heartbeat-manifest.py appie-2:\u002Fopt\u002Fmc-heartbeat-manifest.py\nssh appie-2 \"scp \u002Fopt\u002Fmc-heartbeat-manifest.py root@100.69.131.51:\u002Fopt\u002Fmc-heartbeat-manifest.py\"\n```\n\n**Diagnose heartbeats:**\n```bash\n# Mac Mini: check launchd logs\ncat ~\u002FLibrary\u002FLogs\u002Fmc-heartbeat-appie1.log\ncat ~\u002FLibrary\u002FLogs\u002Fmc-heartbeat-appie1.err.log\n\n# Remote: check systemd logs\nssh appie-2 \"journalctl -u mc-heartbeat-appie2 --no-pager -n 5\"\nssh appie-2 \"ssh -n root@100.69.131.51 'journalctl -u mc-heartbeat-appie3 --no-pager -n 5'\"\n\n# Dry-run test (no POST, just collect and print)\npython3 ~\u002Fclawd\u002Ftools\u002Fmc-heartbeat-manifest.py --agent Appie-1 --dry-run\n```\n\n## Accessing MC-1 from the Mac Mini\n\nThe Mac Mini has **MagicDNS off** — `appie-mc-1.tail61f54b.ts.net` won't resolve. Use the Tailnet IP directly, or hop through appie-2:\n\n```bash\n# Direct (from mini, if Tailnet IP is reachable)\ncurl http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\n\n# Via appie-2 hop\nssh appie-2 \"curl -s --max-time 5 http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\"\n\n## Pitfalls\n\n### 0. MC-1 unreachable from Mac Mini\n\n**Root cause:** Mac Mini has MagicDNS off. `appie-mc-1.tail61f54b.ts.net` won't resolve.\n\n**Fix:** Use Tailnet IP directly (`100.107.179.3`) or hop through appie-2 (`ssh appie-2 \"curl http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\"`).\n\n### 1. All agents show \"idle\" \u002F stale status\n\n### 1. All agents show \"idle\" \u002F stale status\n\n**Root cause:** Heartbeat not running on the Mac Mini. `mc-heartbeat-manifest.py` is NOT in launchd.\n\n**Fix:** Start it manually or add to launchd (see Heartbeat section above). Without heartbeats, MC-1 stores the last known status but never updates.\n\n### 2. MC-1 server appears DOWN\n\n**Root cause:** The `mission-control` systemd service on appie-mc-1 may have stopped. The box itself is usually alive on Tailscale.\n\n**Diagnose:**\n```bash\nssh appie-2 \"ssh -n root@100.107.179.3 'systemctl is-active mission-control'\"\nssh appie-2 \"curl -s --max-time 5 http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\"\n```\n\n**Fix:**\n```bash\nssh appie-2 \"ssh -n root@100.107.179.3 'systemctl restart mission-control'\"\n# Wait 5s, then verify health check\nssh appie-2 \"curl -s --max-time 10 http:\u002F\u002F100.107.179.3:3000\u002Flogin\"\n```\n\n### 3. Dispatch not working (tasks stuck)\n\n**Root cause:** `MC_DISPATCH_MODEL` pointing at wrong provider, or dispatch routing stripped prefix → routes to Anthropic with no key.\n\n**Fix (on mc-1):** Set in `.env.local`:\n```\nMC_DISPATCH_MODEL=litellm\u002Fdeepseek\u002Fdeepseek-v4-flash\nLOCAL_LLM_ENDPOINT=https:\u002F\u002Fopenrouter.ai\u002Fapi\u002Fv1\n```\nThe `litellm\u002F` prefix preserves provider routing. Never use `provider: auto`.\n\n### 5. Routing 404s on New Projects\nWhen creating a new Vercel project from terminal, it may default to a generic name or have `autoExposeSystemEnvs` \u002F `ssoProtection` enabled which causes a 404 \u002F 302 wall for unauthenticated agents.\n**Fix:** Force link to existing project name: `vercel link --project \u003Cname> --yes`. Ensure SSO is disabled via `PATCH \u002Fv9\u002Fprojects\u002F{id}` body `{\"ssoProtection\": null, \"autoExposeSystemEnvs\": false}`.\n\n### 6. Domain ownership (403 Forbidden)\nIf `GET \u002Fv5\u002Fdomains\u002F{domain}` returns 403, the domain belongs to a different Vercel account\u002Fuser, not just a different team on the current token.\n**Verification:** Check all stored tokens: `grep -r \"VERCEL_TOKEN\" ~\u002F.hermes\u002F.env`. If all fail, the user must manually remove the domain from the old account.\n\n## References\n\n- `references\u002Fmc-feature-roadmap.md` — open features and defects from the July 4 handoff audit\n\n### 5. Routing 404s on New Projects\nWhen creating a new Vercel project from terminal, it may default to a generic name or have `autoExposeSystemEnvs` \u002F `ssoProtection` enabled which causes a 404 \u002F 302 wall for unauthenticated agents.\n**Fix:** Force link to existing project name: `vercel link --project \u003Cname> --yes`. Ensure SSO is disabled via `PATCH \u002Fv9\u002Fprojects\u002F{id}` body `{\"ssoProtection\": null, \"autoExposeSystemEnvs\": false}`.\n\n### 6. Domain ownership (403 Forbidden)\nIf `GET \u002Fv5\u002Fdomains\u002F{domain}` returns 403, the domain belongs to a different Vercel account\u002Fuser, not just a different team on the current token.\n**Verification:** Check all stored tokens: `grep -r \"VERCEL_TOKEN\" ~\u002F.hermes\u002F.env`. If all fail, the user must manually remove the domain from the old account.\n\n## References\n\n- `references\u002Faccess-patterns.md` — full MC_ALLOWED_HOSTS proxy logic and access control\n- `references\u002Flog-patterns.md` — common Hermes log warnings and their meanings\n- `references\u002Ffleet-topology.md` — current Appie fleet layout (local vs remote agents)\n- `references\u002Fsession-context-kanban.md` — mirroring session context into MC kanban\n- `references\u002Ffleet-context-ingestion.md` — fleet-wide context ingestion workflow\n- `references\u002Fmc-deploy-handoff.md` — MC-1 wave deploy process, branches, access topology, and verification checklist\n- `references\u002Fmc-feature-roadmap.md` — open features and defects from the July 4 handoff audit\n","# Mission Control — Fleet Dashboard\n\nOpen-source agent orchestration dashboard (Next.js 16, builderz-labs fork with Weblyfe skin). **Canonical deployment runs on `appie-mc-1` (Hetzner), NOT the Mac Mini.** Systemd service `mission-control`, port 3000, tailnet-only via `tailscale serve`.\n\nThe Mac Mini runs the **heartbeat** (`mc-heartbeat-manifest.py`, `~\u002Fclawd\u002Ftools\u002F`) that pushes agent status to MC-1. Local MC clones on the mini are planning\u002Fstaging copies only — never run production tasks against them.\n\n## Access\n\n- **Canonical URL:** `https:\u002F\u002Fappie-mc-1.tail61f54b.ts.net` (tailnet-only)\n- **Tailnet IP:** `100.107.179.3` (reachable via appie-2 hop if MagicDNS is off on mini)\n- **Access pattern:** `ssh appie-2 \"curl -s http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\"`\n- Default creds: see `references\u002Fcredentials.md`\n\n## Deploy model (NEVER edit `\u002Fopt\u002Fmission-control` directly on mc-1)\n\nMC-1 uses a gated wave-deploy with auto-rollback. The full process, branch naming conventions, and verification checklist are in `references\u002Fmc-deploy-handoff.md`. Key rules:\n- Hardlink copy (`cp -al`) to `\u002Fopt\u002Fmc-build`, overlay changed source files, build with pnpm, atomic swap → `systemctl restart`\n- Backup DB before every deploy\n- Verify: health 200, correct BUILD_ID, agents ≥21, `\u002Fapi\u002Fknowledge\u002Fgraph source=cognify-kb`\n- Preserve `.env.local` across deploys (contains FLEET_MEMORY_URL, LOCAL_LLM_API_KEY, MC_DISPATCH_MODEL, etc.)\n\n## Heartbeat (Mac Mini → MC-1)\n\nThe fleet heartbeat daemon lives on the Mac Mini at `~\u002Fclawd\u002Ftools\u002Fmc-heartbeat-manifest.py` (301 lines, Python 3). It POSTs agent status (crons, skills, integrations) to MC-1's `\u002Fapi\u002Fagents\u002F\u003Cagent>\u002Fheartbeat` endpoint every 60s.\n\n**Mac Mini agents run via launchd (60s interval):**\n- `com.weblyfe.mc-heartbeat-appie1` — Appie-1\n- `com.weblyfe.mc-heartbeat-opus` — Appie-Opus\n- `com.weblyfe.mc-heartbeat-appie4` — Appie-4 (CFO, separate Hermes instance)\n\n**Remote agents run via systemd timer (60s):**\n- Appie-2 (Hetzner): `\u002Fetc\u002Fsystemd\u002Fsystem\u002Fmc-heartbeat-appie2.{service,timer}` — runs `\u002Fopt\u002Fmc-heartbeat-manifest.py --agent Appie-2`\n- Appie-3 (Hetzner): same pattern via appie-2 hop — `\u002Fopt\u002Fmc-heartbeat-manifest.py --agent Appie-3`\n\n**Critical script detail — `MC_TAILSCALE_IP`:** The script's IP fallback must point to MC-1's Tailscale IP (`100.107.179.3`). If the Mac Mini has MagicDNS off, the script falls back to a direct HTTPS connection to this IP. A wrong IP here (e.g., the mini's own `100.101.29.56`) causes SSL errors on every heartbeat.\n\n**Sync to remote agents after script changes:**\n```bash\nscp ~\u002Fclawd\u002Ftools\u002Fmc-heartbeat-manifest.py appie-2:\u002Fopt\u002Fmc-heartbeat-manifest.py\nssh appie-2 \"scp \u002Fopt\u002Fmc-heartbeat-manifest.py root@100.69.131.51:\u002Fopt\u002Fmc-heartbeat-manifest.py\"\n```\n\n**Diagnose heartbeats:**\n```bash\n# Mac Mini: check launchd logs\ncat ~\u002FLibrary\u002FLogs\u002Fmc-heartbeat-appie1.log\ncat ~\u002FLibrary\u002FLogs\u002Fmc-heartbeat-appie1.err.log\n\n# Remote: check systemd logs\nssh appie-2 \"journalctl -u mc-heartbeat-appie2 --no-pager -n 5\"\nssh appie-2 \"ssh -n root@100.69.131.51 'journalctl -u mc-heartbeat-appie3 --no-pager -n 5'\"\n\n# Dry-run test (no POST, just collect and print)\npython3 ~\u002Fclawd\u002Ftools\u002Fmc-heartbeat-manifest.py --agent Appie-1 --dry-run\n```\n\n## Accessing MC-1 from the Mac Mini\n\nThe Mac Mini has **MagicDNS off** — `appie-mc-1.tail61f54b.ts.net` won't resolve. Use the Tailnet IP directly, or hop through appie-2:\n\n```bash\n# Direct (from mini, if Tailnet IP is reachable)\ncurl http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\n\n# Via appie-2 hop\nssh appie-2 \"curl -s --max-time 5 http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\"\n\n## Pitfalls\n\n### 0. MC-1 unreachable from Mac Mini\n\n**Root cause:** Mac Mini has MagicDNS off. `appie-mc-1.tail61f54b.ts.net` won't resolve.\n\n**Fix:** Use Tailnet IP directly (`100.107.179.3`) or hop through appie-2 (`ssh appie-2 \"curl http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\"`).\n\n### 1. All agents show \"idle\" \u002F stale status\n\n### 1. All agents show \"idle\" \u002F stale status\n\n**Root cause:** Heartbeat not running on the Mac Mini. `mc-heartbeat-manifest.py` is NOT in launchd.\n\n**Fix:** Start it manually or add to launchd (see Heartbeat section above). Without heartbeats, MC-1 stores the last known status but never updates.\n\n### 2. MC-1 server appears DOWN\n\n**Root cause:** The `mission-control` systemd service on appie-mc-1 may have stopped. The box itself is usually alive on Tailscale.\n\n**Diagnose:**\n```bash\nssh appie-2 \"ssh -n root@100.107.179.3 'systemctl is-active mission-control'\"\nssh appie-2 \"curl -s --max-time 5 http:\u002F\u002F100.107.179.3:3000\u002Fapi\u002Fhealth\"\n```\n\n**Fix:**\n```bash\nssh appie-2 \"ssh -n root@100.107.179.3 'systemctl restart mission-control'\"\n# Wait 5s, then verify health check\nssh appie-2 \"curl -s --max-time 10 http:\u002F\u002F100.107.179.3:3000\u002Flogin\"\n```\n\n### 3. Dispatch not working (tasks stuck)\n\n**Root cause:** `MC_DISPATCH_MODEL` pointing at wrong provider, or dispatch routing stripped prefix → routes to Anthropic with no key.\n\n**Fix (on mc-1):** Set in `.env.local`:\n```\nMC_DISPATCH_MODEL=litellm\u002Fdeepseek\u002Fdeepseek-v4-flash\nLOCAL_LLM_ENDPOINT=https:\u002F\u002Fopenrouter.ai\u002Fapi\u002Fv1\n```\nThe `litellm\u002F` prefix preserves provider routing. Never use `provider: auto`.\n\n### 5. Routing 404s on New Projects\nWhen creating a new Vercel project from terminal, it may default to a generic name or have `autoExposeSystemEnvs` \u002F `ssoProtection` enabled which causes a 404 \u002F 302 wall for unauthenticated agents.\n**Fix:** Force link to existing project name: `vercel link --project \u003Cname> --yes`. Ensure SSO is disabled via `PATCH \u002Fv9\u002Fprojects\u002F{id}` body `{\"ssoProtection\": null, \"autoExposeSystemEnvs\": false}`.\n\n### 6. Domain ownership (403 Forbidden)\nIf `GET \u002Fv5\u002Fdomains\u002F{domain}` returns 403, the domain belongs to a different Vercel account\u002Fuser, not just a different team on the current token.\n**Verification:** Check all stored tokens: `grep -r \"VERCEL_TOKEN\" ~\u002F.hermes\u002F.env`. If all fail, the user must manually remove the domain from the old account.\n\n## References\n\n- `references\u002Fmc-feature-roadmap.md` — open features and defects from the July 4 handoff audit\n\n### 5. Routing 404s on New Projects\nWhen creating a new Vercel project from terminal, it may default to a generic name or have `autoExposeSystemEnvs` \u002F `ssoProtection` enabled which causes a 404 \u002F 302 wall for unauthenticated agents.\n**Fix:** Force link to existing project name: `vercel link --project \u003Cname> --yes`. Ensure SSO is disabled via `PATCH \u002Fv9\u002Fprojects\u002F{id}` body `{\"ssoProtection\": null, \"autoExposeSystemEnvs\": false}`.\n\n### 6. Domain ownership (403 Forbidden)\nIf `GET \u002Fv5\u002Fdomains\u002F{domain}` returns 403, the domain belongs to a different Vercel account\u002Fuser, not just a different team on the current token.\n**Verification:** Check all stored tokens: `grep -r \"VERCEL_TOKEN\" ~\u002F.hermes\u002F.env`. If all fail, the user must manually remove the domain from the old account.\n\n## References\n\n- `references\u002Faccess-patterns.md` — full MC_ALLOWED_HOSTS proxy logic and access control\n- `references\u002Flog-patterns.md` — common Hermes log warnings and their meanings\n- `references\u002Ffleet-topology.md` — current Appie fleet layout (local vs remote agents)\n- `references\u002Fsession-context-kanban.md` — mirroring session context into MC kanban\n- `references\u002Ffleet-context-ingestion.md` — fleet-wide context ingestion workflow\n- `references\u002Fmc-deploy-handoff.md` — MC-1 wave deploy process, branches, access topology, and verification checklist\n- `references\u002Fmc-feature-roadmap.md` — open features and defects from the July 4 handoff audit\n",{"name":5,"tags":53,"description":7},[35,47,5,41,44],"master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Ffleet\u002Fmission-control",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add S3YED\u002Fappie-kit --skill mission-control",{"tool":68,"command":69},"bunx","bunx skills add S3YED\u002Fappie-kit --skill mission-control",{"tool":71,"command":72},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill mission-control","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Ffleet\u002Fmission-control\u002FSKILL.md",true,[76,82,86,90,94],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Faccess-patterns.md","REFERENCE","参考文档",2188,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Ffleet\u002Fmission-control\u002Freferences\u002Faccess-patterns.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Ffleet-context-ingestion.md",2677,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Ffleet\u002Fmission-control\u002Freferences\u002Ffleet-context-ingestion.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Ffleet-topology.md",1091,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Ffleet\u002Fmission-control\u002Freferences\u002Ffleet-topology.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Flog-patterns.md",2930,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Ffleet\u002Fmission-control\u002Freferences\u002Flog-patterns.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fsession-context-kanban.md",1249,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Ffleet\u002Fmission-control\u002Freferences\u002Fsession-context-kanban.md",[99,131,164,190,217,242],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":112,"publishedAt":48},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[105,106,109],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":107,"categoryName":108,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":110,"categoryName":111,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":143,"publishedAt":48},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":141,"categoryName":142,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师",[144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":172,"publishedAt":48},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[170,171],{"categoryNo":110,"categoryName":111,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":141,"categoryName":142,"taxonomyType":28,"taxonomyTypeDesc":29},[145,173,149,174,175,176,151,177,178,179,180,181,182,183,184,185,186,187,188,189],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":198,"publishedAt":48},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[196,197],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":110,"categoryName":111,"taxonomyType":20,"taxonomyTypeDesc":21},[44,199,200,201,202,203,204,45,205,206,207,208,209,210,211,212,213,214,215,216],"vercel deployment","vercel","macos","cli","linux","windows","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":224,"publishedAt":48},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[223],{"categoryNo":110,"categoryName":111,"taxonomyType":20,"taxonomyTypeDesc":21},[225,226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241],"workflows","quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification","for",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":255,"publishedAt":48},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[248,251,254],{"categoryNo":249,"categoryName":250,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":252,"categoryName":253,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":110,"categoryName":111,"taxonomyType":20,"taxonomyTypeDesc":21},[256,257,258,259,260,261,262,263,201,264,265,151,266,204,267,234,268,269,270,271],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]