'team' 검색 결과

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

연결된 Paperclip 팀의 에이전트, 진행 중인 작업, 장애 요인과 승인 대기 사항을 확인합니다. 담당자가 대응할 내용을 작업 참조와 승인 링크를 붙여 정리합니다.

• 팀의 진행 상황 파악
• 장애 요인과 작업 불가 에이전트 확인
• 판단이 필요한 승인 대기 사항 확인

Build and update Power Automate cloud flows through FlowStudio MCP, a connection that lets an agent use external tools. The skill guides workflow definitions, service connections, deployment, verification, and testing without opening the Power Automate portal.

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

• Build a recurring flow that sends SharePoint updates to Teams
• Add or change actions in an existing flow
• Build a flow triggered by an HTTP request

Coordinate multiple agents on a shared task list to complete development work. Break tasks into clear responsibilities, manage dependencies, and move through planning, implementation, verification, and bounded repair cycles with recorded handoffs.

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

• Fixing TypeScript errors across several modules
• Sharing build-error investigation among agents
• Implementing responsive layouts across pages

Build intermediary servers for authorized security exercises, separating public traffic from the command server used by the test team. It covers simple forwarding, request filtering with nginx or Apache, TLS certificates, and validation against the exercise’s traffic profile.

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

• Separating public infrastructure from an exercise command server
• Filtering exercise traffic against a defined profile
• Adding TLS certificates to a redirector

Support product strategy with market and competitor analysis, vision setting, team design, and performance measures. Includes a Python script that turns company objectives into linked product and team goals and calculates alignment scores.

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

• Turning company goals into product and team goals
• Analyzing markets and competitors
• Defining product vision and KPIs

Send a team announcement through Gmail, then post a notice in a Google Chat space. Use email for the announcement details and a chat message to ask teammates to check their inbox.

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

• Announce policy changes by email and chat
• Send an important update through both channels
• Ask a team in Google Chat to check an announcement email

Guide server-side Zoom integrations using Zoom Rivet SDK in JavaScript or TypeScript. Consult patterns for authentication, incoming event notifications, typed API calls, multiple modules, and webhook processing on AWS Lambda.

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

• Implementing Zoom authentication and token handling
• Building a Team Chat bot with API integration
• Combining multiple Zoom modules in one server

Creates workforce reports from uploaded, pasted, or connected HR data. Analyzes headcount, turnover, diversity, and organizational health, then presents key metrics, trends, methodology, caveats, and practical recommendations for leadership and HR teams.

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

• Prepare a headcount snapshot for leadership
• Analyze turnover trends by team
• Compare workforce representation across levels and teams

Plan team structure and hiring by defining needed roles, headcount, timing, and costs. Produce text-based org charts and prioritized hiring roadmaps, and identify structural risks such as excessive management overhead or dependence on one person.

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

• Plan required roles, headcount, and hiring dates
• Review reporting lines and team boundaries
• Set priorities and sequence upcoming hires

Analyze sprint history to forecast delivery ranges, score team health, and track retrospective actions. Python tools turn structured sprint data into reports that support planning, highlight recurring problems, and show whether improvement efforts are progressing.

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

• Forecasting sprint workload from past delivery data
• Assessing team health and prioritizing improvements
• Tracking retrospective actions and recurring themes

Assess startup engineering operations across delivery, hiring, team structure, and production practices. Use delivery metrics, hiring conversion rates, and staffing data to identify bottlenecks, estimate candidate needs, and plan management roles and operational improvements.

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

• Find where development work waits before release
• Estimate candidate volume needed for hiring goals
• Review team structure and manager hiring needs

Checks how company strategy connects to department, team, and individual goals. Identifies disconnected or conflicting goals, missing ownership, departmental silos, and communication gaps, then guides workshops, shared measures, and quarterly reviews to restore alignment.

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

• Reviewing links between company and team goals
• Finding conflicts between departmental goals
• Assigning ownership to neglected company objectives

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.

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

• Designing a tutorial village or dungeon
• Aligning area layouts with story and visual direction
• Planning enemy encounters and reward placement

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.

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

• Draft dialogue for a boss encounter
• Develop lore for factions and locations
• Place story discoveries within a level

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.

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

• Design and implement a parry mechanic
• Coordinate enemy reactions, effects, and audio events
• Review combat architecture for the configured engine