3천건 · 관련도순
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下降"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
承認済みの実装計画（Plan）を Agent Team で並列に実装するスキル。 Plan をタスクに分割 → 依存関係を設定 → Wave ごとに並列エージェントを起動 → 完了を待って次の Wave → 最後にビルド＆テスト検証。 team-plan スキル（調査→計画）の後に使う「実装実行フェーズ」。 Use when: 計画を並列に実装したい、チームで実装を進めたい、 Wave 実行で効率よくコードを書きたい。 Triggers: "team implement", "チームで実装", "並列実装", "plan を実装して", "wave 実行", "team-implement", "エージェントで実装", "実装フェーズ", "implement the plan"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claude Code の並列エージェント(agent teams・teammate)の後始末と無応答時の打ち切りルール。`name` を付けて Agent を起動するとき、TeamCreate でチームを組むとき、teammate から `idle_notification` が届いたとき、評価ループ等で次のイテレーションのエージェントを起動する前、エージェントの返信が届かないときに参照する。`name` を付けない通常のサブエージェント起動だけなら対象外。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agent Team（tmux + TeamCreate）で並列実装する開発フロー。「エージェントチームフロー」「workflow-agent-team」「Agent Team で実装」「チームで実装」「チーム並列開発」などで起動。Issue/PR まで作るかは発話・引数から判断し、曖昧なら確認する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
チーム実装計画を作成。ストーリー分析→タスク分解→レビュー（opencode）。 計画は docs/FEATURES/team/{YYMMDD}_{slug}/ に永続化され、複数保持可能。 Trigger: dev:team-plan, /dev:team-plan, チーム計画, team plan
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Evolve an existing team composition by refining its structure in-place or creating a specialized variant. Covers assessing the current team against template and coordination patterns, gathering evolution requirements, choosing scope (adjust members, change coordination pattern, split/merge teams), applying changes to the team file and CONFIG block, updating version metadata, and synchronizing the registry and cross-references. Use when a team's member roster is outdated, coordination pattern no longer fits, user feedback reveals workflow gaps, a specialized variant is needed alongside the original, or agents have been added or removed from the library affecting team composition.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write an empowered team brief. Use when the user says "team brief", "product brief", "give the team a problem", "empowered team", "how do I brief engineering", "delegate to the team", "product mission", or wants to give a team clear goals without dictating the solution - even if they don't say "team brief".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess whether your leadership behaviors amplify or diminish your team using Liz Wiseman's Multipliers framework. Use when a leader asks "am I a good manager", "why isn't my team performing at their potential", "I feel like I'm doing all the thinking for my team", "my team seems dependent on me", "I want to be a better leader", "how do I empower my people", or "my team is smart but underperforming". Also trigger when someone describes always having the best ideas in the room, team members not taking initiative, reports waiting for direction before acting, or a leader who feels exhausted from carrying the team. Diminisher patterns are often invisible to the leader exhibiting them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build an HTML sales presentation for a design team's product rollout decision. Use the product-launch template to organize the proposal, develop slide content, and prepare speaker notes for internal sharing and presentation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a FlowAI-style team management dashboard with member tables, activity history, summary metrics, and charts. The result is a self-contained HTML prototype with working tabs, light and dark themes, panel zoom, chart tooltips, and CSV export.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize an AI team's work into small tasks with one owner and one deliverable each. Record dependencies, check for duplicate tasks, and update progress so the team's recorded task state stays clear.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review an AI team's work against its acceptance criteria using collected evidence. Match requirements to task results or artifacts, distinguish verified facts from agent claims, and identify uncertainty or missing work before recommending completion.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Integrate Microsoft Graph SDK into .NET, TypeScript/JavaScript, or Python applications to access Microsoft 365 data. Covers authentication, permissions, paginated results, incremental synchronization, change notifications, and retries when requests hit service limits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up Havoc infrastructure for authorized attack simulations, including its command server, traffic listeners, Nginx relay servers, and Windows agents. The skill also covers communication profiles and operational precautions for running the infrastructure.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.