ASP.NET Core Application Development
Build or review ASP.NET Core web applications, from MVC and Minimal APIs to authentication, testing and deployment, using matching .NET guid…
Deploy any project to Vercel instantly. Always deploy as preview (not production) unless the user explicitly asks for production.
command -v vercel).sandbox_permissions=require_escalated).command -v vercel
vercel is installed, run this (with a 10 minute timeout):vercel deploy [path] -y
Important: Use a 10 minute (600000ms) timeout for the deploy command since builds can take a while.
vercel is not installed, or if the CLI fails with "No existing credentials found", use the fallback method below.If CLI fails with auth error, use the deploy script:
skill_dir="<path-to-skill>"
# Deploy current directory
bash "$skill_dir/scripts/deploy.sh"
# Deploy specific project
bash "$skill_dir/scripts/deploy.sh" /path/to/project
# Deploy existing tarball
bash "$skill_dir/scripts/deploy.sh" /path/to/project.tgz
The script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with previewUrl and claimUrl.
Tell the user: "Your deployment is ready at [previewUrl]. Claim it at [claimUrl] to manage your deployment."
Only if user explicitly asks:
vercel deploy [path] --prod -y
Show the user the deployment URL. For fallback deployments, also show the claim URL.
Do not curl or fetch the deployed URL to verify it works. Just return the link.
If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the actual deploy command with escalated permissions (use sandbox_permissions=require_escalated). Do not escalate the command -v vercel installation check. The deploy requires escalated network access when sandbox networking blocks outbound requests.
Example guidance to the user:
The deploy needs escalated network access to deploy to Vercel. I can rerun the command with escalated permissions—want me to proceed?
Source: openai · MIT · SHA-256 shown alongside the download.
License file included. A license and checksum are not a security certification. Review package instructions and scripts before running them.
openai-vercel-deploy/LICENSE.txt1063 bytesopenai-vercel-deploy/SKILL.md2770 bytesopenai-vercel-deploy/SOURCE.txt216 bytesopenai-vercel-deploy/assets/vercel-small.svg243 bytesopenai-vercel-deploy/assets/vercel.png788 bytesopenai-vercel-deploy/scripts/deploy.sh8877 bytesAn adaptation record is bundled. Inspect the declared changes and archived original before use. Review adaptation and original-file hashes →
Machine-readable installation guide →Records are supplied by the site administrator and bound to a specific package. They are not third-party safety certification. This page does not execute skills.
No published scenario records yet. Resource availability and download counts do not imply measured task performance.
Be the first to share your experience.
Sign in to leave a review →Links use published guide associations and catalog labels. Inspect each resource’s requirements and license.
Build or review ASP.NET Core web applications, from MVC and Minimal APIs to authentication, testing and deployment, using matching .NET guid…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores u…
Build or review Windows desktop applications with C#, WinUI 3 and the Windows App SDK, including layout, accessibility, testing and packagin…
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarif…