'team' 검색 결과

Team structure, gearing analysis, continuity planning, and competing demand management for legal matters. Use when setting up a matter team, reviewing whether work is being done at the right grade, planning cover for an unavailable team member, or managing a resource conflict across matters. Trigger on: 'who should be on this matter', 'team structure', 'gearing', 'right people at the right level', 'partner is doing associate work', 'cover for maternity leave', 'who has capacity', 'team member leaving', 'over-allocated', 'staffing conflict', 'pinch point', 'capacity problem', 'how do we resource this', 'team too senior', 'team too junior'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task', 'brief for my team', 'team brief', 'definition of done', 'meeting agenda template', 'my team keeps delivering the wrong thing'. Also use when the user says nobody knows who owns what. Not for — the campaign brief the whole team executes from, see `02-campaign-brief-global`; briefing an external agency or freelancer, see `67-agency-vendor-brief-global`; evaluating performance, see `65-team-performance-review-global`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess team health using Patrick Lencioni's Five Dysfunctions of a Team model. Use when a leader says "my team feels off", "we have trust issues", "people aren't speaking up in meetings", "accountability is a problem", "we keep missing commitments", "the team is siloed", "we're not working well together", or "I want to do a team health check". Also trigger when someone describes symptoms like passive agreement in meetings, blame culture, missed deadlines without escalation, or people optimizing for their own metrics over team goals.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Locate BotProfile::Teamwork in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "BotProfile::Teamwork" (symbol BotProfile_Teamwork). This is a VIRTUAL function - resolve the BotProfile::Teamwork vtable via RTTI and identify the slot, then emit the slot. Verify by xrefs from expected call sites. vtable slots commonly differ between platforms - never assume identical indices. Trigger: BotProfile_Teamwork, BotProfile::Teamwork

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review an AI team's recorded progress, blockers, task ownership, and budget usage. This read-only skill separates recorded claims from verified evidence and highlights the next decision the user needs to make.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing completed and active work
• Finding blockers that need a decision
• Checking task owners and unassigned work

Create an agent user in Microsoft Entra ID so an AI agent can access services requiring a user identity. Covers validating the parent agent identity, creating the account, assigning a manager and licenses, and troubleshooting setup errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a user identity linked to an existing agent identity
• Prepare an agent account for a mailbox and Teams
• Assign a manager for organizational chart visibility

Coordinate a small AI development team with planning, implementation, and optional independent testing roles. Adapt the process to the work’s complexity, prepare pull requests, and preserve decisions and next steps so later sessions can continue.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting development or taking over an existing project
• Coordinating implementation and independent testing
• Comparing perspectives on product or architecture decisions

Plan and run authorized security exercises that simulate an attacker's actions, from reconnaissance to activities after entry. Map techniques to MITRE ATT&CK, a framework of attack behaviors, and report detection gaps and response performance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning the scope and objectives of a red team exercise
• Designing scenarios based on a specific threat actor
• Measuring detection and response during an exercise

Diagnose oh-my-codex installation and skill discovery problems by checking configuration, hooks, plugin caches, and optional Team runtime checks. Produce an evidence-based report and carry out confirmed repairs with user approval, then verify the results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate installation or skill discovery failures
• Check for duplicate hooks and legacy settings
• Inspect plugin cache version conflicts

Guide releases of Happy's CLI, mobile app, web app, and server. Choose versions and release channels, follow build and test checks, publish through the designated services, and verify the resulting packages or app updates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Publishing a stable or beta CLI release
• Delivering preview or production mobile updates
• Building native apps and submitting to stores

Supports CTO-level planning for technical direction, organizational structure, and management of P9 teams. It is intended for architectural decisions spanning multiple teams and produces strategic input templates and organizational designs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning technical strategy from a CTO perspective
• Considering architecture decisions across teams
• Designing organizational structure

Turn due diligence findings, collected during a deal review, into briefings for executives, deal leads, or working teams. Highlight material issues, changes since the previous update, review progress, and decisions needed at the level each audience requires.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare an executive briefing on a deal
• Summarize open issues for the deal lead
• Share detailed findings with the working team

Builds, tests, and deploys Microsoft 365 apps and agents for Teams and Copilot. Includes sub-skills for project creation, local testing, cloud deployment, troubleshooting, and Slack-to-Teams migration. USE FOR: Teams agent, bot, tab, message extension, Declarative Agents, Custom Engine Agents, local testing, Agents Playground, Azure resource provision, remote deployment, Slack to Teams migration, cross-platform bot development, Block Kit to Adaptive Cards conversion. DO NOT USE FOR: general web development, non-bot/non-Teams projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Post project updates to team chat, gather feedback, triage responses, and plan next steps. Adapts to available tools (chat, git, issues, tasks). First run discovers tools and saves a playbook; subsequent runs execute from the playbook. Trigger with 'team update', 'post update', 'sync with team', 'standup', 'check team chat', 'feedback loop', 'project update', 'what did the team say'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interact with Microsoft Teams — send and read messages, search conversations, look up people, check calendar, get meeting transcripts, and manage chats. Use this skill whenever the user mentions Teams, MS Teams, Microsoft Teams, wants to send a message, read chat history, search conversations, look up a colleague, check their calendar, find meeting recordings or transcripts, see direct reports or manager, or do anything involving Teams communication. Also trigger when the user asks about scheduling, org chart, people search, or wants to message someone.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing organizational structure (team topologies, Conway's Law alignment), mapping stakeholders by power-interest for change initiatives, defining team interface contracts (APIs, SLAs, decision rights, handoffs), assessing capability maturity (DORA, CMMC, agile maturity models), planning org restructures (functional to product teams, platform teams, shared services), or when user mentions "org design", "team structure", "stakeholder map", "team interfaces", "capability maturity", "Conway's Law", or "RACI".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

红队渗透 / 攻防 — 受授权的红队作业者 + 渗透测试工程师 + 攻击型安全顾问的认知操作系统 (侦察 OSINT / 外网渗透 / 内网 AD 渗透 BloodHound + Kerberoasting + ADCS 利用 + 横向移动 / Web 应用渗透 OWASP WSTG / 移动 OWASP MASTG / 云渗透 AWS Azure GCP IAM 路径 + 容器逃逸 + K8s / C2 操作 Cobalt Strike Sliver Mythic Havoc + OPSEC / 初始访问 + AV EDR 绕过 (仅授权场景) / 无线 RF / 物理社工 / 报告与整改 / 框架 MITRE ATT&CK + D3FEND + PTES + OSSTMM + NIST 800-115 + Kill Chain / 法律伦理 CFAA + 网络安全法 + 刑法 285 286 + 数据安全法 + GDPR + 授权书 + 范围 + 交战规则 — 不含 黑产 / 未授权攻击 / 大规模 exploitation / 供应链投毒 / 未授权 DoS — 这是 重罪 + 行业封杀 + 律师吊销, 本 skill 严守 authorized-only 边界 — 也不含 蓝队 SOC + 恶意软件 即服务 / 僵尸网络 / 勒索软件作者 — 这是 cybercrime 不是 红队) (Cybersecurity Red Team / Offensive Security Operations — the cognitive operating system of authorized red team operators, penetration testers, and offensive security consultants covering (a) reconnaissance & OSINT (passive + active discovery, asset surface mapping), (b) external network pentest (perimeter, exposed services, web), (c) internal network / Active Directory pentest (AD enumeration via BloodHound, Kerberos abuse — Kerberoasting / AS-REP-roasting / Unconstrained delegation / S4U2self, NTLM relay, ADCS abuse, GPO abuse, lateral movement, privilege escalation), (d) web application pentest (OWASP WSTG, authentication, authorization, SSRF, XXE, deserialization, SSTI, prototype pollution, GraphQL, JWT, API), (e) mobile pentest (OWASP MASTG, iOS / Android, instrumentation Frida / Objection, MASVS), (f) cloud pentest (AWS / Azure / GCP — IAM enumeration, privilege escalation paths, container escape, K8s RBAC, serverless), (g) C2 operations & post-exploitation (Cobalt Strike / Sliver / Mythic / Havoc, beacon ops, malleable profiles, OPSEC), (h) initial access & evasion (phishing infrastructure, payload development, AV / EDR evasion, BYOVD, AMSI / ETW bypass — strictly for authorized engagements), (i) wireless / RF (WPA2/3, evil twin, Wi-Fi pivots), (j) physical / social engineering (badge cloning, pretexting, vishing — under engagement letter), (k) reporting & remediation (executive summary, technical findings, CVSS, MITRE ATT&CK mapping, retest), (l) frameworks & methodology (MITRE ATT&CK, MITRE D3FEND, PTES, OSSTMM, NIST SP 800-115, OWASP WSTG / MASTG, Cyber Kill Chain, Unified Kill Chain, Diamond Model), (m) law & ethics (CFAA US, Computer Misuse Act UK, 中国 刑法 285/286 + 网络安全法 + 数据安全法, GDPR for tested EU systems, engagement letter, scope, rules of engagement, safe harbor for bug bounty); NOT criminal hacking / 黑产 / unauthorized targeting / mass exploitation / supply-chain compromise / DoS against unconsented systems (这是 重罪 + 业内开除 + 律师执照吊销, 本 skill 严守 authorized-only 边界), NOT pure defensive blue team / SOC analyst tradecraft (是 平行学科, 仅做 边界标注 + ATT&CK 反推方向), NOT malware-as-a-service development / botnet ops / ransomware authoring (是 cybercrime 不是 红队), NOT 'ethical hacking' 在 'just curious 看看' 自我合理化的灰色操作 (违反 authorization 原则即不是 红队).) Master OS — automated mastery of Cybersecurity Red Team / Offensive Security Operations — the cognitive operating system of authorized red team operators, penetration testers, and offensive security consultants covering (a) reconnaissance & OSINT (passive + active discovery, asset surface mapping), (b) external network pentest (perimeter, exposed services, web), (c) internal network / Active Directory pentest (AD enumeration via BloodHound, Kerberos abuse — Kerberoasting / AS-REP-roasting / Unconstrained delegation / S4U2self, NTLM relay, ADCS abuse, GPO abuse, lateral movement, privilege escalation), (d) web application pentest (OWASP WSTG, authentication, authorization, SSRF, XXE, deserialization, SSTI, prototype pollution, GraphQL, JWT, API), (e) mobile pentest (OWASP MASTG, iOS / Android, instrumentation Frida / Objection, MASVS), (f) cloud pentest (AWS / Azure / GCP — IAM enumeration, privilege escalation paths, container escape, K8s RBAC, serverless), (g) C2 operations & post-exploitation (Cobalt Strike / Sliver / Mythic / Havoc, beacon ops, malleable profiles, OPSEC), (h) initial access & evasi

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: AI teammate / AIチームメイト / AI チームメイト / Agent Template / Foundry Autopilot / Agent 365 / 同僚エージェントの開発・公開。既定は Foundry hosted agent を Agent template として発行する経路。publish_foundry_autopilot.py が必須で、汎用 scripts/deploy.py や SDK agents.create_version だけで完了にしない。明示的な Agent Template / Autopilot 要求の前提が不足したら停止し、通常 Agent・自己ホストへの自動フォールバックは禁止。明示選択の自己ホストは別経路として対応する。M365 Requests の Type=Agent template と Teams Agents for your team での hire を手動確認するまで未完了。初回 scaffold で評価Hub（Code Apps）・Python EvaluationWorker・回帰テスト、publish 時に Foundry Monitor/Evaluations を構成する。CI/CD・レビューゲートは alm に委譲する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Before dispatching a multi-agent team, run a spectral diagnostic on the proposed communication graph and emit a (ρ, Δ, κ) coordination signature plus a pass/fail verdict against per-task-class thresholds. Builds the row-stochastic operator P from the team graph, computes the successor representation M = (I − γP)⁻¹, and ranks the topology for robustness (κ, condition number), consensus (Δ, spectral gap), and drift (ρ, spectral radius). Per Parks & Alharthi (arxiv 2605.11453), rank order on (κ, Δ, ρ) predicts coordination quality pre-execution with rank correlations of 1.0 / 0.5 / −1.0. Triggers: "dispatch the team", "team topology check", "before running the agents", "is this team configuration OK", "team pre-flight".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Locate CCSPlayerController::HandleCommand_JoinTeam in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSPlayerController::HandleCommand_JoinTeam" (symbol CCSPlayerController_HandleCommand_JoinTeam). This is a non-virtual function - emit a byte signature (func_sig), not an offset. Locate it via cross-references, distinctive constants/strings in its body, or callers of related symbols; verify by decompilation before committing to a candidate. Trigger: CCSPlayerController_HandleCommand_JoinTeam, CCSPlayerController::HandleCommand_JoinTeam

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Locate CBaseEntity::m_iTeamNum in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CBaseEntity::m_iTeamNum" (symbol CBaseEntity_m_iTeamNum). This is a STRUCT MEMBER OFFSET (schema netvar), not a function. Resolve the CBaseEntity class layout via the schema/network system; the member must satisfy natural alignment. Cross-check with functions that dereference the member. Trigger: CBaseEntity_m_iTeamNum, CBaseEntity::m_iTeamNum

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI 에이전트가 구현의 많은 부분을 맡는 개발팀을 위해 계획, 책임 분담, 리뷰 기준, 테스트 요구 사항을 정리하고 생성 코드를 다루는 개발 절차를 설계합니다.

• AI 생성 코드를 다루는 개발 규칙 정비
• 코드 리뷰 기준과 승인 조건 설정
• 에이전트가 작업하기 편한 설계 검토

Review a connected Paperclip team's agents, projects, tasks, and pending approvals. Summarize active work, blockers, unavailable agents, and decisions requiring attention, with task references and approval links so the user can inspect the findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Getting an overview of ongoing team work
• Finding blockers and unavailable agents
• Reviewing decisions awaiting approval