菜单
Identifies cloud cost issues, unused resources, and billing optimization opportunities. Use when the user asks about "costs", "billing", "AWS invoice", "cloud spending", "reduce costs", or "optimize resources". Don't use for monitoring setup, deployment, or security.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scans a GitHub repository to understand its tech stack, hosting, monitoring, integrations, and current production readiness. Use when the user asks to "audit", "check", or "scan" their repo. Don't use for code review or bug detection.
Makes a repository AI-native by creating AGENTS.md, .cursorrules, and documentation that helps any AI agent understand the codebase. Follows the WHAT/WHY/HOW framework from best practices. Use when the user asks to "make repo AI-ready", "add cursor rules", "create AGENTS.md", "set up for AI coding", or "make agents work better". Don't use for deployment (use deployment-engineer), monitoring (use monitoring-setup), or code organization (use repo-structurer).
Detects and connects development tools — Slack with GitHub, Linear with Git, error tracking with notifications. Provides step-by-step setup procedures for each integration. Use when the user asks to "connect tools", "link Slack", "set up notifications", "integrate Linear", or "connect my tools". Don't use for monitoring setup (use monitoring-setup), deployment (use deployment-engineer), or security (use security-auditor).
Configures error tracking (Sentry), product analytics (PostHog), health monitoring, and alerting. Provides verification commands and concrete output templates. Use when the user asks to "set up monitoring", "add error tracking", "configure Sentry", "add analytics", or "set up alerts". Don't use for deployment (use deployment-engineer), security (use security-auditor), or integration linking (use integration-linker).
Audits infrastructure setup — database config, caching, performance, and scaling patterns. Provides concrete detection commands and improvement steps. Use when the user asks about "infrastructure", "database setup", "caching", "scaling", "performance", or "architecture". Don't use for CI/CD setup (use deployment-engineer), monitoring (use monitoring-setup), or security (use security-auditor).
Audits repository security — hardcoded secrets, dependency vulnerabilities, environment variable management, and authentication patterns. Use when the user asks to "check security", "find secrets", "audit dependencies", or "secure my repo". Don't use for code review, deployment, or monitoring.
| name | cost-optimizer |
| description | Identifies cloud cost issues, unused resources, and billing optimization opportunities. Use when the user asks about "costs", "billing", "AWS invoice", "cloud spending", "reduce costs", or "optimize resources". Don't use for monitoring setup, deployment, or security. |
Helps identify and reduce cloud infrastructure costs — especially for solo founders who may not realize what they're paying for.
Check for configuration files:
vercel.json → Vercel (check plan tier)serverless.yml / cdk.json → AWSrailway.toml → Railwayfly.toml → Fly.iodocker-compose.yml → Self-hostedsupabase/ → Supabasefirebase.json → FirebaseAWS:
Vercel:
General:
# Check for cloud SDK usage
grep -rn "aws-sdk\|@aws-sdk\|boto3\|firebase\|supabase" --include="*.ts" --include="*.js" --include="*.py" . | head -20
Present a prioritized list of cost savings, estimated monthly impact, and effort to implement.
## 💰 Cost Optimization Report
### Detected Services
- {service}: {estimated tier/cost}
### Quick Wins
1. {action} — est. savings: ${X}/mo — effort: {low/medium/high}
### Cost Monitoring Setup
- {recommended tool}: {how to set up}