[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EG1A4SJK5RSAVXJSTZKZ95":3,"skill-same:01M7EG1A4SJK5RSAVXJSTZKZ95":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EG1A4SJK5RSAVXJSTZKZ95","cmux-workspace",null,"Work inside the current cmux workspace and terminal. Use for cmux workspace, current workspace, caller surface, panes, surfaces, socket targeting, and non-interfering cmux automation.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcmux-workspace\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cmux-workspace\ndescription: \"Work inside the current cmux workspace and terminal. Use for cmux workspace, current workspace, caller surface, panes, surfaces, socket targeting, and non-interfering cmux automation.\"\n---\n\n# cmux Workspace\n\nScope work to the cmux workspace that invoked the agent.\n\n- **Window**: a macOS cmux window.\n- **Workspace**: a sidebar entry. The UI calls it a tab; CLI\u002Fsocket APIs call it a workspace.\n- **Pane**: a split region inside a workspace.\n- **Surface**: a tab inside a pane, terminal or browser.\n- **Panel**: internal content type inside a surface. Prefer CLI surface commands over panel internals.\n\n## Default rule\n\nScope actions to the current caller workspace unless the user explicitly asks for another workspace, another window, or global state. Do not assume the visually focused workspace is the right target: an agent can run in one workspace while the user looks at another.\n\n```bash\nprintf 'workspace=%s\\nsurface=%s\\nsocket=%s\\n' \\\n  \"${CMUX_WORKSPACE_ID:-}\" \"${CMUX_SURFACE_ID:-}\" \"${CMUX_SOCKET_PATH:-}\"\ncmux identify --json\n```\n\n`CMUX_WORKSPACE_ID` is the default workspace anchor and `CMUX_SURFACE_ID` the default caller terminal anchor. If they are missing, fall back to `cmux identify --json` and say explicitly that you are using the currently focused context.\n\n## Non-disruptive automation\n\nTreat layout and focus as separate concerns. `select-workspace`, `focus-pane`, `focus-panel`, and focus-changing `tab-action` verbs are user-affecting actions, like clicks. Never call them speculatively, even inside the caller's own workspace, since the user may be looking elsewhere.\n\nBuild layout additively in one shot, using commands that create a pane already populated with the right surface:\n\n```bash\ncmux new-pane --workspace \"${CMUX_WORKSPACE_ID}\" --type browser --direction right --url \"http:\u002F\u002F127.0.0.1:8765\"\ncmux new-pane --workspace \"${CMUX_WORKSPACE_ID}\" --type terminal --direction down\ncmux new-pane --workspace \"${CMUX_WORKSPACE_ID}\" --type terminal --direction down --command \"npm run dev\"\n```\n\nWhen the first command for a new terminal is known, pass `--command \u003Ctext>` so it starts at spawn instead of a later `send`. Avoid create-then-move-then-focus chains. Pass `--focus false` wherever the verb supports it (`move-surface --focus false` preserves the user's attention; more commands may grow the flag, see https:\u002F\u002Fgithub.com\u002Fmanaflow-ai\u002Fcmux\u002Fissues\u002F1418 and https:\u002F\u002Fgithub.com\u002Fmanaflow-ai\u002Fcmux\u002Fissues\u002F2820). If a layout command rejects a valid `surface:` or `pane:` ref, report the bug and stop rather than working around it by focusing.\n\n## Right-side helper pane\n\nFor auxiliary output (preview apps, TUIs, logs, one-off shells, browser checks), reuse one helper pane to the right of the caller terminal. Inspect first with `cmux identify --json`, `cmux list-panes`, and `cmux list-pane-surfaces`, then:\n\n- Helper pane exists: add a surface to it.\n  ```bash\n  cmux new-surface --workspace \"${CMUX_WORKSPACE_ID:-}\" --pane pane:\u003Chelper> --type terminal --focus false\n  ```\n- No helper pane: create exactly one.\n  ```bash\n  cmux new-pane --workspace \"${CMUX_WORKSPACE_ID:-}\" --type terminal --direction right --focus false\n  ```\n- Multiple obvious stale helper panes from this same automation, and the user asked to tidy: keep one and clean up duplicates. Never close a pane you cannot confidently identify as stale helper output.\n\nSend commands to the new or reused surface by explicit surface ref, or pass `--command \u003Ctext>` at creation when the first command is already known. Repeated \"open it\" requests create tabs inside the existing right helper pane, not more splits.\n\n## Caller terminal\n\nThe surface that invoked the agent is the safest anchor for relative operations.\n\n```bash\ncmux send \"npm test\\n\"                                    # focused terminal in caller workspace\ncmux send --surface \"${CMUX_SURFACE_ID:-}\" \"git status\\n\"  # exact caller surface\ncmux send-key --surface \"${CMUX_SURFACE_ID:-}\" enter\n```\n\nDo not send keystrokes, close surfaces, or change focus in another workspace unless the user named that target.\n\n## Moving surfaces\n\n```bash\ncmux move-surface --surface \"${CMUX_SURFACE_ID}\" --before surface:3   # also --after, --index\ncmux move-surface --surface surface:240 --pane pane:172 --focus false\ncmux drag-surface-to-split --surface surface:240 down\n```\n\nKnown papercut: `drag-surface-to-split` routes through V1 and resolves the workspace via UI focus, so it fails with `ERROR: Surface not found` when the caller's workspace is not the visually focused one (https:\u002F\u002Fgithub.com\u002Fmanaflow-ai\u002Fcmux\u002Fissues\u002F1901, related https:\u002F\u002Fgithub.com\u002Fmanaflow-ai\u002Fcmux\u002Fissues\u002F3189). Until that lands, build layout additively. Never call `focus-pane` or `focus-panel` to recover from a failed move; report the failure and stop.\n\n## Sidebar state\n\nAttach status, progress, and logs to the current workspace so the sidebar reflects this task.\n\n```bash\ncmux set-status build \"running\" --workspace \"${CMUX_WORKSPACE_ID:-}\" --color \"#ff9500\"\ncmux set-progress 0.4 --label \"Building\" --workspace \"${CMUX_WORKSPACE_ID:-}\"\ncmux log --workspace \"${CMUX_WORKSPACE_ID:-}\" --level info -- \"Started build\"\ncmux sidebar-state --workspace \"${CMUX_WORKSPACE_ID:-}\" --json\n```\n\n## Contributor reloads\n\nFor cmux app\u002Fruntime changes in a cmux source checkout, use a tagged reload from the active worktree. It creates an isolated app name, bundle ID, debug socket, and DerivedData path. Never build or launch untagged `cmux DEV`.\n\n```bash\n.\u002Fscripts\u002Freload.sh --tag \u003Cshort-tag>\nCMUX_SOCKET_PATH=\u002Ftmp\u002Fcmux-debug-\u003Cshort-tag>.sock cmux identify --json\n```\n\n## Socket access\n\nUse the socket path cmux provided before any default: `SOCK=\"${CMUX_SOCKET_PATH:-\u002Ftmp\u002Fcmux.sock}\"`. Socket access can be off, restricted to cmux-spawned processes, or open to all local processes. If a command cannot connect, inspect `cmux capabilities --json` and `cmux ping` before changing settings.\n\n## Rules\n\n- Work in the caller workspace by default; prefer explicit `--workspace` and `--surface` flags for mutating actions even when env vars are set, so automation is auditable.\n- Never call `focus-pane`, `focus-panel`, `select-workspace`, or focus-changing `tab-action` verbs unless the user explicitly asked.\n- Pass `--focus false` on `move-surface` and any creation verb that supports it.\n- Build layout additively with `new-pane --type ... --url ...` or `--command ...`, not create-then-move-then-focus.\n- If a CLI command rejects a valid surface or pane ref, report it. Do not work around by focusing.\n- Do not close, focus, move, or send input to another workspace unless the user names that target.\n- Use short refs in chat and examples; UUIDs only for logs, persistence, or debugging.\n\n## References\n\n- [references\u002Fcommands.md](references\u002Fcommands.md): full workspace, pane, surface, notification, and utility command list.\n- [..\u002Fcmux-browser\u002FSKILL.md](..\u002Fcmux-browser\u002FSKILL.md): browser surfaces under the same current-workspace rule.\n","# cmux Workspace\n\nScope work to the cmux workspace that invoked the agent.\n\n- **Window**: a macOS cmux window.\n- **Workspace**: a sidebar entry. The UI calls it a tab; CLI\u002Fsocket APIs call it a workspace.\n- **Pane**: a split region inside a workspace.\n- **Surface**: a tab inside a pane, terminal or browser.\n- **Panel**: internal content type inside a surface. Prefer CLI surface commands over panel internals.\n\n## Default rule\n\nScope actions to the current caller workspace unless the user explicitly asks for another workspace, another window, or global state. Do not assume the visually focused workspace is the right target: an agent can run in one workspace while the user looks at another.\n\n```bash\nprintf 'workspace=%s\\nsurface=%s\\nsocket=%s\\n' \\\n  \"${CMUX_WORKSPACE_ID:-}\" \"${CMUX_SURFACE_ID:-}\" \"${CMUX_SOCKET_PATH:-}\"\ncmux identify --json\n```\n\n`CMUX_WORKSPACE_ID` is the default workspace anchor and `CMUX_SURFACE_ID` the default caller terminal anchor. If they are missing, fall back to `cmux identify --json` and say explicitly that you are using the currently focused context.\n\n## Non-disruptive automation\n\nTreat layout and focus as separate concerns. `select-workspace`, `focus-pane`, `focus-panel`, and focus-changing `tab-action` verbs are user-affecting actions, like clicks. Never call them speculatively, even inside the caller's own workspace, since the user may be looking elsewhere.\n\nBuild layout additively in one shot, using commands that create a pane already populated with the right surface:\n\n```bash\ncmux new-pane --workspace \"${CMUX_WORKSPACE_ID}\" --type browser --direction right --url \"http:\u002F\u002F127.0.0.1:8765\"\ncmux new-pane --workspace \"${CMUX_WORKSPACE_ID}\" --type terminal --direction down\ncmux new-pane --workspace \"${CMUX_WORKSPACE_ID}\" --type terminal --direction down --command \"npm run dev\"\n```\n\nWhen the first command for a new terminal is known, pass `--command \u003Ctext>` so it starts at spawn instead of a later `send`. Avoid create-then-move-then-focus chains. Pass `--focus false` wherever the verb supports it (`move-surface --focus false` preserves the user's attention; more commands may grow the flag, see https:\u002F\u002Fgithub.com\u002Fmanaflow-ai\u002Fcmux\u002Fissues\u002F1418 and https:\u002F\u002Fgithub.com\u002Fmanaflow-ai\u002Fcmux\u002Fissues\u002F2820). If a layout command rejects a valid `surface:` or `pane:` ref, report the bug and stop rather than working around it by focusing.\n\n## Right-side helper pane\n\nFor auxiliary output (preview apps, TUIs, logs, one-off shells, browser checks), reuse one helper pane to the right of the caller terminal. Inspect first with `cmux identify --json`, `cmux list-panes`, and `cmux list-pane-surfaces`, then:\n\n- Helper pane exists: add a surface to it.\n  ```bash\n  cmux new-surface --workspace \"${CMUX_WORKSPACE_ID:-}\" --pane pane:\u003Chelper> --type terminal --focus false\n  ```\n- No helper pane: create exactly one.\n  ```bash\n  cmux new-pane --workspace \"${CMUX_WORKSPACE_ID:-}\" --type terminal --direction right --focus false\n  ```\n- Multiple obvious stale helper panes from this same automation, and the user asked to tidy: keep one and clean up duplicates. Never close a pane you cannot confidently identify as stale helper output.\n\nSend commands to the new or reused surface by explicit surface ref, or pass `--command \u003Ctext>` at creation when the first command is already known. Repeated \"open it\" requests create tabs inside the existing right helper pane, not more splits.\n\n## Caller terminal\n\nThe surface that invoked the agent is the safest anchor for relative operations.\n\n```bash\ncmux send \"npm test\\n\"                                    # focused terminal in caller workspace\ncmux send --surface \"${CMUX_SURFACE_ID:-}\" \"git status\\n\"  # exact caller surface\ncmux send-key --surface \"${CMUX_SURFACE_ID:-}\" enter\n```\n\nDo not send keystrokes, close surfaces, or change focus in another workspace unless the user named that target.\n\n## Moving surfaces\n\n```bash\ncmux move-surface --surface \"${CMUX_SURFACE_ID}\" --before surface:3   # also --after, --index\ncmux move-surface --surface surface:240 --pane pane:172 --focus false\ncmux drag-surface-to-split --surface surface:240 down\n```\n\nKnown papercut: `drag-surface-to-split` routes through V1 and resolves the workspace via UI focus, so it fails with `ERROR: Surface not found` when the caller's workspace is not the visually focused one (https:\u002F\u002Fgithub.com\u002Fmanaflow-ai\u002Fcmux\u002Fissues\u002F1901, related https:\u002F\u002Fgithub.com\u002Fmanaflow-ai\u002Fcmux\u002Fissues\u002F3189). Until that lands, build layout additively. Never call `focus-pane` or `focus-panel` to recover from a failed move; report the failure and stop.\n\n## Sidebar state\n\nAttach status, progress, and logs to the current workspace so the sidebar reflects this task.\n\n```bash\ncmux set-status build \"running\" --workspace \"${CMUX_WORKSPACE_ID:-}\" --color \"#ff9500\"\ncmux set-progress 0.4 --label \"Building\" --workspace \"${CMUX_WORKSPACE_ID:-}\"\ncmux log --workspace \"${CMUX_WORKSPACE_ID:-}\" --level info -- \"Started build\"\ncmux sidebar-state --workspace \"${CMUX_WORKSPACE_ID:-}\" --json\n```\n\n## Contributor reloads\n\nFor cmux app\u002Fruntime changes in a cmux source checkout, use a tagged reload from the active worktree. It creates an isolated app name, bundle ID, debug socket, and DerivedData path. Never build or launch untagged `cmux DEV`.\n\n```bash\n.\u002Fscripts\u002Freload.sh --tag \u003Cshort-tag>\nCMUX_SOCKET_PATH=\u002Ftmp\u002Fcmux-debug-\u003Cshort-tag>.sock cmux identify --json\n```\n\n## Socket access\n\nUse the socket path cmux provided before any default: `SOCK=\"${CMUX_SOCKET_PATH:-\u002Ftmp\u002Fcmux.sock}\"`. Socket access can be off, restricted to cmux-spawned processes, or open to all local processes. If a command cannot connect, inspect `cmux capabilities --json` and `cmux ping` before changing settings.\n\n## Rules\n\n- Work in the caller workspace by default; prefer explicit `--workspace` and `--surface` flags for mutating actions even when env vars are set, so automation is auditable.\n- Never call `focus-pane`, `focus-panel`, `select-workspace`, or focus-changing `tab-action` verbs unless the user explicitly asked.\n- Pass `--focus false` on `move-surface` and any creation verb that supports it.\n- Build layout additively with `new-pane --type ... --url ...` or `--command ...`, not create-then-move-then-focus.\n- If a CLI command rejects a valid surface or pane ref, report it. Do not work around by focusing.\n- Do not close, focus, move, or send input to another workspace unless the user names that target.\n- Use short refs in chat and examples; UUIDs only for logs, persistence, or debugging.\n\n## References\n\n- [references\u002Fcommands.md](references\u002Fcommands.md): full workspace, pane, surface, notification, and utility command list.\n- [..\u002Fcmux-browser\u002FSKILL.md](..\u002Fcmux-browser\u002FSKILL.md): browser surfaces under the same current-workspace rule.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fcmux-workspace",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill cmux-workspace",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill cmux-workspace",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill cmux-workspace","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcmux-workspace\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",392,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcmux-workspace\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcommands.md",4393,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcmux-workspace\u002Freferences\u002Fcommands.md",[57,64,71,78,86,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7EXRM12046G0GM1WGMMFXCN","ci-cd-and-automation","Automates CI\u002FCD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fci-cd-and-automation\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7EXRFYYSJ3Y15AGPDDEWWQD","chrome-devtools","Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-devtools\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7EXR6EYPE4X5X1BTAE6QJRV","chrome-cdp","Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a\ndebuggable Chrome is running (launching it if needed) so the agent can\nnavigate, read page content, inspect the DOM, run JavaScript, and take\nscreenshots — without the user typing any launch command. Includes a\nfirst-class \"review a live running app\" flow: point Chrome at the app under\ndevelopment and inspect\u002Fscreenshot the REAL page (what a static-artifact tool\ncannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when\nasked to \"use chrome\", \"open chrome\", \"drive my browser\", \"read the page in\nchrome\", \"review the running app\", \"screenshot the app\", or \"\u002Fchrome-cdp\".","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-cdp\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7EXR1Y7E79KQKG4J798XGH6","check-identity-pack","Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcheck-identity-pack\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7EXQXW7C7PGREJW9ZZTZ16H","changelog","Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7EXQMH2ZME3ANN8Q8MEWPFB","cellxgene-census","Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs\u002Fdownloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcellxgene-census\u002FSKILL.md",[],[]]