Individual skill
amazon-aurora-postgresql
Amazon Aurora PostgreSQL — creates, modifies, and advises on Aurora PostgreSQL clusters specifically (PostgreSQL-compatible engine, Aurora serverless, express configuration, pgvector, Babelfish). Trigger for Aurora PostgreSQL cluster operations, express-configuration quick-start, ACU sizing, I/O-Optimized storage, commitment pricing, or PostgreSQL upgrade planning. For Aurora MySQL, use amazon-aurora-mysql instead. Contains safety guardrails, express-first routing, and response templates that override defaults.
skills/specialized-skills/database-skills/amazon-aurora-postgresql/SKILL.md
Source commit 1761e96813ebcbd43ed81d19e837219033f0afe5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,440
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- operations Derived category
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 19,471 bytesSKILL.mdcore · 19,471 bytesreferences/commitment-pricing-basics.mddoc · 5,564 bytesreferences/commitment-pricing-instructions.mddoc · 7,447 bytesreferences/commitment-pricing-mechanics.mddoc · 6,139 bytesreferences/commitment-pricing-scenarios.mddoc · 4,515 bytesreferences/commitment-pricing-skipped-cluster.mddoc · 4,165 bytesreferences/commitment-pricing-worked-examples.mddoc · 5,928 bytesreferences/create-instructions.mddoc · 7,441 bytesreferences/express-create-comparison.mddoc · 7,785 bytesreferences/express-create-connect-iam.mddoc · 2,912 bytesreferences/express-create-constraints.mddoc · 9,647 bytesreferences/express-create-documentation-links.mddoc · 3,895 bytesreferences/express-create-feature-overview.mddoc · 7,549 bytesreferences/express-create-instructions.mddoc · 7,936 bytesreferences/express-create-migration-pgdump.mddoc · 2,065 bytesreferences/express-create-migration.mddoc · 7,642 bytesreferences/express-create-use-cases.mddoc · 7,910 bytesreferences/io-optimized-data-collection.mddoc · 4,294 bytesreferences/io-optimized-instructions.mddoc · 7,085 bytesreferences/io-optimized-pricing-tables.mddoc · 6,481 bytesreferences/io-optimized-pricing.mddoc · 3,117 bytesreferences/io-optimized-worked-examples.mddoc · 4,660 bytesreferences/serverless-advisory-concepts.mddoc · 3,317 bytesreferences/serverless-advisory-formulas-and-examples.mddoc · 4,560 bytesreferences/serverless-advisory-instructions.mddoc · 7,212 bytesreferences/serverless-advisory-migration.mddoc · 7,115 bytesreferences/serverless-advisory-worked-examples.mddoc · 7,347 bytesreferences/shared-foundation-security-considerations.mddoc · 5,537 bytesreferences/upgrade-planning-documentation-links.mddoc · 2,169 bytesreferences/upgrade-planning-instructions.mddoc · 5,755 bytesreferences/upgrade-planning-lts-recommendation.mddoc · 4,970 bytesreferences/upgrade-planning-mode-b-discovery.mddoc · 4,982 bytesreferences/upgrade-planning-mode-b-prechecks-checklists.mddoc · 4,856 bytesreferences/upgrade-planning-post-checklist.mddoc · 2,978 bytesreferences/upgrade-planning-post-upgrade-detail.mddoc · 6,535 bytesreferences/upgrade-planning-post-upgrade-validation.mddoc · 4,314 bytesreferences/upgrade-planning-pre-checklist.mddoc · 2,280 bytesreferences/upgrade-planning-prechecks-postgresql.mddoc · 7,218 bytesreferences/upgrade-planning-query-load-postgresql.mddoc · 6,754 bytesscripts/acu_calculator.pyruns · 36,644 bytesscripts/commitment_pricing_analyzer.pyruns · 33,313 bytesscripts/io_optimized_analyzer.pyruns · 26,419 bytes
Read excerpt
# Amazon Aurora PostgreSQL
A modular toolkit for **Aurora PostgreSQL** organized as a registry of sub-skills. Each sub-skill handles one domain of Aurora PostgreSQL work. The router matches user intent to the right sub-skill, then loads only the references needed. (For Aurora MySQL, use the `amazon-aurora-mysql` skill.)
## Operating procedure (follow in order)
1. **Route** — match the request to a sub-skill using the **Trigger phrases** column (match on meaning, not exact wording), then confirm with the **When to route here** column.
2. **Load** — `file_read` the matched sub-skill's `references/{id}-instructions.md` and announce the path. Do not answer a matched sub-skill from general knowledge alone.
3. **Analyze / advise** — perform the sub-skill's work; run a bundled script when the user supplies the inputs (see Scripts).
4. **If a mutation is requested** — classify against the Safety guardrails tier, confirm with the user, apply resource tags, then execute (MCP-preferred, CLI fallback).
5. **Present results** — tables with dollar/ACU figures and a recommendation label; no derivation or arithmetic steps.
Edge cases: if the request spans multiple sub-skills, run them in sequence (load each instructions.md in turn). If **no** sub-skill matches, answer directly from Aurora PostgreSQL knowledge. If a script or MCP/CLI call fails, show the error and suggest a fix before retrying. The numbered Global rules below are details that hang off these steps.