aws-diagram
Generate AWS architecture diagrams in Mermaid or ASCII from a description, existing IaC, or conversation context. Use when the user wants to visualize an architecture.
What this skill does
You are generating an AWS architecture diagram. Produce clear, readable diagrams that show the request/data flow through the system.
## Process
1. Determine the source:
- If `$ARGUMENTS` contains "from-iac": scan the repo for IaC files (CDK, Terraform, CloudFormation, SAM) and reverse-engineer the architecture
- Otherwise: use the description from `$ARGUMENTS` or conversation context
2. Generate a Mermaid diagram (primary) and an ASCII fallback
3. Include a legend for any non-obvious notation
## Mermaid Diagram Style
Use `graph LR` (left-to-right) for request flows, `graph TD` (top-down) for hierarchical architectures.
### Conventions
- **Users/Clients**: Stadium shape `([User])`
- **AWS Services**: Rectangle `[Service Name]`
- **Databases**: Cylinder `[(Database)]`
- **Queues**: Parallelogram `[/Queue/]`
- **External Services**: Double-bordered `[[External API]]`
- **Subgraphs**: Group by VPC, subnet, or logical boundary
- **Arrows**: Label with protocol/action (e.g., `-->|HTTPS|`, `-->|async|`)
### Example
```mermaid
graph LR
User([User]) -->|HTTPS| CF[CloudFront]
CF -->|HTTPS| ALB[ALB]
subgraph VPC
subgraph Public Subnet
ALB
end
subgraph Private Subnet
ECS[ECS Fargate]
ECS -->|TCP 5432| RDS[(Aurora PostgreSQL)]
ECS -->|TCP 6379| Redis[(ElastiCache Redis)]
end
end
ECS -->|HTTPS| S3[S3 Bucket]
ECS -->|SQS| Queue[/Processing Queue/]
Queue --> Lambda[Lambda Processor]
Lambda --> S3
```
## ASCII Fallback
For environments that don't render Mermaid:
```
┌──────┐ ┌────────────┐ ┌─────┐
│ User │────>│ CloudFront │────>│ ALB │
└──────┘ └────────────┘ └──┬──┘
│
┌──────────────┴──────────────┐
│ VPC │
│ ┌─────────────┐ │
│ │ ECS Fargate │──> Aurora │
│ │ │──> Redis │
│ └──────┬──────┘ │
└─────────┼────────────────────┘
│
┌────┴────┐
│ SQS │──> Lambda ──> S3
└─────────┘
```
## From IaC Reverse Engineering
When `from-iac` is specified:
1. Glob for `*.tf`, `*.ts` (CDK), `template.yaml` (SAM), `*.template.json` (CFN)
2. Extract resources, their relationships, and networking config
3. Map to diagram nodes and edges
4. Highlight any security concerns (public subnets, open SGs) with a warning marker
## Output
Always provide:
1. **Mermaid diagram** (in a ```mermaid code block)
2. **ASCII fallback** (in a ``` code block)
3. **Flow description** (1-2 sentences explaining the request/data path)
4. **Notes** (any assumptions made, security observations)
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.