3.1K skills · sorted by relevance
Find the migration path for the removed OMX parallel execution command. This retirement notice directs users to replace `$ultrawork` with `$team`, which manages worker panes, shared task state, messaging, dispatch, and coordinated worker lifecycles.
Prepare an existing OpenClaw setup for import as an AgentTeams managed Worker. Analyze tool dependencies, adapt role instructions and scheduled jobs, and build a ZIP package containing the configuration and custom image requirements.
Agent Teams スキルを設計・構築するためのベストプラクティスガイド。 サブエージェント定義、SendMessage 通信プロトコル、タスク依存管理、 PostToolUse Hook によるログ、MCP ツール統合、コンテキストファイル設計を網羅。 7つの実績あるチームスキル（app-naming, ui-review, logo-design, persona-creation, skill-creator-team, ui-variations, aso-optimize）から抽出したパターン集。 Use when: Agent Teams を使ったスキルを新規作成したい、 既存のチームスキルの品質を改善したい、エージェント間通信のデバッグ、 チームスキルの設計パターンを知りたい。 Triggers: "agent team", "チームスキル", "エージェントチーム", "サブエージェント定義", "SendMessage パターン", "チーム設計", "エージェント間通信", "team skill", "swarm pattern"
The English summary is being prepared. Showing the original description.
承認済みの team-plan 計画（task-list.json）を Agent Teams + Subagent ハイブリッドで並行実行。 Git Worktree でファイル分離。Delegate mode / Plan Approval / hooks にフル準拠。 Trigger: dev:team-run, /dev:team-run, チーム実行, team run
The English summary is being prepared. Showing the original description.
承認済みのteam-opencode計画（task-list.json）をAgent Teamsで並行実行。 Wave式チーム実行→レビューフィードバック→クリーンアップ。 Trigger: dev:team-opencode-exec, /dev:team-opencode-exec, チーム実行, team exec
The English summary is being prepared. Showing the original description.
Plan an AI team around a goal, defining roles, deliverables, and a recorded unit budget. After approval, it creates team, run, and task records in RuFlo AI Team; it does not execute the work.
Set up repeatable security tests for LLM apps with Promptfoo and DeepTeam. Connect them to automated build pipelines, detect renewed vulnerabilities to malicious instructions or data leakage, and compare results across model or prompt changes.
Implement shared authentication for Azure Communication Services in Java, including automatic renewal of access tokens, the credentials used to access services. It also guides handling identifiers for ACS users, phone numbers, and Microsoft Teams users.
Set up an agent that replies in Slack or Microsoft Teams using CopilotKit's guided CLI workflow. It covers project preparation, agent creation, channel configuration, a persistent host process, and verification with a real message.
Check active PUA agents and teams from Codex CLI using an alias for the Claude Code status command. Review process IDs and record lifetimes when available, alongside stale records.
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"
The English summary is being prepared. Showing the original description.
承認済みの実装計画（Plan）を Agent Team で並列に実装するスキル。 Plan をタスクに分割 → 依存関係を設定 → Wave ごとに並列エージェントを起動 → 完了を待って次の Wave → 最後にビルド＆テスト検証。 team-plan スキル（調査→計画）の後に使う「実装実行フェーズ」。 Use when: 計画を並列に実装したい、チームで実装を進めたい、 Wave 実行で効率よくコードを書きたい。 Triggers: "team implement", "チームで実装", "並列実装", "plan を実装して", "wave 実行", "team-implement", "エージェントで実装", "実装フェーズ", "implement the plan"
The English summary is being prepared. Showing the original description.
Claude Code の並列エージェント(agent teams・teammate)の後始末と無応答時の打ち切りルール。`name` を付けて Agent を起動するとき、TeamCreate でチームを組むとき、teammate から `idle_notification` が届いたとき、評価ループ等で次のイテレーションのエージェントを起動する前、エージェントの返信が届かないときに参照する。`name` を付けない通常のサブエージェント起動だけなら対象外。
The English summary is being prepared. Showing the original description.
Inspect, debug, and inject custom code into a running Steam client — desktop (macOS, Linux, Windows) or Steam Deck over the network — through its Chromium Embedded Framework (CEF) Chrome DevTools Protocol endpoint. Use when developing Steam UI plugins, mods, themes, or integrations — injecting CSS/JS to try a change, locating webpack modules and obfuscated class names, reading React or SteamUIStore state, inspecting Big Picture / Quick Access Menu windows, screenshotting what actually rendered, streaming console logs, or diagnosing runtime errors in Steam's UI. The same commands run against either device, or both at once. Injection is per-session and for development only. Not for building a plugin loader or making changes persist across restarts, Steamworks game SDK work, game development, or scraping the public Steam web store.
The English summary is being prepared. Showing the original description.
Agent Team（tmux + TeamCreate）で並列実装する開発フロー。「エージェントチームフロー」「workflow-agent-team」「Agent Team で実装」「チームで実装」「チーム並列開発」などで起動。Issue/PR まで作るかは発話・引数から判断し、曖昧なら確認する。
The English summary is being prepared. Showing the original description.
チーム実装計画を作成。ストーリー分析→タスク分解→レビュー（opencode）。 計画は docs/FEATURES/team/{YYMMDD}_{slug}/ に永続化され、複数保持可能。 Trigger: dev:team-plan, /dev:team-plan, チーム計画, team plan
The English summary is being prepared. Showing the original description.
Pause, resume, or complete an AI team while preserving its work evidence. Check the current state before changes, identify unfinished tasks that prevent run completion, and offer an evidence bundle before closing the work.
Use Stratus Red Team to simulate attack techniques across AWS, Azure, GCP, and Kubernetes. Prepare test resources, run and repeat simulations, check logs and alerts, and remove resources to assess whether security detections work.
Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.
Build Zoom Team Chat integrations for user messages or interactive bots. Guides API selection, authentication, message cards with buttons and forms, and webhooks that receive commands and user actions.
Review a sales team's pipeline by representative and deal stage. The skill summarizes progress against targets, highlights deals that could affect the quarter, and suggests concrete manager actions and coaching questions using CRM data or an uploaded export.
Plan and configure a shared GKE cluster for multiple teams or environments. Set up namespaces, team permissions, resource limits, and network separation, then use labels and GKE cost allocation to track spending by team.
Set up OpenRig to run a team of coding agents, including Claude Code and Codex. Open the team interface, pass project goals to its operator, reconnect to agents, and follow assigned work through to its results.
Manage human accounts in AgentTeams by adding users, assigning one of three permission levels, and choosing which agents they can contact. It also covers listing accounts, updating permissions, and removing access.