搜索「Multi Agent」的结果

io.github.mattpocock/skills/research

针对高可信的一手来源调研问题，并把结论以 Markdown 文件形式记录到仓库中。当用户想调研某个主题、收集文档或 API 事实，或把资料阅读的跑腿工作交给后台代理时使用。

io.github.mattpocock/skills/wayfinder

把超出单次代理会话容量的大块工作，规划成 issue 跟踪器上共享的决策工单地图，逐条解决，直到通往目标的路径清晰。

io.github.microsoft/vscode/integrated-browser

在开发 VS Code 内置浏览器（browserView）时使用，帮助理解其架构与心智模型。覆盖编辑器标签页中内嵌的 Chromium 浏览器、导航、遮罩/布局、会话，以及 src/vs/platform/browserView 和 src/vs/workbench/contrib/browserView 下的代理浏览器工具。

io.github.garrytan/gstack/setup-gbrain

为当前编码 agent 配置 gbrain：安装 CLI、初始化本地 PGLite 或 Supabase brain、注册 MCP、逐远端记录信任策略。（gstack）

io.github.affaan-m/ECC/flox-environments

使用 Flox（声明式的 Nix 环境管理器）创建可复现的跨平台（macOS/Linux）开发环境。适用于为任意语言设置项目工具链、安装系统级依赖（编译器、数据库、openssl/BLAS 等本地库）、为团队锁定精确的包版本、运行本地服务（PostgreSQL、Redis、Kafka）、一条命令完成开发者入职，或解决“在我机器上没问题”类问题——包括需要项目级工具且无需 sudo 的智能体/vibe-coding 场景。用户提及 .flox/、manifest.toml、flox activate 或 FloxHub 时同样适用。

io.github.morluto/rea/rea-analysis-optimization

Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.

io.github.XiaomiMiMo/MiMo-Code/codex

Operate OpenAI Codex CLI in non-interactive headless environments. Load only when the user explicitly authorizes this skill or names Codex / codex. Before any command, confirm the `codex` binary is available; if missing, stop and give install or auth guidance. Covers `codex exec` automation in Bash or PowerShell, native Windows or WSL2, scripts, CI/CD, Docker, Kubernetes, remote servers, agent harnesses, sandbox and approval modes, JSONL events, session resume, and stdin prompts.

io.github.cheaper-inference/OmniRoute/cli-skill-collector

Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and install them to the detected tools via OmniRoute's built-in APIs.

io.github.volcengine/OpenViking/openviking-memory

Work with OpenViking, the persistent context database behind this agent's memory. Use it whenever the user refers to earlier sessions or shared history ("like last time", "what did we decide"), asks to remember or forget something, shares files, URLs, or repos worth keeping, or when the task needs context this session does not have — even if nobody says the word "memory". Also use it when the user asks where memories are stored: per project, per folder, or shared between repositories. Covers choosing between context search, find, list search, and grep, reading viking:// URIs, and when (not) to write.

io.github.davila7/claude-code-templates/evaluation-nemo-evaluator

在 18 套以上评测框架的 100 多个基准（MMLU、HumanEval、GSM8K、安全、VLM）上评估大模型，支持多后端执行。适用于需要在本机 Docker、Slurm HPC 或云平台上做可扩展评测的场景，是 NVIDIA 的企业级平台，采用容器优先架构以保证基准可复现。

io.github.Jeffallan/claude-skills/kubernetes-specialist

在部署或管理 Kubernetes 工作负载时使用。用于创建 deployment manifest、配置 pod security policy、设置 service account、定义网络隔离规则、调试 pod 崩溃、分析资源限额、检查容器日志或为工作负载定容。也用于 Helm chart、RBAC 策略、NetworkPolicy、存储配置、性能优化、GitOps 流水线与多集群管理。

io.github.affaan-m/ECC/living-docs-governance

Keep a long-lived project's documentation from rotting by assigning existing project docs clear constitution, map, status, and history roles, then wiring the active agent harness to those canonical sources. Use in the maintain phase when docs drift from code, agents lose context between sessions, or intentional removals keep being recreated. Prefer adopting the repository's current docs structure over creating new root files. 中文触发：文档治理、活文档、项目状态追踪、防文档漂移、项目地图、健康仪表盘、删除区、长期项目治理

io.github.affaan-m/ECC/dynamic-workflow-mode

为 Claude 动态工作流模式及其他自适应智能体框架设计任务局部评测脚手架（harness）、评估门禁与可复用技能抽取。适用于构建任务局部 harness、添加评估门禁，或从临时性工作中抽取可复用技能。

io.github.bytedance/deer-flow/data-analysis

当用户上传 Excel（.xlsx/.xls）或 CSV 文件并希望做数据分析、生成统计、创建摘要、透视表、SQL 查询或任何结构化数据探索时使用。支持多 Sheet Excel 工作簿、聚合、过滤、连接，并将结果导出为 CSV/JSON/Markdown。

io.github.davila7/claude-code-templates/docker-expert

Docker 容器化专家，精通多阶段构建、镜像优化、容器安全、Docker Compose 编排与生产部署模式。对 Dockerfile 优化、容器问题、镜像体积、安全加固、网络与编排难题主动使用。

io.github.asgeirtj/system_prompts_leaks/control-browser

Use when opening, navigating, inspecting, testing, clicking, typing, filling, screenshotting, or verifying web pages and local HTTP targets (localhost, 127.0.0.1, ::1) inside ZCode, including browser/web-UI automation, rendered-page scraping, frontend checks, and visible page-state reading. Prefer this over Computer Use for anything that stays inside a web page, unless the user explicitly asks for Computer Use. Main agent only.

io.github.Significant-Gravitas/AutoGPT/pr-test

使用 docker compose、agent-browser 与 API 调用对 PR/分支进行 E2E 手动测试。当用户要求手动测试 PR、端到端测试某功能，或对运行中的系统执行集成测试时触发。

io.github.alirezarezvani/claude-skills/slo-architect

用于定义、评审或运维 SLO/SLI/错误预算。触发词包括「define an SLO」「what should our SLO be」「error budget」「burn rate」「SLI」「service level objective」「Google SRE workbook」「multi-window burn-rate alert」，或任何可靠性目标问题。附带 SLO 设计器、带多窗口燃烧率阈值的错误预算计算器，以及捕捉常见缺陷（目标过于激进、窗口过短、SLO 冲突、缺少 SLI 定义）的 SLO 评审器。4 份关于 SLO 原则+SLI 设计+错误预算数学+与 feature-flags-architect/chaos-engineering/kubernetes-operator 组合的参考文档。不是通用的可观测性技能——专注 SLO 这一学科。

io.github.alirezarezvani/claude-skills/engineering-advanced-skills

为 Claude Code、Codex、Gemini CLI、Cursor、OpenClaw 提供 37 个高级工程 agent 技能的索引。用于浏览或选择 POWERFUL 层级的工程技能：agent 设计、RAG、MCP 服务器、CI/CD、数据库设计、可观测性、安全审计、changelog/release 自动化、可靠性（SLO/chaos/flags/operators）、平台运维。

io.github.affaan-m/ECC/safety-guard

Guard against destructive operations with three modes: Careful intercepts dangerous commands (rm -rf, git push --force, DROP TABLE) for confirmation, Freeze locks writes to one directory, and Guard combines both. Advisory: the agent applies these rules itself; no hook ships with it. Use when working on production systems, running agents autonomously, restricting edits to a directory, or during migrations, deploys, and data changes.

io.github.tracer-cloud/opensre/tools

通过 REST API 读取 Yandex Cloud。适用于任何关于 VM、指标、日志、审计事件、Kubernetes、托管数据库、serverless、网络或其他 Yandex Cloud 资源的问题。绝不通过 shell 调用 `yc` CLI——那不是本 agent 访问 Yandex Cloud 的方式，且它通常没有安装。

io.github.google/skills/gke-ai-troubleshooting-tpu-performance-degradation

Diagnose GKE Cloud TPU training throughput drops and step-time regressions (15%+ TPU duty-cycle drop) using ML Diagnostics Workload Monitoring (`gcloud alpha mldiagnostics monitored-events` / `hypercomputecluster.googleapis.com/v1alpha`) and 1-minute Cloud Monitoring system metrics (`kubernetes.io/node/accelerator/*`). Distinguishes hardware and network fabric throttling from workload resource bottlenecks (HBM capacity, host memory, or host CPU saturation). Use when TPU training throughput or duty cycle drops without crashing pods, when `PERFORMANCE_DEGRADATION` monitored events fire, or when triaging slow multi-slice training steps. Don't use for complete multi-slice XLA execution stalls with `HANG_DETECTED` logs (use gke-ai-troubleshooting-tpu-mxla-hang) or pod eviction/interruption restarts (use gke-ai-troubleshooting-jobset-interruption).

io.github.google/skills/gke-ai-troubleshooting-tpu-mxla-hang

Diagnose GKE Cloud TPU multi-slice training hangs (Megascale `HANG_DETECTED` logs and hang monitored events) using the ML Diagnostics `Megascale XLA (MXLA) Hang Analyzer` (`gcloud alpha mldiagnostics monitored-events`) and 1-minute Cloud Monitoring multi-slice latency metrics (`kubernetes.io/container/multislice/*`). Distinguishes XLA compiler/HLO launch divergence and host data-input stalls from TPU chip, SparseCore, ICI, or network fabric faults. Use when multi-slice TPU training jobs freeze without progressing steps, emit `HANG_DETECTED`, or stall in collective operations. Don't use for gradual step-time throughput drops without hangs (use gke-ai-troubleshooting-tpu-performance-degradation) or pod preemption/eviction restarts (use gke-ai-troubleshooting-jobset-interruption).

io.github.github/awesome-copilot/conventional-branch

Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/, plus AI agent prefixes ai/, copilot/, cursor/, claude/, codex/). Use when creating a new branch, naming a branch, or checking whether a branch name complies with the spec.