Crm Production Investigation Guidelines

Organization

aws

crm-production-investigation-guidelines

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.

Overview

Publisher	aws
Repository	`tools-for-devops-agent`
Skill name	`crm-production-investigation-guidelines`
Stars	120
Forks	97
Bundled files	1
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by aws on GitHub. Read the source before you install it.

Installation

Install the Crm Production Investigation Guidelines AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/aws/tools-for-devops-agent.git /tmp/tools-for-devops-agent
mkdir -p .claude/skills
cp -r /tmp/tools-for-devops-agent/skills/crm-production-investigation-guidelines .claude/skills/crm-production-investigation-guidelines

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Crm Production Investigation Guidelines in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Crm Production Investigation Guidelines on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Crm Production Investigation Guidelines is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

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)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

CHANGELOG.md1 KB

Frequently asked questions

What does the Crm Production Investigation Guidelines AI skill do?

Why use Crm Production Investigation Guidelines on TypingMind?

Because you install it once and use it with any model. Crm Production Investigation Guidelines is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Crm Production Investigation Guidelines in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/aws/tools-for-devops-agent/tree/main/skills/crm-production-investigation-guidelines. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Crm Production Investigation Guidelines?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Crm Production Investigation Guidelines?

As many as you like. As long as a model supports skills, you can use Crm Production Investigation Guidelines with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Crm Production Investigation Guidelines AI skill free?

Yes. It is published on GitHub by aws under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Modal

NousResearch

OrganizationPopular

Serverless GPU cloud for ML jobs and model APIs.

Huggingface Hub

HuggingFace hf CLI: search/download/upload models, datasets.

Pinecone

Managed vector DB for production RAG and search.

Qdrant

Vector search engine for production RAG systems.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now