Token导航 LogoToken导航

Agent Skill · 运维和基础设施

deployment-advisor(部署顾问)

用于辅助云资源、部署、容器、基础设施和运维自动化任务。它适合让 Agent 检查配置、整理部署步骤、分析资源状态、生成排障思路或辅助云服务接入。使用时需要明确目标环境、账号权限、区域和资源组,区分本地测试与生产操作;涉及删除资源、重启服务、修改网络或权限配置时,应先确认影响范围。

deployment-advisor 是运维和基础设施类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,第三方扫描已通过,按安装量在运维和基础设施类的 2,449 个 Skill 里排第 150。

总安装 15,227周安装 445GitHub Stars 26下载 5,501核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:deployment-advisor(部署顾问)
来源仓库:https://github.com/daffy0208/ai-dev-standards
仓库路径:skills/deployment-advisor
安装命令:
npx skills add https://github.com/daffy0208/ai-dev-standards --skill 'Deployment Advisor'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/daffy0208/ai-dev-standards --skill 'Deployment Advisor'

这个 Skill 是做什么的

运维和基础设施类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

根据应用规模推荐合适部署策略,平衡成本与可扩展性需求。适用于 MVP 项目选择 Vercel/Netlify,企业级系统采用 Kubernetes 方案。强调从小规模起步,仅在必要时引入复杂架构如蓝绿部署或多区域复制。提供各平台定价参考与典型用例匹配,帮助用户做出务实决策。

deployment-advisor 属于运维和基础设施类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/deployment-advisor

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/daffy0208/ai-dev-standards --skill 'Deployment…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

deployment-advisor 怎么安装?

在终端执行 npx skills add https://github.com/daffy0208/ai-dev-standards --skill 'Deployment Advisor'。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

deployment-advisor 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

deployment-advisor 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

deployment-advisor 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

deployment-advisor 用的人多吗?

公开数据是累计安装 15,227 次,近一周安装 445 次,下载 5,501 次,GitHub 26 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

deployment-advisor 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理运维和基础设施类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

运维和基础设施类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
brainstorming

头脑风暴 · Codex、Claude

3,148,776173,131操作浏览器MIT通过
copywriting

文案写作 · Codex、Claude

1,996,72425,583需要联网MIT通过
openclaw-secure-linux-cloud

OpenClaw secure linux cloud 命令行 · Codex、Claude

1,853,08840接触敏感数据未明确未通过
xget

xget 命令行 · Codex、Claude

1,799,28040执行命令未明确未通过
requesting-code-review

代码审查请求 · Codex、Claude

1,590,144173,103权限未标注MIT通过
deployment-advisor

部署顾问 · 本页

15,22726接触敏感数据MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Deployment Advisor

Choose the right deployment strategy for your application scale and requirements.

Core Principle

Start simple, scale when needed. Don't over-engineer infrastructure for 10 users that won't arrive for months.

Deployment Tiers

Tier 1: MVP / Small Projects (<1,000 users)

Cost: $0-$20/month Time to Deploy: 5-15 minutes Best for: MVPs, prototypes, side projects, marketing sites

Recommended Platforms:

Vercel (Next.js, React, static sites):

  • Push to GitHub → auto deploy
  • Edge functions, image optimization
  • Free SSL, global CDN
  • $0 for hobby, $20/mo for team

Netlify (Static sites, Jamstack):

  • Similar to Vercel, better for non-Next.js
  • Form handling, split testing
  • Serverless functions

Railway (Full-stack, databases):

  • Deploys anything (Node, Python, Go, Rust)
  • Integrated PostgreSQL, Redis, MongoDB
  • $5/mo for 512MB RAM + usage

Cloudflare Pages (Static + Workers):

  • Free unlimited bandwidth
  • Edge functions (Workers)
  • Fastest CDN globally

Tier 2: Growing Products (1K-100K users)

Cost: $20-$500/month Time to Deploy: 1-4 hours Best for: Validated products, growing startups, paid customers

Recommended Platforms:

AWS Amplify (Full-stack web apps):

  • Managed hosting + backend
  • Authentication, APIs, databases
  • Auto-scaling, monitoring
  • $50-200/mo typical

Google Cloud Run (Containerized apps):

  • Pay only for actual usage
  • Scales to zero
  • Automatic HTTPS
  • $20-100/mo for small traffic

Fly.io (Distributed apps):

  • Global deployment (closer to users)
  • PostgreSQL, Redis included
  • Docker-based
  • $50-200/mo

Render (Simpler alternative to AWS):

  • Auto-deploy from Git
  • PostgreSQL, Redis, cron jobs
  • Free tier available
  • $50-150/mo for production

Tier 3: Scale / Enterprise (100K+ users)

Cost: $500-$5,000+/month Time to Deploy: 1-4 weeks Best for: High traffic, enterprise, compliance requirements

Recommended Platforms:

AWS ECS (Containers, no Kubernetes complexity):

  • Fargate (serverless containers)
  • Full AWS ecosystem
  • Fine-grained control
  • $500-2000/mo typical

AWS EKS / Google GKE (Kubernetes):

  • Full orchestration
  • Multi-region, auto-scaling
  • Complex but powerful
  • $1000-5000+/mo

DigitalOcean App Platform (Mid-tier simplicity):

  • Kubernetes-powered, no K8s knowledge needed
  • Cheaper than AWS
  • Good middle ground
  • $200-1000/mo

Decision Framework

Question 1: What are you deploying?

Static site (HTML, CSS, JS): → Vercel, Netlify, Cloudflare Pages

Next.js app: → Vercel (best integration), Netlify

React/Vue/Angular SPA: → Vercel, Netlify, Cloudflare Pages

Node.js API: → Railway, Render, Fly.io, AWS Amplify

Python API (FastAPI, Flask, Django): → Railway, Render, Fly.io, Google Cloud Run

Go/Rust API: → Fly.io, Railway, Google Cloud Run

Full-stack (Frontend + Backend + DB): → Railway, Render, AWS Amplify

Microservices: → Fly.io, Google Cloud Run, AWS ECS

Question 2: Do you need a database?

No database: → Vercel, Netlify, Cloudflare Pages

Serverless database (PostgreSQL, MySQL): → Railway, Render (integrated), AWS RDS, Supabase

Redis/caching: → Railway, Render, AWS ElastiCache, Upstash

MongoDB: → MongoDB Atlas, Railway, AWS DocumentDB

Question 3: How many users?

<100 users (MVP): → Free/cheap tiers: Vercel free, Railway $5

100-1,000 users: → Vercel Pro ($20), Railway ($20-50), Render

1K-10K users: → Railway ($50-100), AWS Amplify, Cloud Run

10K-100K users: → AWS Amplify, Cloud Run, Fly.io ($100-500)

100K-1M users: → AWS ECS, GKE, dedicated servers ($500-5000)

Question 4: Geographic distribution?

Single region (US/Europe): → Any platform

Global (low latency worldwide): → Cloudflare Pages/Workers, Vercel Edge, Fly.io (multi-region)

China/Asia: → Cloudflare, Fly.io Hong Kong, Alibaba Cloud

Question 5: Special requirements?

Compliance (HIPAA, SOC 2, GDPR): → AWS, Google Cloud, Azure (compliance certifications)

Long-running jobs (>15 min): → Railway, Render Background Workers, AWS ECS

WebSockets/real-time: → Railway, Render, Fly.io, AWS ECS

High compute (video processing, ML): → AWS ECS/EKS, Google Cloud Run, dedicated GPUs


CI/CD Pipeline Setup

Tier 1: Git Push Auto-Deploy

Platforms: Vercel, Netlify, Railway, Render

Setup (5 minutes):

  1. Connect GitHub/GitLab repo
  2. Configure build command: npm run build
  3. Configure output directory: dist or .next
  4. Push to main branch → auto deploy

Environment Variables:

DATABASE_URL=postgresql://...
API_KEY=secret_key
NODE_ENV=production

Preview Deployments:

  • Every pull request gets preview URL
  • Test before merging to production

Tier 2: GitHub Actions CI/CD

Use when: Custom tests, security scans, multi-stage deploys

# .github/workflows/deploy.yml
name: Deploy to Production

on:
  push:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '18'
      - run: npm ci
      - run: npm test
      - run: npm run lint

  deploy:
    needs: test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: amondnet/vercel-action@v20
        with:
          vercel-token: ${{ secrets.VERCEL_TOKEN }}
          vercel-org-id: ${{ secrets.ORG_ID }}
          vercel-project-id: ${{ secrets.PROJECT_ID }}
          vercel-args: '--prod'

Tier 3: Enterprise CI/CD

Features:

  • Multi-environment (dev, staging, prod)
  • Blue-green deployments
  • Canary releases
  • Automated rollbacks
  • Security scanning (SAST, DAST)

Pipeline Stages:

Build → Test → Security Scan → Stage Deploy → Integration Tests → Prod Deploy

Tools:

  • GitHub Actions, GitLab CI, CircleCI
  • ArgoCD (GitOps for Kubernetes)
  • Terraform (Infrastructure as Code)

Deployment Checklist

Pre-Launch

  • Environment variables configured
  • Database migrations tested
  • SSL/HTTPS enabled
  • Custom domain connected
  • Error monitoring set up (Sentry, Rollbar)
  • Analytics configured
  • Backup strategy defined

Launch Day

  • Deploy to production
  • Verify all pages load
  • Test critical user flows
  • Check error monitoring dashboard
  • Monitor performance metrics
  • Have rollback plan ready

Post-Launch

  • Monitor logs for errors
  • Check performance (response times)
  • Verify analytics tracking
  • Review cost/usage
  • Document any issues
  • Plan scaling strategy

Common Deployment Patterns

Pattern 1: Jamstack (Static + API)

Stack: Next.js (Vercel) + API (Railway/Supabase)

Pros: Fast, cheap, scales easily Cons: Not suitable for real-time or server-heavy apps

Frontend (Vercel) → API (Railway) → Database (Supabase)

Pattern 2: Serverless

Stack: Vercel Functions + Serverless DB (Supabase/PlanetScale)

Pros: Zero server management, pay per use Cons: Cold starts, vendor lock-in

Frontend (Vercel) → Edge Functions (Vercel) → Serverless DB

Pattern 3: Traditional Full-Stack

Stack: Railway (Node.js + PostgreSQL)

Pros: Simple, everything in one place Cons: Single point of failure

Railway: Node.js API + PostgreSQL + Redis

Pattern 4: Microservices

Stack: Multiple Cloud Run services + Cloud SQL

Pros: Independent scaling, fault isolation Cons: Complex, higher cost

Frontend (Vercel) → Service 1 (Cloud Run) → Database
                 → Service 2 (Cloud Run) → Queue

Cost Optimization

Free Tier Strategy

  • Vercel: Free for personal projects
  • Supabase: 500MB DB, 50K API requests/day
  • Railway: $5 credit/month (enough for small API)
  • Cloudflare: Unlimited bandwidth free

Total: $0-5/month for MVP

Production Cost Optimization

  • Use caching (Redis, CDN) to reduce compute
  • Optimize images (Next.js Image, Cloudinary)
  • Database connection pooling (PgBouncer)
  • Monitor and right-size resources
  • Use spot instances for non-critical workloads

Security Best Practices

Must-Haves

  • ✅ HTTPS only (automatic on most platforms)
  • ✅ Environment variables for secrets (never commit)
  • ✅ Database encryption at rest
  • ✅ Regular dependency updates
  • ✅ Rate limiting on APIs

Recommended

  • Security headers (helmet.js for Node)
  • DDoS protection (Cloudflare)
  • Automated vulnerability scanning
  • Audit logs for sensitive operations
  • Backup and disaster recovery plan

Monitoring & Observability

Tier 1: Basic Monitoring

  • Platform dashboards (Vercel Analytics, Railway Metrics)
  • Error tracking: Sentry ($0-26/mo)
  • Uptime monitoring: UptimeRobot (free), Better Uptime

Tier 2: Enhanced Monitoring

  • APM: New Relic, Datadog ($15-100/mo)
  • Log aggregation: LogTail, Papertrail
  • Custom metrics and alerting

Tier 3: Enterprise Observability

  • Full stack: Datadog, New Relic ($300-1000+/mo)
  • Distributed tracing (OpenTelemetry)
  • Custom dashboards (Grafana)
  • PagerDuty for incidents

Quick Start Recommendations

Simple marketing site: → Vercel + Contentful CMS

SaaS MVP: → Next.js (Vercel) + Supabase (DB + Auth) + Stripe

Internal tool: → React (Netlify) + FastAPI (Railway) + PostgreSQL (Railway)

Mobile app backend: → FastAPI (Cloud Run) + Cloud SQL + Firebase Auth

E-commerce: → Next.js (Vercel) + Shopify/Stripe + PostgreSQL (Supabase)


Related Resources

Related Skills:

  • frontend-builder - For building apps to deploy
  • api-designer - For API architecture
  • performance-optimizer - For optimizing deployed apps

Related Patterns:

  • META/DECISION-FRAMEWORK.md - Platform selection guidance
  • STANDARDS/architecture-patterns/deployment-patterns.md - Deployment architectures (when created)

Related Playbooks:

  • PLAYBOOKS/deploy-to-vercel.md - Vercel deployment guide (when created)
  • PLAYBOOKS/setup-cicd.md - CI/CD setup procedure (when created)

平台分布

Claude Code

30.78%
按下载量换算1,693

Antigravity

23.65%
按下载量换算1,301

OpenCode

17.65%
按下载量换算971

Gemini CLI

12.07%
按下载量换算664

Codex

7.33%
按下载量换算403

windsurf

3.35%
按下载量换算184

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills