create▌

Generate a complete TypeSpec declarative agent for Microsoft 365 Copilot with instructions, capabilities, and conversation starters. \n \n Produces a main.tsp file with agent declaration, instructions, conversation starters, and capability definitions following Microsoft's TypeSpec M365 Copilot schema \n Supports 10 capability types including WebSearch, OneDriveAndSharePoint, TeamsMessages, Email, People, CodeInterpreter, GraphicArt, GraphConnectors, Dataverse, and Meetings with optional scoping

Generate TypeSpec API plugins for Microsoft 365 Copilot with REST operations, authentication, and Adaptive Cards. \n \n Scaffolds complete TypeSpec projects with agent definitions (main.tsp) and API operations (actions.tsp) following Microsoft 365 Copilot conventions \n Supports four authentication modes: public APIs, API key headers, OAuth2 with authorization code flow, and registered auth references \n Includes optional confirmation dialogs for destructive operations and Adaptive Card template

Create comprehensive documentation for the object-oriented component(s) at: ${input:ComponentPath}.

Turn a user prompt into a single, actionable plan delivered in the final assistant message.

Create new scientific tools following established patterns.

通过 MCP 调用 create-doc，从 Lark-flavored Markdown 内容创建一个新的飞书云文档。

This utility skill creates new Magento 2 modules in app/code/. It is designed to be called by other skills that need module scaffolding.

Create pull requests following the best engineering practices.

Scaffold a declarative agent for Microsoft 365 Copilot integrated with an MCP server. \n \n Generates complete project structure including manifest.json, declarativeAgent.json, and ai-plugin.json with tool definitions auto-imported from MCP servers \n Supports OAuth 2.0 and SSO authentication with environment variable configuration and secure credential storage \n Provides response semantics mapping to extract and format API response data for Copilot consumption \n Includes MCP server integratio

Create concise, example-driven tldr pages from documentation URLs and command names. \n \n Requires both a command name and authoritative documentation URL; provides guidance if either is missing \n Extracts 5–8 most common use cases ordered by frequency, following strict tldr-pages project formatting standards \n Uses {{placeholder}} syntax for options, arguments, and user-provided values with specific conventions for flags, options with arguments, and subcommands \n Validates documentation sou