スキルを探す

セキュリティ診断の方式と対象の技術構成に応じて、必要なスキル群や報告形式を選び、読み込んだ内容を一覧化して診断開始の準備を整えるスキル。

• レッドチーム診断のスキル準備
• Webアプリ診断のスキル読み込み
• 複数ホストの技術別スキル選定

初期アクセス取得後の内網テストで、別ホストへの移動や認証情報の取得、権限昇格などの手順資料を案内するスキル。AD・ADCSやトンネル接続も扱います。

• 初期アクセス後の内網テストを計画したいとき
• 横移動や認証情報取得の資料を探したいとき
• 権限昇格やアクセス維持の検証項目の確認

OneDriveのファイル検索やアップロード・ダウンロード、フォルダ整理、共有リンク作成、アクセス権の確認と変更をRube MCP経由で自動化するスキル。

• OneDrive内の資料を探したいとき
• ファイルをアップロード・ダウンロード
• ファイルやフォルダの整理

Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evaluations, managing connections/deployments/datasets/indexes, or using OpenAI-compatible clients. This is the high-level Foundry SDK - for low-level agent operations, use azure-ai-agents-python skill.

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

Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: "PersistentAgentsClient", "persistent agents", "agent threads", "agent runs", "streaming agents", "function calling agents .NET".

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

Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore (including the Harness managed agent loop). Applies when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, migrating/porting/converting a Bedrock Agent (including inline agents) to an AgentCore Harness, troubleshooting Bedrock errors (ThrottlingException, AccessDeniedException), or choosing models (Claude, Llama, Nova, Titan). Also for prompt caching, quota and throttling diagnosis, cost tracking, migrating between Claude model generations (4.5 to 4.6 to 4.7), chunking strategies, API selection (Converse vs InvokeModel), guardrail capabilities, and model selection. Also covers AgentCore Payments (x402, microtransactions, Payment Manager, Connector, Instrument, Coinbase CDP, Stripe Privy, paid endpoints, agent payments). NOT for custom model training, Rekognition, or Comprehend.

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

Analyzes the user's business problem and recommends the right backend integration approach — Web API, AI Web API (generative summaries / grounded search), Server Logic, Cloud Flows, or a combination — for a Power Pages site, then routes to the appropriate specialized skill. Use when the user wants to add backend integration, connect to data, add AI summaries, or needs help deciding which backend approach to use.

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

Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it.

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

Adds a data source or connector to a Power Apps code app. Asks what the user wants to accomplish and routes to the appropriate specialized skill.

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

Use when adding an unspecified data source to an Expo/React Native Power Apps mobile app; routes to Dataverse, SharePoint, or another connector.

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

Use when the user wants to iterate on an existing generated Power Apps mobile app after /create-mobile-app: update Application Insights configuration, the plan, data model, native capabilities, design, screens, generated app code, and preview without restarting the full project flow. Natural-language triggers include 'the app already exists', 'edit my app', 'change this screen', and 'add a feature to this app'.

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

Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.

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

Adds Work IQ (M365 Copilot Search) to a Power Apps code app via the Work IQ Copilot MCP connector (shared_a365copilotchatmcp), then wires up a production-ready McpSession wrapper for AI-powered, knowledge-grounded search and chat. Use when integrating Microsoft 365 Copilot search/chat. The CopilotChat tool searches internal Microsoft 365 content (documents, emails, chats, sites, files) across your organization — prefer workload-specific tools (SharePoint, OneDrive, Teams, Mail) when the workload is explicit; do not use it for general knowledge, news, public web, or external information.

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

Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile app and no dedicated mobile connector skill exists.

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

Use when the user wants to read or write SharePoint lists, manage documents in a SharePoint document library, or create a new SharePoint list from a Power Apps mobile app.

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

Adds SharePoint Online connector to a Power Apps code app. Use when reading lists, managing documents, or integrating with SharePoint sites. Can also create new SharePoint lists.

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

Creates Power Apps code apps using React and Vite. Use when building code apps, scaffolding projects, or deploying to Power Platform.

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

Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to add a data source, add a connection, add an API, add a connector, connect to SharePoint / Dataverse / SQL / Excel / OneDrive / Teams / Office 365, or any similar request to make new data available to the app. DO NOT USE WHEN the user is asking to list or describe existing data sources — call list_data_sources or list_apis directly instead.

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

Creates, updates, and deploys Power Apps generative pages for model-driven apps using React v17, TypeScript, and Fluent UI V9. Orchestrates specialist agents for planning, entity creation, and code generation. Use it when user asks to build, retrieve, or update a page in an existing Microsoft Power Apps model-driven app. Use it when user mentions "generative page", "page in a model-driven", or "genux". Do not use it for a generic or standalone React or web app, website, or dashboard (including a Power Apps code app), for Power Pages, canvas apps, or Power Automate, or when the user rules out Power Platform, Dataverse, or model-driven apps (for example "no Power Platform"). A generative page only runs inside a model-driven app, and this skill cannot scaffold a standalone project. This skill stands alone and does not require /app-builder — but if the user wants a whole app built (tables, forms, views, sitemap) rather than pages for an app that already exists, use /app-builder instead.

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

Use when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch.

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

Adds Excel Online (Business) connector to a Power Apps code app. Use when reading or writing Excel workbook data from OneDrive or SharePoint.

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

Microsoft 365 tenant administration for Global Administrators. Use for tenant setup, Azure AD user management, Exchange Online and Teams config, Conditional Access policies, license management, and PowerShell bulk-operation scripts.

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

Comprehensive Microsoft 365 tenant administration skill for setup, configuration, user management, security policies, and organizational structure optimization for Global Administrators

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

Stakeholder mapping, communication plan design, reporting hierarchy, and mid-matter comms updates. Use when setting up a new matter and needing to identify who needs what information, designing the communication rhythm, building reporting structures for multi-jurisdiction programmes, or updating the comms plan when the stakeholder landscape changes. Trigger on: 'stakeholder map', 'who needs to be kept informed', 'communication plan', 'reporting structure', 'who do we report to', 'how often do we meet', 'client wants more updates', 'new contact on the client side', 'build the comms plan', 'reporting hierarchy', 'HQ vs regions', 'who is the decision maker', 'comms rhythm', 'meeting cadence', 'status call schedule'.

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