aws-compare
Compare 2-3 AWS architecture options side-by-side across cost, complexity, performance, security, and operational burden. Use when evaluating trade-offs between approaches or when the user is deciding between options.
What this skill does
You are comparing AWS architecture options. Your job is to make the trade-offs crystal clear so the user can make an informed decision. ## Process 1. Identify the options to compare (from conversation context or ask the user) 2. Evaluate each option across the dimensions below 3. Present a side-by-side comparison 4. Give an opinionated recommendation with reasoning ## Comparison Dimensions | Dimension | What to Evaluate | |-----------|-----------------| | **Cost** | Monthly baseline, cost at scale, pricing model (per-request vs provisioned), cost optimization options | | **Complexity** | Setup effort, learning curve, operational overhead, number of moving parts | | **Performance** | Latency, throughput, cold starts, scaling speed | | **Security** | Attack surface, encryption defaults, IAM complexity, compliance posture | | **Reliability** | Failure modes, blast radius, recovery time, multi-AZ/region support | | **Team Fit** | Required skills, hiring market, existing team expertise | | **Vendor Lock-in** | Portability, open standards, exit cost | ## Output Format ```markdown # Architecture Comparison: [Context] ## Options ### Option A: [Name] [1-2 sentence description] ### Option B: [Name] [1-2 sentence description] ### Option C: [Name] (if applicable) [1-2 sentence description] ## Side-by-Side | Dimension | Option A | Option B | Option C | |-----------|----------|----------|----------| | Monthly cost (baseline) | $X | $X | $X | | Monthly cost (at scale) | $X | $X | $X | | Setup complexity | Low/Med/High | ... | ... | | Operational burden | Low/Med/High | ... | ... | | Latency (p99) | Xms | Xms | Xms | | Scaling speed | seconds/minutes | ... | ... | | Cold start risk | Yes/No | ... | ... | | Security posture | Good/Better/Best | ... | ... | | Team skill match | Good/Better/Best | ... | ... | | Vendor lock-in | Low/Med/High | ... | ... | ## Detailed Analysis ### Cost [Deep dive on pricing differences] ### When to Choose Each - **Choose A when**: [specific scenarios] - **Choose B when**: [specific scenarios] - **Choose C when**: [specific scenarios] ## Recommendation **Go with [Option X]** because [specific reasoning tied to the user's constraints from discovery]. Caveat: [When this recommendation would change] ``` ## Rules - Always tie the recommendation back to the user's specific constraints (budget, team skills, timeline) - Use actual numbers for cost estimates, not just "cheaper" — use the `aws-pricing` MCP tools or `cost-check` skill - Be opinionated but honest about trade-offs. "It depends" is not helpful without specifics. - If the user hasn't done discovery yet, ask 2-3 key questions before comparing (budget, team skills, scale expectations)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.