3.4K skills · sorted by relevance
Plan game stories, world lore, dialogue, visual direction, and story placement within levels through a staged workflow. Produce narrative documents with consistency checks and localization considerations, using the roles enabled by the team settings.
Coordinate game area design from story, world context, and visual direction through layout, enemies, rewards, accessibility, and test planning. Compile the results into a level design document, with specialist participation determined by the configured team size.
Refine a game feature or area through performance measurement, visual and audio polish, and stress and regression testing. Report before-and-after metrics, remaining issues, and release readiness, with work limited to the enabled team roles.
Coordinate role-based agents to design, implement, integrate, and test a game combat feature. The workflow covers gameplay rules, enemy behavior, visual effects, and audio planning, with a final report on completion, test results, and unresolved issues.
Coordinate development work by breaking tasks down, writing six-part Task Prompts, and managing P8 agent teams. This skill takes a technical lead role, directing parallel agents and their delivery without writing code itself.
Use cmux on macOS to organize visible teams of AI agents, send prompts, inspect terminal output, and monitor completion. Set up role-based teams or have several agents investigate the same problem; live operation remains unproven in the supplied material.
Set up an OpenRig team for ongoing repository work, with clear ownership, implementation, independent review, and handoffs. Choose direct coordination, a task queue, or an explicit workflow, then expand the team as authorized work requires.
Interpret Culture Index behavioral profiles to understand individual traits, team balance, and possible strain from workplace adaptation. Use PDF or JSON data to inform hiring discussions, management approaches, onboarding plans, and conflict mediation.
Identify whether a Matrix chat room is a request source or a task workspace, then create or reuse a project-specific task room. The skill also handles worker invitation details and preserves information about where requests originated.
Guides communication in Matrix agent teams by choosing recipients, rooms, and when to mention someone. It covers task notifications and progress reports, helping agents avoid duplicate assignments and send concrete updates to the appropriate requester.
Set up file-based coordination between agent teams on different machines or across organizations. The skill creates connection settings, installs bundled sync scripts, and can initialize a shared Git repository for exchanging team status.
Install and configure mirrord Operator for team use on Kubernetes. The skill covers licensing, access permissions, feature settings, internal registries, and offline deployments, with guidance for upgrades and troubleshooting across supported cluster platforms.
Sub-skill of microsoft-365-agents-toolkit. Routed expert system with 100+ micro-expert files for migrating Slack bots to Teams, cross-platform bridging, and dual-platform bot development. USE FOR: migrating Slack bot to Teams, adding Teams support to Slack bot, building dual-platform bots, converting Block Kit to Adaptive Cards, identity/OAuth bridging, deploying bots to Azure or AWS, configuring AI model providers. DO NOT USE FOR: general web development, non-bot projects, standalone Teams development without Slack (use parent skill instead).
The English summary is being prepared. Showing the original description.
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
The English summary is being prepared. Showing the original description.
Start a cross-team project with the collaboration contract that prevents the classic collisions — who decides what, how work flows between teams, the communication channels and cadence, and what done means — agreed before the first collision instead of during it. Use when asked kick off this cross-team project right, our two teams keep colliding, define how we'll work with the other team, or set up the partnership before we start. Produces the one-page contract: decision rights, interfaces, cadence, and the done-definition.
The English summary is being prepared. Showing the original description.
Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and their roles or scopes, or attributing consumption per user or model. Keywords: governance, model control, consumption cap, spend limit, API key hygiene, team admin, enterprise.
The English summary is being prepared. Showing the original description.
Use when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation. Triggers on /orchestrate, multi-agent coordination, parallel team work, task delegation to teammates.
The English summary is being prepared. Showing the original description.
Universal team coordination skill with dynamic role generation. Uses team-worker agent architecture with role-spec files. Only coordinator is built-in -- all worker roles are generated at runtime as role-specs and spawned via team-worker agent. Beat/cadence model for orchestration. Triggers on "Team Coordinate ".
The English summary is being prepared. Showing the original description.
Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team issue".
The English summary is being prepared. Showing the original description.
Unified team skill for architecture optimization. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team arch-opt".
The English summary is being prepared. Showing the original description.
Collaborative purple-team operations — threat-informed adversary emulation planning (ATT&CK, CTID, Atomic Red Team, CALDERA), the detect-tune-validate loop, detection coverage measurement (DeTT&CT/Navigator), safe execution and deconfliction, and MTTD/coverage reporting
The English summary is being prepared. Showing the original description.
Turn a work-items.md file (produced by /plan-work-items) into Linear issues, one per slice, in a single target Linear team. Use when you want to publish work items as Linear issues, create implementation tickets to track in Linear, or push a broken-down plan into a Linear team. Requires a configured Linear MCP server and a target team. Reads the team's real workflow states, labels, Projects, and members and resolves every option against them before creating anything; defaults each issue to the team's initial state, unassigned, uncategorized, with no parent or Project unless you ask. Links within-file `Depends on` relationships as native Linear "blocked by" relations and annotates the source file so re-runs resume cleanly. Does not produce the work-items file itself — use plan-work-items first. Does not post to Jira — use work-items-to-jira. Does not post to GitHub — use work-items-to-issues.
The English summary is being prepared. Showing the original description.
Start long-lived provider LLM teammates as native Claude Code agent-team members (the native Agent tool with a ccf-<provider> type) that you message with SendMessage — multi-turn, collaborative, watchable in tmux panes. Use for sustained parallel build/work ("start 3 glm teammates", N teammates on N files), or when you need a collaborator you message across turns, from a terminal `claude` session. NOT a fire-and-forget one-shot or a flat batch of independent prompts — that is /cc-fleet:subagent. NOT a scripted multi-phase run — that is /cc-fleet:workflow.
The English summary is being prepared. Showing the original description.
Agent Teams 智能编排决策引擎。自动分析任务复杂度，判断使用 Subagent 还是 Agent Teams。 触发场景： (1) 任务涉及多角度并行分析（如代码审查、竞争假说调试） (2) 需要成员之间互相通信、质疑、协作 (3) 跨层开发（前端/后端/测试各自负责） (4) 用户明确要求"创建团队"、"用 agent teams" (5) 任务描述包含"并行"、"同时"、"多人"、"协作"等关键词 (6) 使用 /team 命令
The English summary is being prepared. Showing the original description.