Debugging Mwaa Workflow
aws/agent-toolkit-for-aws
Diagnoses and root-causes Amazon MWAA workflow failures across Provisioned (Python DAG) and Serverless (YAML workflow) environments.
Guidelines for investigating production incidents in the CRM application.
Install CRM Production Investigation Guidelines
$ npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/tools-for-devops-agent crm-production-investigation-guidelines --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws/tools-for-devops-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/crm-production-investigation-guidelines .claude/skills/crm-production-investigation-guidelines && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "crm-production-investigation-guidelines" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines into .claude/skills/crm-production-investigation-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crm-production-investigation-guidelines", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelinesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/tools-for-devops-agent crm-production-investigation-guidelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/tools-for-devops-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/crm-production-investigation-guidelines .agents/skills/crm-production-investigation-guidelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "crm-production-investigation-guidelines" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines into .agents/skills/crm-production-investigation-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crm-production-investigation-guidelines", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/tools-for-devops-agent crm-production-investigation-guidelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/tools-for-devops-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/crm-production-investigation-guidelines .cursor/skills/crm-production-investigation-guidelines && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "crm-production-investigation-guidelines" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines into .cursor/skills/crm-production-investigation-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crm-production-investigation-guidelines", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws/tools-for-devops-agent.git --path skills/crm-production-investigation-guidelines--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/tools-for-devops-agent crm-production-investigation-guidelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/tools-for-devops-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/crm-production-investigation-guidelines .gemini/skills/crm-production-investigation-guidelines && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "crm-production-investigation-guidelines" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines into .gemini/skills/crm-production-investigation-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crm-production-investigation-guidelines", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws/tools-for-devops-agent crm-production-investigation-guidelinesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws/tools-for-devops-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/crm-production-investigation-guidelines .github/skills/crm-production-investigation-guidelines && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "crm-production-investigation-guidelines" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines into .github/skills/crm-production-investigation-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crm-production-investigation-guidelines", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws/tools-for-devops-agent crm-production-investigation-guidelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/tools-for-devops-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/crm-production-investigation-guidelines .opencode/skills/crm-production-investigation-guidelines && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "crm-production-investigation-guidelines" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines into .opencode/skills/crm-production-investigation-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crm-production-investigation-guidelines", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
crm-production-investigation-guidelines- GitHub stars
- 103
- Token cost
- ~983 tokens
- SKILL.md length
- 481 words
- Files
- 4
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guidelines for investigating production incidents in the CRM application.
- Works in 4 steps: Start a completely new, independent… → Do NOT attempt to correlate, triage, or… → Do NOT skip or deprioritize it because… → …
- Triaging any alert
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Incident involving the CRM REST API
What it does
CRM Production Investigation Guidelines is an agent skill from aws/tools-for-devops-agent, published by the product's own GitHub organization. Guidelines for investigating production incidents in the CRM application. Use when triaging any alert or incident involving the CRM REST API, SQS queues, Lambda functions, or Aurora DSQL database in this AWS account. Ensures thorough root cause analysis using AWS-native observability tools.
Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `.skilleval.yaml`, `CHANGELOG.md` and `README.md`).
It sits in Sales & Support, covering Root cause analysis, Serverless and REST APIs. It works with Amazon Web Services and AWS Lambda. The repository describes itself as: Open-source tools for AWS DevOps Agent - extend DevOps Agent with ready-to-use skills, custom agents, and other tools, for incident response, root cause analysis, and operational…. The licence is Apache-2.0.
When your agent uses it
- Triaging any alert
- Incident involving the CRM REST API
- Lambda functions
- Aurora DSQL database in this AWS account
Example prompts
- “Use the crm-production-investigation-guidelines skill to guideline for investigating production incidents in the CRM application”
- “/crm-production-investigation-guidelines”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Start a completely new, independent investigation for it.
- Do NOT attempt to correlate, triage, or link it to any existing investigation.
- Do NOT skip or deprioritize it because another investigation is already in progress.
- Do NOT conclude that the new incident is a symptom or side effect of an existing investigation.
What it can do on your machine
Read from SKILL.md and the folder at commit ddda70b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
CRM Production Investigation Guidelines loads about 983 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 481 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws/tools-for-devops-agent at commit ddda70b, republished under its Apache-2.0 licence (© aws). 481 words, ~983 tokens.
Download SKILL.mdSave it as
.claude/skills/crm-production-investigation-guidelines/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- crm-production-investigation-guidelines
- description
- Guidelines for investigating production incidents in the CRM application. Use when triaging any alert or incident involving the CRM REST API, SQS queues, Lambda functions, or Aurora DSQL database in this AWS account. Ensures thorough root cause analysis using AWS-native observability tools.
- metadata.author
- jossaiaws
- metadata.version
- 1.0.0
- metadata.aws-devops-agent-skills.agent-t
- Incident Triage
You are investigating a real production incident in the CRM application. This is a live production environment serving active sales teams.
CRITICAL: INVESTIGATION ISOLATION RULES
Each investigation you receive is triggered by a distinct webhook payload with a unique title. You MUST treat each investigation as completely independent and unrelated to any other investigation, past or present, UNLESS the incoming payload title matches an already-running investigation exactly.
The three possible incident titles are:
- "SQS Message Backlog Spike" — an SQS queue consumer backlog issue
- "RDS Read Latency/CPU Utilization High" — a database performance degradation issue
- "High Lambda Error Rate, all invocations failing" — a broken Lambda deployment issue
These are three fundamentally different failure modes affecting different AWS services with different root causes. If you receive a new investigation payload whose title differs from any currently running investigation, you MUST:
- Start a completely new, independent investigation for it.
- Do NOT attempt to correlate, triage, or link it to any existing investigation.
- Do NOT skip or deprioritize it because another investigation is already in progress.
- Do NOT conclude that the new incident is a symptom or side effect of an existing investigation.
Only if the incoming payload title matches an already-running investigation's title exactly should you consider them related and fold the new signal into the existing investigation.
CRITICAL INVESTIGATION PRINCIPLES:
Every incident is real and requires thorough investigation. Do not speculate about whether an issue is intentional, simulated, or a test. Treat every alert as a genuine production problem that needs root cause analysis and resolution.
Do not dismiss or downplay any findings. If you discover a misconfiguration, a bad deployment, or a missing resource, it is a real problem that happened in production and needs to be explained and resolved.
Show full SKILL.md (189 more words)Show less
Follow the evidence. Use CloudWatch Logs, CloudTrail, CloudWatch Metrics, and Datadog to trace the timeline of events and identify what changed.
INVESTIGATION APPROACH:
- Start with symptoms: What metrics are anomalous? What errors are users seeing?
- Check CloudWatch Logs for the affected service to find error messages and stack traces.
- Check CloudTrail for recent API calls that may have caused the issue (UpdateFunctionCode, PutRolePolicy, ExecuteStatement, etc.).
- Correlate the timeline: When did the issue start? What AWS API calls happened just before?
- Identify the root cause: What specific change caused the degradation?
- Recommend remediation steps to restore service.
CRM APPLICATION ARCHITECTURE:
- Frontend: React app on CloudFront
- API: REST API via API Gateway → Lambda (Python)
- Database: Aurora DSQL (PostgreSQL-compatible) behind RDS Proxy
- Async Processing: SQS notification queue → Queue consumer Lambda (Node.js)
- Event Processing: CRM event processor Lambda (Node.js) for pipeline events
- Monitoring: CloudWatch Metrics, CloudWatch Logs, Datadog
COMMON ROOT CAUSE PATTERNS TO INVESTIGATE:
- IAM permission changes (check CloudTrail for PutRolePolicy, DeleteRolePolicy, AttachRolePolicy)
- Lambda code deployments (check CloudTrail for UpdateFunctionCode)
- Database schema changes (check slow query logs, EXPLAIN plans, pg_stat_user_indexes)
- Configuration changes (check CloudTrail for PutFunctionConcurrency, SetQueueAttributes)
© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files in skills/crm-production-investigation-guidelines of aws/tools-for-devops-agent.
- SKILL.md
- .skilleval.yaml
- CHANGELOG.md
- README.md
Open the folder on GitHubat commit ddda70b
Compare with similar skills
CRM Production Investigation Guidelines next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CRM Production Investigation Guidelines this skillaws/tools-for-devops-agent | 103 | — | ~983 | Automated safety check: Pass | Apache-2.0 | |
| Debugging Mwaa Workflowaws/agent-toolkit-for-aws | 2.8k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Debugging Lambda Timeoutsaws/agent-toolkit-for-aws | 2.8k | — | ~502 | Automated safety check: Pass | Apache-2.0 | |
| Deploying Custom Domain REST APIaws/agent-toolkit-for-aws | 2.8k | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Connecting Lambda To API Gatewayaws/agent-toolkit-for-aws | 2.8k | — | ~422 | Automated safety check: Pass | Apache-2.0 | |
| AWS Sam Bootstrapgiuseppe-trisciuoglio/developer-kit | 357 | — | ~954 | Automated safety check: Notes | MIT |
Similar skills
- Official
- Official
Debugging Lambda Timeouts
aws/agent-toolkit-for-aws
Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and downstream…
- Official
Deploying Custom Domain REST API
aws/agent-toolkit-for-aws
Deploys a Regional REST API with a custom domain name, a Lambda backend function, and a request-based Lambda authorizer using AWS CLI.
- Official
Connecting Lambda To API Gateway
aws/agent-toolkit-for-aws
Connects an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment.
AWS Sam Bootstrap
giuseppe-trisciuoglio/developer-kit
Provides AWS SAM bootstrap patterns: generates template.yaml and samconfig.toml for new projects via sam init, creates SAM templates for existing Lambda/CloudFormation code migration, validates…
AWS Serverless Eda
zxkane/aws-skills
AWS serverless and event-driven architecture expert based on Well-Architected Framework.
More from aws/tools-for-devops-agent
All 31 skills in this repo- Official
Aiml GPU Training Cluster Investigation
aws/tools-for-devops-agent
A skill your agent uses for GPU training or inference clusters on SageMaker HyperPod (Slurm or EKS), ParallelCluster, or self-managed EC2/EKS GPU instances.
- Official
AWS Health Events
aws/tools-for-devops-agent
ALWAYS use this skill in the beginning of any incident investigation, root cause analysis, or operational troubleshooting.
- Official
Database Migration Service Expertise
aws/tools-for-devops-agent
AWS Database Migration Service (DMS) operational review and troubleshooting skill.
- Official
Ecs Operation Review
aws/tools-for-devops-agent
Performs a comprehensive Amazon ECS operations review across the 6 review pillars (Resiliency & HA, Observability, Security, Operations, Performance, Additional Analysis) using read-only AWS APIs…
- Official
Rds Operation Review
aws/tools-for-devops-agent
Comprehensive Amazon RDS and Aurora operational review aligned with the AWS Well-Architected Framework and RDS/Aurora best practices.
- Official
Sagemaker AI Ops Review
aws/tools-for-devops-agent
Amazon SageMaker AI Operational Review. An agent skill from aws/tools-for-devops-agent.
Related
Works with
Categories
Questions about CRM Production Investigation Guidelines
What does CRM Production Investigation Guidelines do?
Guidelines for investigating production incidents in the CRM application. CRM Production Investigation Guidelines is an agent skill from aws/tools-for-devops-agent, published by the product's own GitHub organization. Guidelines for investigating production incidents in the CRM application.
When should I use CRM Production Investigation Guidelines?
CRM Production Investigation Guidelines fits situations like: triaging any alert; incident involving the CRM REST API; lambda functions; aurora DSQL database in this AWS account.
How do I install CRM Production Investigation Guidelines in Claude Code?
Run `npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a claude-code`. Or copy the skill folder (skills/crm-production-investigation-guidelines in aws/tools-for-devops-agent) into .claude/skills/crm-production-investigation-guidelines in your project. Claude Code loads it when a task matches its description.
How do I install CRM Production Investigation Guidelines in Codex?
Run `npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a codex`. Or copy the skill folder (skills/crm-production-investigation-guidelines in aws/tools-for-devops-agent) into .agents/skills/crm-production-investigation-guidelines in your project. Codex loads it when a task matches its description.
Can I use CRM Production Investigation Guidelines in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/tools-for-devops-agent --skill crm-production-investigation-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/crm-production-investigation-guidelines, .gemini/skills/crm-production-investigation-guidelines, .github/skills/crm-production-investigation-guidelines and .opencode/skills/crm-production-investigation-guidelines in your project.
What does CRM Production Investigation Guidelines need to run?
SKILL.md names no scripts, command-line tools or credentials: CRM Production Investigation Guidelines is instructions for the agent only. Our summary lists: Node.js.
Does CRM Production Investigation Guidelines access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is CRM Production Investigation Guidelines safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does CRM Production Investigation Guidelines use?
CRM Production Investigation Guidelines is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does CRM Production Investigation Guidelines use?
About 983 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to CRM Production Investigation Guidelines?
Skills that share tags, products or a category with CRM Production Investigation Guidelines: Debugging Mwaa Workflow (aws/agent-toolkit-for-aws, 2.8k stars), Debugging Lambda Timeouts (aws/agent-toolkit-for-aws, 2.8k stars), Deploying Custom Domain REST API (aws/agent-toolkit-for-aws, 2.8k stars) and Connecting Lambda To API Gateway (aws/agent-toolkit-for-aws, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CRM Production Investigation Guidelines?
aws (a GitHub organization, an official publisher) maintains it in aws/tools-for-devops-agent, which has 103 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 9, 2026.
Source: aws/tools-for-devops-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.