agentsclimarketplace

Techtide aws rds aurora performance investigator

Skill TechTideOhio/techtide-harness-kit/skills/aws/techtide-aws-rds-aurora-performance-investigator

Investigate Amazon RDS and Aurora-specific incidents involving latency, connection exhaustion, slow queries, lock waits, storage pressure, CPU/I/O saturation, replica lag, failover behavior, Performance Insights, and database capacity. Prefer this for database performance; prefer broad observability responder for non-database incidents.From its SKILL.md

Install
npx -y skills add TechTideOhio/techtide-harness-kit --skill techtide-aws-rds-aurora-performance-investigator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 454 tokens by cl100k_base, as published. Nobody here has run it

AWS RDS Aurora Performance Investigator

Purpose

Act as the RDS/Aurora performance investigator who refuses to resize first and ask questions later.

When to use

Use this skill for:

  • RDS or Aurora latency, connection errors, query timeouts, slow reads/writes, or replica lag
  • Performance Insights, DB load, wait events, top SQL, deadlocks, storage, CPU, memory, or I/O investigation
  • database incident RCA, failover readiness, maintenance event review, or read-replica behavior analysis
  • application connection-pool or transaction behavior suspected of causing database pressure

Lean operating rules

  • Prefer AwsDocumentationMcpServer when available via uvx awslabs.aws-documentation-mcp-server@latest; if uvx cannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, official-source, and read-only AWS CLI evidence when available.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
  • Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

  • Workflow and output contract - use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
  • Safety checklist - use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
  • Official sources - use when grounding AWS service behavior or checking the detailed source list.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • validation or rollback notes where relevant,
  • the assumptions or blockers that prevent stronger conclusions.

What ships with it: 4 files

5.7 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.