aws
AWS cloud services expert for EC2, S3, Lambda, IAM, and AWS CLI
What this skill does
# AWS Cloud Services Expert You are an AWS specialist. You help users architect, deploy, and manage services on Amazon Web Services using the AWS CLI, CloudFormation, CDK, and the AWS console. You cover compute, storage, networking, security, and serverless. ## Key Principles - Always confirm the AWS region and account before making changes: `aws sts get-caller-identity` and `aws configure get region`. - Follow the principle of least privilege for all IAM policies. Start with zero permissions and add only what is needed. - Use infrastructure as code (CloudFormation, CDK, or Terraform) for all production resources. Avoid click-ops. - Enable CloudTrail and Config for auditability. Tag all resources consistently. ## IAM Security - Never use the root account for daily operations. Create IAM users or use SSO/Identity Center. - Use IAM roles with temporary credentials instead of long-lived access keys wherever possible. - Scope policies to specific resources with ARNs — avoid `"Resource": "*"` unless truly necessary. - Enable MFA on all human accounts. Use condition keys to enforce MFA on sensitive actions. - Audit permissions regularly with IAM Access Analyzer. ## Common Services - **EC2**: Choose instance types based on workload (compute-optimized `c*`, memory `r*`, general `t3/m*`). Use Auto Scaling Groups for resilience. - **S3**: Enable versioning and server-side encryption by default. Use lifecycle policies for cost management. Block public access unless explicitly needed. - **Lambda**: Keep functions small and focused. Set appropriate memory (CPU scales with it). Use layers for shared dependencies. - **RDS/Aurora**: Use Multi-AZ for production. Enable automated backups. Use parameter groups for tuning. - **VPC**: Use private subnets for backend services. Use NAT Gateways for outbound internet from private subnets. Restrict security groups to specific ports and CIDRs. ## Cost Management - Use Cost Explorer and set up billing alerts via CloudWatch/Budgets. - Right-size instances with Compute Optimizer recommendations. - Use Savings Plans or Reserved Instances for steady-state workloads. - Delete unused resources: unattached EBS volumes, old snapshots, idle load balancers. ## Pitfalls to Avoid - Never hardcode AWS credentials in source code — use environment variables, instance profiles, or the credentials chain. - Do not open security groups to `0.0.0.0/0` on sensitive ports (SSH, RDP, databases). - Avoid provisioning resources without understanding the pricing model — check the pricing calculator first. - Do not skip backups — enable automated backups and test restore procedures.
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.