Auto-detect deployment targets and deploy projects to hosting platforms.
npx skills add https://github.com/quanganh208/cookmate --skill ck-deploy-quanganh208
Please help me install this Agent Skill. Skill: ck:deploy Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/deploy Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-deploy-quanganh208
This Skill removes the guesswork and manual steps required to publish projects by automatically detecting the appropriate hosting platform from deployment docs and config files, executing authenticated deploy commands, and producing a reproducible deployment record.
Deploy this repository to the recommended platform, authenticate if requested, run the platform deploy command, verify the URL, and update docs/deployment.md.
High-intent search queries and answers about installing and using this skill.
Auto-detecting the best hosting platform for project deployment involves scanning configuration files like vercel.json, netlify.toml, or Dockerfile. The system identifies whether your project is a static site, SPA, SSR app, or Dockerized service to recommend a cost-optimized target.
Yes, this deployment tool supports monorepos and Python APIs alongside static sites, SPAs, SSR frameworks, and Node APIs. It scans project structures and configuration files to apply the appropriate platform-specific deploy commands for each supported architecture.
To deploy a Next.js app to Vercel and update deployment docs, the system checks and authenticates the CLI, runs the platform-specific deploy command, verifies the production URL, and automatically writes or updates the docs/deployment.md file with reproducible steps.
The best way to deploy a Dockerized service to Fly.io is by using automated CLI checks and authentication before running platform-specific deploy commands. The workflow verifies the production URL afterward and records the deployment steps in your documentation.
No, you do not need to manually install CLIs before running deploy commands. The execution workflow automatically checks for the required platform CLIs, installs them if missing, validates authentication, and then proceeds with the deployment process.
No, the deployment workflow does not expose secrets when updating deployment docs. It writes or updates docs/deployment.md with reproducible deployment records while strictly avoiding the disclosure of any sensitive authentication credentials or secrets.
windyskyDeploy and manage Railway container deployments with Docker, volumes, and auto-scaling.
pulsemcpTrigger production deployment workflows and monitor ECS rollout health.
aaronbassettAutomate Flutter deployment guidance across Android, iOS, Web, and Desktop.
ProfPowellDeploy static sites and Node.js services to Cloudflare and DigitalOcean.
