semantic-kernel

# Semantic Kernel Use this skill when working with applications, plugins, function-calling flows, or AI integrations built on Semantic Kernel. Always ground implementation advice in the latest Semantic Kernel documentation and samples rather than memory alone. ## Determine the target language first Choose the language workflow before making recommendations or code changes: 1. Use the **.NET** workflow when the repository contains `.cs`, `.csproj`, `.sln`, or other .NET project files, or when the user explicitly asks for C# or .NET guidance. Follow [references/dotnet.md](references/dotnet.md). 2. Use the **Python** workflow when the repository contains `.py`, `pyproject.toml`, `requirements.txt`, or the user explicitly asks for Python guidance. Follow [references/python.md](references/python.md). 3. If the repository contains both ecosystems, match the language used by the files being edited or the user's stated target. 4. If the language is ambiguous, inspect the current workspace first and then choose the closest language-specific reference. ## Always consult live documentation - Read the Semantic Kernel overview first: <https://learn.microsoft.com/semantic-kernel/overview/> - Prefer official docs and samples for the current API surface. - Use the Microsoft Docs MCP tooling when available to fetch up-to-date framework guidance and examples. ## Shared guidance When working with Semantic Kernel in any language: - Use async patterns for kernel operations. - Follow off...