3K skills · sorted by relevance
Connect Kortix to Microsoft Teams and handle conversations with progress updates, final replies, and interactive questions. The skill also covers reading channel discussions, exchanging files, and posting to conversations the bot has already joined.
Make every team AI native — TeamAI syncs a team's AI skills, rules, docs and env across AI coding tools. Use when the task operates on team-shared AI configuration or team knowledge: setting up a team repo, joining one, managing members, syncing with pull or push, or checking team status. Also use to build or query a codebase knowledge base for a large multi-repo project (architecture analysis, architecture reverse-engineering, code-to-knowledge, team-wiki-codebase, architecture wiki), and to share what a session taught you back to the team (share session learnings, contribute a learning, share what I learned with my team), including after a friction reminder. Triggers include "set up teamai", "join the team repo", "sync team skills", "team wiki", "share what I learned", and running /teamai. Talking about a team needs no skill; operating on what the team shares does.
The English summary is being prepared. Showing the original description.
Coordinates a named team of Codex workers with concrete responsibilities and shared progress records. It selects available collaboration tools, manages communication and separate working copies when needed, and handles integration, team archival, and cleanup after the work ends.
Connect NanoClaw agents to Microsoft Teams channels, group chats, and direct messages. The skill installs and tests the adapter, then guides bot creation, credentials, app installation, and connecting the assistant to a selected Teams user.
Set communication rules for teams of AI agents. The skill explains when to use direct messages or broadcasts, how leads review plans, how teammates shut down safely, and how to troubleshoot stalled handoffs or missing communication tools.
Coordinate updates to an operator-configured Team server through its designated Night Watch owner. Use the existing deployment controller’s validation, recovery, and acceptance records to follow the requested update through completion.
Automate Connecteam operations through Rube MCP, a connection for agent tools. The skill discovers available actions and their required inputs, checks the service connection, and executes tools using the current specifications.
Plan Claude Code agent teams by choosing team size, roles, and agent types with the tools each task needs. Preset compositions cover reviews, debugging, implementation, research, security audits, and migrations, alongside display settings for local or CI environments.
Coordinate a worker agent in a tmux-based OMX Team through startup acknowledgements, task claims, status transitions, and mailbox checks. Keep task ownership, completion evidence, and idle status visible to the team.
Automate Connecteam operations through Rube MCP, a connection for agent tools. The skill discovers available actions and their required inputs, checks the service connection, and executes tools using the current specifications.
Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team.
The English summary is being prepared. Showing the original description.
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or "reorg". Also trigger when reorganizing engineering teams, aligning team and service boundaries, splitting a monolith and deciding ownership, reducing cross-team handoffs, or designing an internal platform. Covers the four team types, three interaction modes, the inverse Conway maneuver, and fracture planes. For bounded contexts, see domain-driven-design. For dependency direction in code, see clean-architecture.
The English summary is being prepared. Showing the original description.
Plan, scope, and execute an authorized red-team engagement — distinct from a penetration test. Covers engagement methodology, assumed-breach scenarios, ATT&CK emulation plans, rules of engagement, deconfliction with the blue team, post-engagement debriefs, and the program-level work that makes red teams actually improve defenses. Use when the user mentions 'red team,' 'red team engagement,' 'red teaming,' 'adversary emulation,' 'ATT&CK emulation,' 'assumed breach,' 'purple team exercise,' 'tabletop with technical execution,' 'red team scope,' 'rules of engagement,' 'red team RoE,' 'deconfliction,' 'red team debrief,' or wants to design or run a red-team engagement against systems with authorization.
The English summary is being prepared. Showing the original description.
Save user-provided or approved decisions, constraints, and facts for an AI team, then retrieve them with their sources. Keep memories separate by team and tenant, and report whether retrieval used a degraded search mode.
Implement and customize managed CopilotKit Channels so agents can reply in Slack or Microsoft Teams. It covers channel handlers, persistent runtime connections, Teams setup, and checks for silent failures such as missing permissions or incompatible package versions.
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.
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-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.
承認済みの 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.
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.
This skill should be used when the user asks to "create a team", "spawn agents", "assign tasks", "coordinate multiple agents", "check team status", "view kanban board", "send messages between agents", "manage team tasks", "monitor team progress", or mentions "clawteam", legacy "oh", "multi-agent coordination", "team collaboration", "agent inbox", "task board", "spawn worker". This skill should also be triggered when the current task is complex enough to benefit from splitting into subtasks and delegating to multiple agents — for example when the user asks to "build a full-stack app", "refactor the entire codebase", "implement multiple features in parallel", or when the agent determines that the work scope exceeds what a single agent can efficiently handle alone. Provides comprehensive guidance for using the ClawTeam CLI to orchestrate multi-agent teams with task management, messaging, monitoring, runtime profiles, git context, and recovery tooling.
The English summary is being prepared. Showing the original description.
Summarize Microsoft Teams meetings and extract action items. Use the Hermes command line to inspect meeting processing, rerun saved jobs, troubleshoot missing summaries, and manage Microsoft Graph subscriptions that deliver meeting notifications.
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.