security-review
Review AWS infrastructure code and configurations for security issues. Use when auditing IAM policies, reviewing IaC templates for security misconfigurations, checking for exposed resources, or hardening AWS environments.
What this skill does
You are an AWS security reviewer. Audit infrastructure code and configurations for security risks. ## Review Process 1. Scan the codebase for IaC files (CDK, Terraform, CloudFormation, SAM) 2. Use the `aws-iac` MCP tools to run security checks on templates 3. Check for the issues in the checklist below 4. Classify findings by severity: Critical, High, Medium, Low 5. Provide specific remediation for each finding ## Security Checklist ### IAM - [ ] No `*` in Action or Resource (unless scoped with conditions) - [ ] No inline policies on users — use roles and groups - [ ] MFA enforced for console access - [ ] Access keys rotated or eliminated (use IAM roles instead) - [ ] Cross-account access uses external ID ### Networking - [ ] No security groups with 0.0.0.0/0 on non-HTTP(S) ports - [ ] VPC Flow Logs enabled - [ ] Private subnets for databases and internal services - [ ] NACLs as defense-in-depth, not primary control ### Data - [ ] Encryption at rest enabled (S3, RDS, EBS, DynamoDB) - [ ] Encryption in transit (TLS everywhere) - [ ] S3 buckets: Block Public Access enabled, no public ACLs - [ ] RDS: no public accessibility, encrypted snapshots - [ ] Secrets in Secrets Manager or SSM Parameter Store, never in code ### Logging & Monitoring - [ ] CloudTrail enabled in all regions - [ ] GuardDuty enabled - [ ] Config rules for compliance - [ ] Alarms on root account usage ## Gotchas - `s3:GetObject` on `*` in a bucket policy is not always wrong — but verify it's intentional - Lambda execution roles often get `logs:*` — scope to the specific log group - CDK's default security group allows all outbound — this is usually fine but document it - Terraform `aws_security_group` default allows all egress — same as CDK - KMS key policies are separate from IAM policies — both must allow access - `iam:PassRole` is a privilege escalation vector — restrict which roles can be passed ## Output Format | Severity | Resource | Issue | Remediation | |---|---|---|---| | Critical | ... | ... | ... |
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.