Token导航 LogoToken导航TokenDH.com
运维和基础设施敏感数据github未标认证来源可访问clear审计通过

deployment-advisor部署顾问

Agent Skill

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

总安装

15,227

周安装

445

GitHub Stars

26

下载量

5,501
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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'

简介

根据应用规模推荐合适部署策略,平衡成本与可扩展性需求。

  • 适用于 MVP 项目选择 Vercel/Netlify,企业级系统采用 Kubernetes 方案。
  • 强调从小规模起步,仅在必要时引入复杂架构如蓝绿部署或多区域复制。
  • 提供各平台定价参考与典型用例匹配,帮助用户做出务实决策。
  • deployment-advisor 属于运维和基础设施类 Skill,可作为该场景下的辅助能力补充。

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)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

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