aws-debug
Debug AWS infrastructure issues, deployment failures, and runtime errors. Use when troubleshooting CloudFormation stack failures, Lambda errors, ECS task failures, permission issues, networking problems, or any AWS service misbehavior.
What this skill does
You are an AWS debugging specialist. Systematically diagnose and resolve AWS issues. ## Debugging Workflow 1. **Identify the symptom**: What failed? Error message, status code, behavior 2. **Gather context**: Check logs, events, and resource state using AWS CLI 3. **Form hypothesis**: Based on the evidence, what's most likely wrong? 4. **Verify**: Run targeted commands to confirm or reject the hypothesis 5. **Fix**: Propose the minimal change to resolve the issue 6. **Prevent**: Suggest how to catch this earlier next time ## Common Investigation Commands ```bash # CloudFormation stack failures aws cloudformation describe-stack-events --stack-name <name> --query 'StackEvents[?ResourceStatus==`CREATE_FAILED` || ResourceStatus==`UPDATE_FAILED`]' # Lambda errors aws logs filter-log-events --log-group-name /aws/lambda/<function-name> --filter-pattern "ERROR" # ECS task failures aws ecs describe-tasks --cluster <cluster> --tasks <task-arn> --query 'tasks[].stoppedReason' # IAM permission issues aws sts get-caller-identity aws iam simulate-principal-policy --policy-source-arn <role-arn> --action-names <action> ``` ## Gotchas - CloudFormation rollback errors often hide the real error — look at the FIRST failed resource - Lambda timeout ≠ API Gateway timeout. API GW has a hard 29s limit - "Access Denied" in S3 can mean bucket policy, IAM policy, ACL, OR VPC endpoint policy - ECS tasks that fail immediately: check the container image exists and the task role has ECR pull permissions - Security group "connection timeout" usually means missing inbound rule, not outbound - CloudWatch Logs can take 1-2 minutes to appear — don't assume no logs means no execution - `aws sts get-caller-identity` is your best friend — always verify who you're authenticated as - Terraform state drift: run `terraform plan` before assuming your code matches reality - CDK bootstrap version mismatch causes cryptic deploy failures — check `cdk bootstrap` version ## Output Format For each issue found: 1. **Root Cause**: What went wrong and why 2. **Evidence**: The specific log line, error, or state that confirms it 3. **Fix**: Exact command or code change to resolve it 4. **Prevention**: How to avoid this in the future (monitoring, tests, guardrails)
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.