aws-modernize-workshop-db
Comprehensive AWS database modernization workshop: SQL Server → RDS → PostgreSQL → DynamoDB with AI-assisted development using Amazon Q Developer. Achieve X% cost reduction through progressive 3-phase migration.
Install / Use
npx skills add kuettai/aws-modernize-workshop-dbInstalls into whichever agent you are using.
Amazon Q Rules
Amazon Q Developer rules
Quality Score
Category
Data & AnalyticsSupported Platforms
Our assessment of aws-modernize-workshop-db
aws-modernize-workshop-db scores 26/100 on our quality scale, 585th of 587 Data & Analytics skills we index.
Its Amazon Q Rules is 446 bytes long, written without headings and no code examples: very short, closer to a stub than a full skill.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-10-20 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
ReviewOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: Instructs the agent to automatically run `git add . && git commit ... && git push` after every interaction, removing user review before publishing changes.
AI review: risky
- Instructs the agent to automatically run `git add . && git commit ... && git push` after every interaction, removing user review before publishing changes.
- Uses `git add .` which stages all files indiscriminately, increasing risk of committing unintended or sensitive files.
- Hardcodes repository owner/name references, which is not malicious but could lead to incorrect repo-specific outputs.
AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
aws-modernize-workshop-db compared with similar skills
All 4 of these similar skills score higher than aws-modernize-workshop-db; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| aws-modernize-workshop-db (this skill)by kuettai | 26 | 0 | — | Amazon Q Rules |
| claude-memby thedotmack | 100 | 102.6k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 101.4k | today | CLAUDE.md |
| constraint-driven-developmentby addyosmani | 100 | 108.2k | 10d ago | SKILL.md |
| developer-growth-analysisby ComposioHQ | 100 | 77.4k | 35d ago | SKILL.md |
Frequently asked questions
- How do I install aws-modernize-workshop-db?
- Run
npx skills add kuettai/aws-modernize-workshop-db. The install tabs above show the steps for each supported agent. - Which AI agents does aws-modernize-workshop-db work with?
- It is written for Amazon Q, as a Amazon Q Rules file. Other agents that read the same format can often use it too.
- Is aws-modernize-workshop-db safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: Instructs the agent to automatically run
git add . && git commit ... && git pushafter every interaction, removing user review before publishing changes. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand. - Is aws-modernize-workshop-db still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubAlways run git add . && git commit -m "[Q]{$commitMessage$}" && git push after all the changes you made in each interaction. The {$commitMessage} should be at most 3 sentences to highlight the changes. The [Q] in the commit message indicate this is coming from Amazon Q
By any chance you require to output repo information, instead of using "youruser" and "yourrepo", the user should be "kuettai", the repo should be "aws-modernize-workshop-db"
Related Skills
claude-mem
102.6kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Agent-Reach
101.4kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
constraint-driven-development
108.2kEstablishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-i…
developer-growth-analysis
77.4kAnalyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.