413 件 ・ 関連度順
概要と使いどころ
Use when working with Codeowners — cODEOWNERS file management covering ownership mapping analysis, coverage gap detection, team assignment validation, orphaned path identification, and review requirement auditing. Use when auditing code ownership across repositories, identifying unowned code paths, validating team configurations, or optimizing pull request review workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Expert en data mesh (domain ownership, data products, self-serve, gouvernance fédérée)
日本語の概要は準備中です。原文の説明を表示しています。
Prove repository ownership, module ownership, assembly boundaries, edit-marker rules, extension points, and test placement.
日本語の概要は準備中です。原文の説明を表示しています。
GitHubやLinear、ローカルの通知を棚卸しし、重要度と担当者に応じた届け先を設計します。重複や不要な通知を整理し、次の対応が分かる運用にまとめるスキル。
製品の要望や企画書を、開発に着手できる具体的な要件へ整理します。業務ルール、データ、サービス間の接点、未決事項を明文化し、次の担当へ引き継ぎます。
GitHubの課題やプルリクエストを仕分けし、実行予定の作業をLinearにつなげて、公開状況と社内の担当・優先度・次の対応を整理するスキル。
Quarkusアプリの認証・アクセス権限・入力検証を実装し、安全性を見直します。秘密情報の管理、パスワード保存、アクセス制限、監査ログや依存関係の点検も扱います。
米国の特許・商標をUSPTOの公式情報で調べ、出願状況、審査書類、権利譲渡の記録を確認し、検索条件や取得日を残して調査結果を整理するスキル。
C++コードの実装・レビュー・改修で、型の扱い、メモリ管理、例外処理、並行処理を点検するスキル。標準的な指針に沿って安全性と書き方の一貫性を整えます。
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.
日本語の概要は準備中です。原文の説明を表示しています。
Run, verify, reseed, and repair Paperclip isolated dev workspace services. Use when asked to start or fix a managed project/worktree service and prove health, login readiness, cloned data, runtime visibility, and correct port ownership.
日本語の概要は準備中です。原文の説明を表示しています。
Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, and decomposing work across agents. Use `orca-cli` for full ownership handoffs — "hand off", "handoff", "handover", "give this to another agent", "another worktree" — unless asked to supervise, monitor, or coordinate a DAG, and for terminal control, lightweight terminal prompts, shell commands, Orca worktree management, and reading or waiting on terminals.
日本語の概要は準備中です。原文の説明を表示しています。
Reports an AI team's progress, blockers, task ownership, and recorded budget. Use when the user asks for status, what is blocked, who owns what, or how much of the budget is recorded as used. Read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team.
日本語の概要は準備中です。原文の説明を表示しています。
Create, write, or manage Meta ads and assets: ad copy, campaigns, spend, reports, audiences, catalogs, product feeds, feed refresh schedules, experiments, and policy. Always load for any request to create or write an ad, or to advertise a product or service, even when no platform is named; this includes sensitive or restricted categories. Always load for any question asking what a Meta, Facebook, or Instagram advertising policy means, allows, prohibits, or requires, including a standalone policy-definition question with no account context. Those questions must use ads_policy_tool, never browser search or memory. Load for a specifically named catalog or feed with an upload or refresh-schedule request; use Ads reads to resolve ownership before writing. Generic unnamed feeds need context. Whether an image, claim or piece of copy may be used in an ad is ALWAYS a Meta Ads task — 'can I use this in an ad', 'is it allowed', 'is this against policy', and any rights, likeness, celebrity, logo or trademark question about advertising with an image, including a follow-up about one just generated. Those are ads-policy questions, not general legal ones. An ad request uses the campaign workflow unless explicitly only an image or organic post.
日本語の概要は準備中です。原文の説明を表示しています。
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks, React/UI conventions, and tests. Review depth adapts to diff size and runtime subagent capability (single-agent or multi-agent reviewer-verifier). Report-only by default; code fixes and GitHub submission each require explicit invocation-time authorization (`fix` / `submit`). Normal-review prompts and safe interruption behavior follow the interaction contract below. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.
日本語の概要は準備中です。原文の説明を表示しています。
Review repository architecture using Ontoly Software Graph and MCP capabilities. Use when asked to explain architecture, module boundaries, package topology, service ownership, or architectural risk.
日本語の概要は準備中です。原文の説明を表示しています。
Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE Starter Kit. Load this skill when asked to: tag or classify flows, set business impact, assign ownership, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run a governance review, generate a compliance report, offboard a maker, or any task that involves writing governance metadata to flows. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app
日本語の概要は準備中です。原文の説明を表示しています。
Use the smallest visual when prose must carry structure—control flow, call depth, module ownership, or change shape: pseudocode, call tree, component/file tree, Mermaid diagram, or diff. Skip it when prose already answers the question.
日本語の概要は準備中です。原文の説明を表示しています。
Parse an investor or client onboarding packet into structured KYC fields — identity, ownership, control, source of funds, and document inventory. Use as the first step of KYC screening; output feeds the rules engine.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX/TAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Create C-suite and VP-level resumes emphasizing strategic leadership, P&L ownership, and board-level impact. Use when the user mentions executive, C-suite, CEO, CFO, CTO, VP, director, or senior leadership resume.
日本語の概要は準備中です。原文の説明を表示しています。