containerize-aspnetcore skill
Containerize an ASP.NET Core project by creating Dockerfile and .dockerfile files customized for the project.
Is the containerize-aspnetcore skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the containerize-aspnetcore skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/github/awesome-copilot.git /tmp/awesome-copilot mkdir -p ~/.claude/skills cp -r /tmp/awesome-copilot/skills/containerize-aspnetcore ~/.claude/skills/containerize-aspnetcore
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
ASP.NET Core Docker Containerization Prompt
Containerization Request
Containerize the ASP.NET Core (.NET) project specified in the settings below, focusing exclusively on changes required for the application to run in a Linux Docker container. Containerization should consider all settings specified here.
Abide by best practices for containerizing .NET Core applications, ensuring that the container is optimized for performance, security, and maintainability.
Containerization Settings
This section of the prompt contains the specific settings and configurations required for containerizing the ASP.NET Core application. Prior to running this prompt, ensure that the settings are filled out with the necessary information. Note that in many cases, only the first few settings are required. Later settings can be left as defaults if they do not apply to the project being containerized.
Any settings that are not specified will be set to default values. The default values are provided in [square brackets].
Basic Project Information
- Project to containerize:
- [ProjectName (provide path to .csproj file)]
- .NET version to use:
- [8.0 or 9.0 (Default 8.0)]
- Linux distribution to use:
- [debian, alpine, ubuntu, chiseled, or Azure Linux (mariner) (Default debian)]
- Custom base image for the build stage of the Docker image ("None" to use standard Microsoft base image):
- [Specify base image to use for build stage (Default None)]
- Custom base image for the run stage of the Docker image ("None" to use standard Microsoft base image):
- [Specify base image to use for run stage (Default None)]
Container Configuration
- Ports that must be exposed in the container image:
- Primary HTTP port: [e.g., 8080]
- Additional ports: [List any additional ports, or "None"]
- User account the container should run as:
- [User account, or default to "$APP_UID"]
- Application URL configuration:
- [Specify ASPNETCORE_URLS, or default to "http://+:8080"]
Build configuration
- Custom build steps that must be performed before building the container image:
- [List any specific build steps, or "None"]
- Custom build steps that must be performed after building the container image:
- [List any specific build steps, or "None"]
- NuGet package sources that must be configured:
- [List any private NuGet feeds with authentication details, or "None"]
Dependencies
- System packages that must be installed in the container image:
- [Package names for the chosen Linux distribution, or "None"]
- Native libraries that must be copied to the container image:
- [Library names and paths, or "None"]
- Additional .NET tools that must be installed:
- [Tool names and versions, or "None"]
System Configuration
- Environment variables that must be set in the container image:
- [Variable names and values, or "Use defaults"]
File System
- Files/directories that need to be copied to the container image:
- [Paths relative to project root, or "None"]
- Target location in container: [Container paths, or "Not applicable"]
- Files/directories to exclude from containerization:
- [Paths to exclude, or "None"]
- Volume mount points that should be configured:
- [Volume paths for persistent data, or "None"]
.dockerignore Configuration
- Patterns to include in the .dockerignore file (.dockerignore will already have common defaults; these are additional patterns):
- Additional patterns: [List any additional patterns, or "None"]
Health Check Configuration
- Health check endpoint:
- [Health check URL path, or "None"]
- Health check interval and timeout:
- [Interval and timeout values, or "Use defaults"]
Additional Instructions
- Other instructions that must be followed to containerize the project:
- [Specific requirements, or "None"]
More skills from github/awesome-copilot
- Aacquire-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.
- Aacreadiness-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.
- Aacreadiness-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.
- Aacreadiness-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.
- Aad-campaign-analyzerUse this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign planning or creative generation without performance data.
- Aadd-educational-commentsAdd educational comments to the file specified, or prompt asking for file to comment if one is not provided.
- Aadobe-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.
- Aagent-architectureDesign AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.
- Aagent-governancePatterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
- Aagent-owasp-complianceCheck any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"
- Aagent-skill-stackFind, evaluate, and assemble the smallest compatible set of AI Agent Skills for an end-to-end natural-language goal. Use when a user wants Skills for a multi-step workflow, asks which Skills fit a project, needs an installed-Skill audit or conflict check, has low Skill recall, wants indirect helpers such as humanizers or compliance checks, or wants a project-specific Skill Stack with controlled installation. Search local Skills, registries, GitHub, and OpenCLI; compare adoption, verified fit, safety, and overlap. Do not use for locating one known or common Skill; use the generic find-skills workflow.
- Aagent-supply-chainVerify supply chain integrity for AI agent plugins, tools, and dependencies. Use this skill when: - Generating SHA-256 integrity manifests for agent plugins or tool packages - Verifying that installed plugins match their published manifests - Detecting tampered, modified, or untracked files in agent tool directories - Auditing dependency pinning and version policies for agent components - Building provenance chains for agent plugin promotion (dev → staging → production) - Any request like "verify plugin integrity", "generate manifest", "check supply chain", or "sign this plugin"