Flux Recon
jeremylongshore/tons-of-skills-marketplace
Database reconnaissance — full inventory of schema, migrations, data volume, backups, connection pooling, and query patterns.
AWS Database Migration Service (DMS) operational review and troubleshooting skill.
Install Database Migration Service Expertise
$ npx skills add aws/tools-for-devops-agent --skill database-migration-service-expertise -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/tools-for-devops-agent database-migration-service-expertise --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/database-migration-service-expertise .claude/skills/database-migration-service-expertise && 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 "database-migration-service-expertise" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/database-migration-service-expertise into .claude/skills/database-migration-service-expertise/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration-service-expertise", 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/database-migration-service-expertiseType 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 database-migration-service-expertise -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/tools-for-devops-agent database-migration-service-expertise --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/database-migration-service-expertise .agents/skills/database-migration-service-expertise && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "database-migration-service-expertise" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/database-migration-service-expertise into .agents/skills/database-migration-service-expertise/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration-service-expertise", 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 database-migration-service-expertise -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/tools-for-devops-agent database-migration-service-expertise --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/database-migration-service-expertise .cursor/skills/database-migration-service-expertise && 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 "database-migration-service-expertise" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/database-migration-service-expertise into .cursor/skills/database-migration-service-expertise/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration-service-expertise", 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/database-migration-service-expertise--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 database-migration-service-expertise -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/tools-for-devops-agent database-migration-service-expertise --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/database-migration-service-expertise .gemini/skills/database-migration-service-expertise && 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 "database-migration-service-expertise" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/database-migration-service-expertise into .gemini/skills/database-migration-service-expertise/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration-service-expertise", 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 database-migration-service-expertiseInstalls 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 database-migration-service-expertise -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/database-migration-service-expertise .github/skills/database-migration-service-expertise && 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 "database-migration-service-expertise" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/database-migration-service-expertise into .github/skills/database-migration-service-expertise/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration-service-expertise", 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 database-migration-service-expertise -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 database-migration-service-expertise --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/database-migration-service-expertise .opencode/skills/database-migration-service-expertise && 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 "database-migration-service-expertise" agent skill from https://github.com/aws/tools-for-devops-agent/tree/main/skills/database-migration-service-expertise into .opencode/skills/database-migration-service-expertise/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "database-migration-service-expertise", 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
database-migration-service-expertise- GitHub stars
- 100
- Token cost
- ~3.4k tokens
- SKILL.md length
- 1,307 words
- Files
- 13 (incl. references)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
AWS Database Migration Service (DMS) operational review and troubleshooting skill.
- Works in 7 steps: Identify Target Resources → Collect DMS Configuration → Collect Observability Data (7-Day… → …
- Requests like DMS review
- SKILL.md covers When to Use, Step 1: Identify Target…, Step 2: Collect DMS… and Step 3: Collect Observability…, plus 3 more sections
- Calls aws
What it does
Database Migration Service Expertise is an agent skill from aws/tools-for-devops-agent, published by the product's own GitHub organization. AWS Database Migration Service (DMS) operational review and troubleshooting skill. Conducts best practices validation, health assessments, performance diagnostics, cost optimization reviews, and migration cutover guidance. Triggers on requests like "DMS review", "DMS health check", "DMS troubleshooting", "migration assessment", "DMS best practices audit", "DMS cost optimization", "replication instance review", "CDC latency issue", or "DMS task failure".
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including reference files (for example `.skilleval.yaml`, `CHANGELOG.md` and `README.md`).
It sits in Databases, covering Database migrations, Messaging and chat bots and Database administration. It works with Amazon Web Services. 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
- Requests like DMS review
- DMS health check
- DMS troubleshooting
- Migration assessment
Example prompts
- “DMS review”
- “DMS health check”
- “DMS troubleshooting”
- “/database-migration-service-expertise”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
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
Shell commands in SKILL.md call:
aws
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.
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
Database Migration Service Expertise loads about 3.4k tokens when it runs, and up to ~23k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 1,307 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). 1,307 words, ~3,381 tokens.
Download SKILL.mdSave it as
.claude/skills/database-migration-service-expertise/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.- name
- database-migration-service-expertise
- description
- AWS Database Migration Service (DMS) operational review and troubleshooting skill. Conducts best practices validation, health assessments, performance diagnostics, cost optimization reviews, and migration cutover guidance. Triggers on requests like "DMS review", "DMS health check", "DMS troubleshooting", "migration assessment", "DMS best practices audit", "DMS cost optimization", "replication instance review", "CDC latency issue", or "DMS task failure".
- metadata.author
- tabhiman
- metadata.version
- 1.0.0
- metadata.aws-devops-agent-skills.agent-t
- Chat tasks, Evaluation
- metadata.aws-devops-agent-skills.aws-ser
- AWS Database Migration Service
- metadata.aws-devops-agent-skills.technic
- Database
AWS DMS Operational Review & Troubleshooting
Conduct comprehensive operational reviews, best practices validation, troubleshooting, and cost optimization assessments for AWS Database Migration Service (DMS) environments aligned with AWS Well-Architected principles.
When to Use
Activate this skill when the user asks to:
- Review, audit, or assess DMS configurations
- Check DMS best practices compliance
- Troubleshoot DMS task failures, latency, or connectivity issues
- Evaluate DMS cost optimization opportunities
- Plan or execute a database migration cutover
- Assess DMS version deprecations and upgrade paths
- Run a pre-migration assessment
- Evaluate DMS Serverless vs provisioned suitability
- Investigate data validation mismatches
- Review DMS homogeneous data migration options
Step 1: Identify Target Resources
Ask the user which DMS resources to review. Accept:
- Specific replication instance names and regions
- Specific replication task identifiers
- "all instances" in a specific region
- "all instances in all regions"
Query AWS APIs to discover DMS resources:
- List replication instances across the configured account regions
- List replication tasks and their states
- List endpoints and connectivity status
Step 2: Collect DMS Configuration
For EACH replication instance and its associated tasks, gather the following data using AWS APIs.
2.1 Replication Instance Config
Engine version, instance class, Multi-AZ, storage, public accessibility, KMS encryption, auto-upgrade, VPC/subnet configuration, pending maintenance actions.
aws dms describe-replication-instances --profile <profile> --region <region>
aws dms describe-pending-maintenance-actions --profile <profile> --region <region>2.2 Replication Tasks
Task identifiers, status, migration type, table mappings, task settings, CDC start positions, last failure messages, stop reasons, replication task statistics.
aws dms describe-replication-tasks --profile <profile> --region <region>2.3 Endpoints
Endpoint identifiers, types (source/target), engine names, SSL mode, connection status, Secrets Manager integration, security group configurations.
aws dms describe-endpoints --profile <profile> --region <region>
aws dms describe-connections --filter Name=endpoint-arn,Values=<endpoint-arn> --profile <profile> --region <region>2.4 Table Statistics
Per-table state, row counts, validation state, error rows, DDL counts.
aws dms describe-table-statistics --replication-task-arn <task-arn> --profile <profile> --region <region>2.5 DMS Serverless (if applicable)
Replication configs, serverless replications, DCU utilization.
aws dms describe-replication-configs --profile <profile> --region <region>
aws dms describe-replications --profile <profile> --region <region>2.6 Version and Deprecation Data
Available engine versions, pending maintenance actions, AWS Health events.
aws dms describe-orderable-replication-instances --query "OrderableReplicationInstances[*].EngineVersion" --profile <profile> --region <region>
aws health describe-events --filter '{"services":["DMS"],"eventTypeCategories":["scheduledChange"]}' --profile <profile> --region us-east-1Note: AWS Health API is a global service and must be called with
--region us-east-1regardless of where DMS resources are deployed.
Step 3: Collect Observability Data (7-Day Historical)
3.1 CloudWatch Metrics (7 days)
Replication Instance Metrics (namespace: AWS/DMS):
- CPUUtilization (Average, Maximum)
- FreeableMemory (Average, Minimum)
- SwapUsage (Average, Maximum)
- DiskQueueDepth (Average, Maximum)
- ReadIOPS / WriteIOPS (Average, Maximum)
- ReadLatency / WriteLatency (Average, Maximum)
- NetworkTransmitThroughput (Average)
- NetworkReceiveThroughput (Average)
Task Metrics (namespace: AWS/DMS):
- CDCLatencySource (Average, Maximum)
- CDCLatencyTarget (Average, Maximum)
- CDCIncomingChanges (Average, Maximum)
- CDCChangesMemorySource (Average, Maximum)
- CDCChangesDiskSource (Maximum)
- CDCChangesDiskTarget (Maximum)
- FullLoadThroughputBandwidthTarget (Average)
- FullLoadThroughputRowsTarget (Average)
DMS Serverless (namespace: AWS/DMS, if applicable):
- ServerlessTotalCapacityUnits (Average, Maximum)
3.2 CloudWatch Logs (7 days)
Query task logs for error patterns:
ERROR— general errors (count)- Network/connectivity errors (
Network error,Connection lost,timeout) - Memory/resource errors (
out of memory,OOM,swap) - CDC-specific errors (WAL, binlog, LogMiner patterns)
- Data/constraint errors (
truncation,constraint,duplicate key)
3.3 AWS Health Events
Query DMS scheduled changes and deprecation notices:
- Upcoming engine version deprecations
- Pending mandatory maintenance actions
- Certificate expirations
Step 4: Analyze Against Best Practices
Evaluate ALL collected data against these categories. Assign severity to every finding: CRITICAL, HIGH, MEDIUM, LOW, or INFO.
Reference: references/dms-best-practices.md for detailed best practices.
Reference: references/dms-validation-checklist.md for validation criteria and thresholds.
Reference: references/dms-version-reference.md for version lifecycle and known issues.
4.1 Instance Health (25 points)
- Instance status (must be "available")
- Engine version currency (EOL → CRITICAL; not on latest or latest-1 active version → HIGH)
- Instance class appropriate (CPU < 80%, Memory > 20% free)
- Multi-AZ for production CDC tasks
- Storage utilization (< 80%)
- Not publicly accessible
- KMS encryption enabled
- Auto minor version upgrade enabled (non-prod)
4.2 Task Health (25 points)
- Task status (running/stopped, not failed/error)
- No tables in error/suspended state
- Logging enabled on all tasks
- CDC latency within thresholds (< 120s)
- Recovery checkpoint exists
- No full load error rows
- Task settings follow best practices (LOB mode, parallelism, batch apply)
4.3 Endpoint Security (20 points)
- SSL/TLS enabled on all endpoints (SslMode != "none")
- Secrets Manager integration for credentials
- Connection tests passing
- Security groups restrict access (no 0.0.0.0/0)
- VPC endpoints configured for AWS services
- Private subnet placement (not publicly accessible)
4.4 Performance (15 points)
- CPU utilization within thresholds (< 80% avg)
- Freeable memory adequate (> 2 GB minimum)
- No swap usage (SwapUsage = 0)
- Disk queue depth normal (< 10)
- No sustained disk-based CDC caching (CDCChangesDisk* = 0)
- CDC throughput adequate for workload
4.5 Cost Efficiency (15 points)
- No over-provisioned instances (CPU avg > 20% for 7+ days)
- No idle instances (no running tasks for 7+ days)
- Multi-AZ justified (production/critical only)
- Debug logging disabled in production
- Same-engine migrations using homogeneous/native tools where applicable
- DMS Serverless evaluated for variable workloads
Step 5: Troubleshooting (When Applicable)
When the user reports an active issue, follow this structured approach:
Phase 0: Version Check (Always First)
Check DMS engine version and cross-reference with references/dms-version-reference.md for known bugs.
Phase 1: Error Classification
Route by error category:
| Error Pattern | Category | Diagnostic Path |
|---|---|---|
| Network error, Connection lost, timeout | Connectivity | Network diagnostics |
| Memory, OOM, swap, disk full | Resource Exhaustion | Instance metrics |
| CDCLatency, falling behind | Performance/Latency | CDC metrics analysis |
| Data truncation, type mismatch | Data Mismatch | Table statistics |
| Table error, suspended, DDL | Table-Level Failure | Table reload |
| Credential, authentication, access denied | Auth/Permissions | Endpoint test |
| SSL, certificate, handshake | SSL/TLS | Certificate check |
| Task stops without clear error | Silent Failure | Comprehensive check |
Show full SKILL.md (503 more words)Show less
Phase 2: Targeted Diagnostics
Follow the appropriate diagnostic path using AWS CLI commands to gather evidence.
Phase 3: Log Analysis
Query CloudWatch Logs with engine-specific filter patterns (Oracle/PostgreSQL/MySQL/SQL Server).
Step 6: Migration Cutover Guidance (When Applicable)
When the user is planning or executing a cutover:
Pre-Cutover Checklist (T-7 to T-1 days)
- CDC latency at zero
- No tables in error
- Validation passing
- No pending maintenance
- Instance resources healthy
- Recovery checkpoint exists
- Target schema matches source
- Application connection strings prepared
- Rollback plan documented
Cutover Execution (T-0)
- Final latency check
- Stop application writes to source
- Wait for CDC to drain (zero latency)
- Run final validation
- Stop DMS task
- Switch application to target
- Validate application
- Monitor (T+0 to T+24h)
Rollback Procedure
Documented steps to revert to source if cutover fails.
Post-Cutover Cleanup (T+3 to T+7 days)
Resource deletion and documentation updates.
Step 7: Generate Report
Generate a separate shareable report artifact for EACH environment reviewed.
Artifact naming: dms-review-<instance-name>-<YYYY-MM-DD>.md
Example: dms-review-prod-replication-2026-07-22.md
For each environment, create the artifact as a Markdown document with these sections:
Report Header
# DMS Operational Review — <instance-name>
Account: <account-id> | Region: <region> | Date: <YYYY-MM-DD> | Engine Version: <version>Executive Summary
- Environment health: ✅ HEALTHY / ⚠️ WARNINGS / ❌ CRITICAL
- Health Score: XX/100 [Rating]
- Finding counts by severity
- Top 3 critical/high items
Health Score Breakdown
| Category | Score | Key Issues |
|---|---|---|
| Instance Health | XX/25 | [list issues] |
| Task Health | XX/25 | [list issues] |
| Endpoint Security | XX/20 | [list issues] |
| Performance | XX/15 | [list issues] |
| Cost Efficiency | XX/15 | [list issues] |
Resource Inventory
| Resource Type | Count | Status Summary |
|---|
Findings by Category
For each of the 5 categories above, present:
| # | Finding | Severity | Current State | Recommendation |
|---|
CloudWatch Metrics (7-Day)
| Metric | Category | 7-Day Avg | 7-Day Max | Status | Finding |
|---|
CloudWatch Logs Analysis (7-Day)
| Pattern | Occurrences | Severity | Finding |
|---|
Version & Deprecation Status
All instances with version, EOL status, upgrade recommendations.
Cost Optimization Opportunities
| # | Opportunity | Resource | Estimated Savings | Risk Level |
|---|
Priority Matrix
| # | Finding | Severity | Category | Effort | Impact |
|---|---|---|---|---|---|
| All findings sorted by severity. |
Next Steps
- Immediate (CRITICAL/HIGH — 7 days)
- Short-term (MEDIUM — 30 days)
- Long-term (LOW — 90 days)
Appendix
Refer to the AWS DMS documentation for detailed guidance on best practices, monitoring, troubleshooting, release notes, serverless, and data validation.
Severity Definitions
| Severity | Definition | SLA |
|---|---|---|
| CRITICAL | Immediate risk to migration integrity, data loss, or security breach | Fix within 24-48 hours |
| HIGH | Significant gap that could lead to task failures or data issues | Fix within 1 week |
| MEDIUM | Notable improvement opportunity for performance or cost | Plan within 30 days |
| LOW | Minor optimization or hardening | Address when convenient |
| INFO | Observation, no action required | N/A |
Health Score Formula
Scoring Categories (100 points total)
| Category | Weight | Scope |
|---|---|---|
| Instance Health | 25 pts | Status, version, Multi-AZ, public access, storage, encryption |
| Task Health | 25 pts | Task status, table errors, CDC latency, logging |
| Endpoint Security | 20 pts | SSL mode, Secrets Manager, connectivity, SG rules |
| Performance | 15 pts | CPU, memory, swap, disk queue, CDC throughput |
| Cost Efficiency | 15 pts | Right-sizing, idle resources, Multi-AZ justification |
Score Interpretation
| Score | Rating | Action |
|---|---|---|
| 90-100 | 🟢 Excellent | Minor optimizations only |
| 75-89 | 🟡 Good | Address warnings at next opportunity |
| 60-74 | 🟠 Needs Attention | Plan remediation within 1-2 weeks |
| 40-59 | 🔴 Poor | Immediate action required on critical items |
| 0-39 | ⚫ Critical | Migration at risk — escalate immediately |
© 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 12 other files (references) in skills/database-migration-service-expertise of aws/tools-for-devops-agent.
- SKILL.md
- .skilleval.yaml
- CHANGELOG.md
- README.md
- evals/benchmark.json
- evals/eval_queries.json
- evals/evals.json
- evals/files/dms-context.json
- evals/report.json
- evals/trigger_report.json
- references/dms-best-practices.md
- references/dms-validation-checklist.md
- references/dms-version-reference.md
Open the folder on GitHubat commit ddda70b
Compare with similar skills
Database Migration Service Expertise 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 |
|---|---|---|---|---|---|---|
| Database Migration Service Expertise this skillaws/tools-for-devops-agent | 100 | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Flux Reconjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~916 | Automated safety check: Notes | MIT | |
| MySQL Schema and Query Tuningplanetscale/database-skills | 705 | 3 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Neon Postgressmontlouis/bible-strong | 171 | 1 repos | ~2.3k | Automated safety check: Notes | GPL-3.0 | |
| Neon Postgresusenotra/notra | 256 | — | ~4.1k | Automated safety check: Notes | AGPL-3.0 | |
| Neon Postgresneondatabase/agent-skills | 100 | — | ~4.1k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
MySQL Schema and Query Tuning
planetscale/database-skills
Guides safe, measurable MySQL and InnoDB changes across schema design, indexing, query tuning, transactions, locking and replication, with rollout steps.
Neon Postgres
smontlouis/bible-strong
Guides and best practices for working with Lakebase Postgres, the database behind Neon.
Neon Postgres
usenotra/notra
Guides and best practices for working with Lakebase Postgres, the database behind Neon.
- Official
Neon Postgres
neondatabase/agent-skills
Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero, instant restore, read replicas, IP…
Kotlin Exposed Patterns
affaan-m/ECC
JetBrains Exposed ORM patterns including DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern.
More from aws/tools-for-devops-agent
All 31 skills in this repo- Official
Sagemaker AI Ops Review
aws/tools-for-devops-agent
Amazon SageMaker AI Operational Review. An agent skill from aws/tools-for-devops-agent.
- 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
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
Service Quota Check
aws/tools-for-devops-agent
Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits.
Related
Works with
Categories
Questions about Database Migration Service Expertise
What does Database Migration Service Expertise do?
AWS Database Migration Service (DMS) operational review and troubleshooting skill. Database Migration Service Expertise is an agent skill from aws/tools-for-devops-agent, published by the product's own GitHub organization. AWS Database Migration Service (DMS) operational review and troubleshooting skill.
When should I use Database Migration Service Expertise?
Database Migration Service Expertise fits situations like: requests like DMS review; DMS health check; DMS troubleshooting; migration assessment.
How do I install Database Migration Service Expertise in Claude Code?
Run `npx skills add aws/tools-for-devops-agent --skill database-migration-service-expertise -a claude-code`. Or copy the skill folder (skills/database-migration-service-expertise in aws/tools-for-devops-agent) into .claude/skills/database-migration-service-expertise in your project. Claude Code loads it when a task matches its description.
How do I install Database Migration Service Expertise in Codex?
Run `npx skills add aws/tools-for-devops-agent --skill database-migration-service-expertise -a codex`. Or copy the skill folder (skills/database-migration-service-expertise in aws/tools-for-devops-agent) into .agents/skills/database-migration-service-expertise in your project. Codex loads it when a task matches its description.
Can I use Database Migration Service Expertise 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 database-migration-service-expertise -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/database-migration-service-expertise, .gemini/skills/database-migration-service-expertise, .github/skills/database-migration-service-expertise and .opencode/skills/database-migration-service-expertise in your project.
What does Database Migration Service Expertise need to run?
Going by SKILL.md and its folder, Database Migration Service Expertise needs the command-line tools its instructions call (aws).
Does Database Migration Service Expertise 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 Database Migration Service Expertise 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 Database Migration Service Expertise use?
Database Migration Service Expertise 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 Database Migration Service Expertise use?
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 19k tokens, read only when the agent opens those files.
What are the alternatives to Database Migration Service Expertise?
Skills that share tags, products or a category with Database Migration Service Expertise: Flux Recon (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), MySQL Schema and Query Tuning (planetscale/database-skills, 705 stars), Neon Postgres (smontlouis/bible-strong, 171 stars) and Neon Postgres (usenotra/notra, 256 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Database Migration Service Expertise?
aws (a GitHub organization, an official publisher) maintains it in aws/tools-for-devops-agent, which has 100 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 8, 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.