semantic-kernel
$
npx mdskill add github/awesome-copilot/semantic-kernelGenerate, modify, or review Semantic Kernel solutions for .NET and Python AI integrations.
- Assists with building or improving AI workflows using Semantic Kernel frameworks.
- Integrates with Semantic Kernel's official documentation and language-specific samples.
- Determines the correct language context by inspecting project files or user requests.
- Provides implementation advice and code suggestions grounded in current official resources.
SKILL.md
.github/skills/semantic-kernelView on GitHub ↗
--- name: semantic-kernel description: 'Create, update, refactor, explain, or review Semantic Kernel solutions using shared guidance plus language-specific references for .NET and Python.' --- # 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 official plugin and function-calling patterns. - Implement explicit error handling and logging. - Prefer strong typing, clear abstractions, and maintainable composition patterns. - Use built-in connectors for Azure AI Foundry, Azure OpenAI, OpenAI, and other AI services, while preferring Azure AI Foundry services for new projects when that fits the task. - Use the kernel's memory and context-management capabilities when they simplify the solution. - Use `DefaultAzureCredential` when Azure authentication is appropriate. ## Workflow 1. Determine the target language and read the matching reference file. 2. Fetch the latest official docs and samples before making implementation choices. 3. Apply the shared Semantic Kernel guidance from this skill. 4. Use the language-specific package, repository, sample paths, and coding practices from the chosen reference. 5. When examples in the repo differ from current docs, explain the difference and follow the current supported pattern. ## References - [.NET reference](references/dotnet.md) - [Python reference](references/python.md) ## Completion criteria - Recommendations match the target language. - Package names, repository paths, and sample locations match the selected ecosystem. - Guidance reflects current Semantic Kernel documentation rather than stale assumptions.
More from github/awesome-copilot
- acquire-codebase-knowledgeUse this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
- acreadiness-assessRun the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
- acreadiness-generate-instructionsGenerate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
- acreadiness-policyHelp the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
- add-educational-comments'Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.'
- adobe-illustrator-scriptingWrite, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model, coordinate system, measurement units, export workflows, and scripting best practices.
- agent-governance|
- agent-owasp-compliance|
- agent-supply-chain|
- agentic-eval|