「team」の検索結果

花叔数据分析专家团主理人（数据洞察总监）。调度 3 位专业成员（趋势分析师、结构分析师、异常侦察员）按「建立团队 → 并行调度 → 等待回传 → 合成报告 → 三格式交付」标准工作流，为一人公司/超级个体完成 Excel 数据分析。输出 HTML / XLSX / PPTX 三种格式的综合分析报告。

日本語の概要は準備中です。原文の説明を表示しています。

洞察报告撰写师（若溪 Rex）。综合多源数据分析结果、知识检索发现和可视化图表，撰写结构化分析报告。输出包含执行摘要、核心发现、图表和决策建议的 HTML/Markdown 报告。 触发词：由 copilot-team-lead 主理人调度执行，不直接面向用户。当主理人下发 Phase 3 报告撰写任务时激活。也可响应纯报告撰写需求。

日本語の概要は準備中です。原文の説明を表示しています。

SQL查询架构师（秦逸 Quinn）。将自然语言转换为优化SQL，支持多表关联、窗口函数、CTE；自动探索数据库Schema，执行查询并返回结构化结果与数据画像。 触发词：由 copilot-team-lead 主理人调度执行，不直接面向用户。当主理人下发 Phase 1 数据采集任务时激活。也可响应纯SQL查询类直接请求。

日本語の概要は準備中です。原文の説明を表示しています。

Expert in designing, orchestrating, and managing multi-agent systems (MAS). Specializes in agent collaboration patterns, hierarchical structures, and swarm intelligence. Use when building agent teams, designing agent communication, or orchestrating autonomous workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Multi-agent coordination patterns for building effective AI teams

日本語の概要は準備中です。原文の説明を表示しています。

Best practices for designing Claude Code agent files (.claude/agents/*.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official guidance with battle-tested patterns from agent team usage.

日本語の概要は準備中です。原文の説明を表示しています。

Guide Maestro's Linear issue/task journeys using exact team and issue identities, source-scoped controls, state mappings, and repository PR linkage.

日本語の概要は準備中です。原文の説明を表示しています。

Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.

日本語の概要は準備中です。原文の説明を表示しています。

Route Microsoft Graph work from VS Code. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

Socratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited. Leads you to see the issues through questions, names smells and moves precisely, then closes with a concrete plan.

日本語の概要は準備中です。原文の説明を表示しています。

AI-powered multi-agent code review. Simulates a team of Principal Engineers reviewing code from different perspectives. Use when asked to review code, check a PR, analyze changes, or perform code review.

日本語の概要は準備中です。原文の説明を表示しています。

Use whenever you state a fact. Add a short "Sources:" list at the end of your answer with where each claim came from (file name, URL, or "reasoning"). Shared by every agent on the team.

日本語の概要は準備中です。原文の説明を表示しています。

"Apply the Knowledge-Based View (Grant, 1996) and Nonaka and Takeuchi's SECI model to analyze how organizations create, transfer, and integrate knowledge for competitive advantage. Use this skill when the user needs to design knowledge management systems, understand why knowledge transfer fails across teams, evaluate knowledge creation processes, or when they ask 'how do we capture tacit knowledge', 'why does knowledge stay siloed', or 'how can we turn individual expertise into organizational capability'.".

日本語の概要は準備中です。原文の説明を表示しています。

"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.".

日本語の概要は準備中です。原文の説明を表示しています。

"Design customer service operations including tiered support (L1/L2/L3), response templates, SLA definitions, escalation procedures, and complaint handling. Use this skill when the user needs to set up a CS team, create service standards, design escalation flows, or improve response quality — even if they say 'our CS is a mess', 'how should we handle complaints', 'set up support tiers', or 'create CS SOPs'.".

日本語の概要は準備中です。原文の説明を表示しています。

Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.

日本語の概要は準備中です。原文の説明を表示しています。

Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.

日本語の概要は準備中です。原文の説明を表示しています。

Forensic scan for npm/PyPI supply-chain compromise (Shai-Hulud/TeamPCP campaigns) — checks persistence, hook injection, compromised packages, IOC strings, C2, dead-man switches. Use when auditing a machine or repo for malicious dependencies. Trigger on "supply chain audit", "check for compromised packages", "Shai-Hulud", "scan for malicious deps".

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate sprint planning by organizing backlog items, estimating effort, balancing capacity, identifying dependencies, and producing a sprint commitment summary. Use when teams need structured sprint planning output. Do not use for strategic roadmap planning, annual budgeting, or product vision work.

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate monthly S&OP or integrated business planning cycles by aligning demand, supply, inventory, capacity, and executive decisions with a standard meeting rhythm and decision log. Use when operations teams need a demand review, supply review, pre-S&OP reconciliation, or executive S&OP pack. Do not use for single-SKU replenishment math only.

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate and document Sprint Retrospectives per Scrum Guide 2020. Choose format by team maturity, structure the session, capture action items, and track improvement across sprints. Use after every sprint. Do not use for individual performance reviews, blame sessions, or annual assessments.

日本語の概要は準備中です。原文の説明を表示しています。

Write and cascade OKRs (Objectives and Key Results) for company, department, team, or project level. Ensure objectives are inspiring and key results are measurable outcomes. Includes weekly check-in template. Use at the start of each quarter or when aligning strategy to execution. Do not use for KPI performance reviews or daily task tracking.

日本語の概要は準備中です。原文の説明を表示しています。

Create practical role-specific onboarding checklists with owners, timing, access needs, and first-week milestones. Use for new hire, contractor, client, or team onboarding.

日本語の概要は準備中です。原文の説明を表示しています。

Compare policies, procedures, onboarding files, or operating evidence against a named compliance framework such as AML/KYC, privacy, internal controls, or audit readiness. Use when a team needs a gap matrix, control checklist, remediation priorities, or evidence request list. Do not use when no target framework is specified or when formal legal or regulatory sign-off is required.

日本語の概要は準備中です。原文の説明を表示しています。