joao-aires/agent-skills-public/postgresql-operations
Claude Code and agent skill by joao-aires/agent-skills-public
- community
Checking that the SKILL.md file is still in the repository.
Plan or perform scoped PostgreSQL backup/recovery, maintenance, replication
Install
npx vskill@latest install joao-aires/agent-skills-public/postgresql-operationsSKILL.md
The same SKILL.md was published earlier as joao-aires/agent-skills-public/postgresql-operations.
Operate PostgreSQL with a verified recovery path
Identify the authorized cluster/database, version, hosting model, topology and operating commitments. Reuse accepted recovery objectives and procedures. Read sources for version-specific PostgreSQL and reviewed upstream material. Managed-service controls differ from self-hosted server access; do not invent superuser, filesystem or control-plane capabilities.
Establish recoverability
Begin with what must be recovered: one record set, one database, or the cluster and its supporting state. Establish the acceptable recovery point and time, then choose a backup and restoration approach that can meet them in the actual hosting environment. Logical backup, physical backup/WAL recovery and managed snapshots/PITR serve different recovery units and operating constraints; a combination may be needed.
Check the complete restore path, including access to the backup, compatible tools, required roles/extensions and the configuration needed to start the recovered system. A backup that cannot be restored within the available access and time does not meet the operating requirement.
- Include roles/global objects, extensions, encryption/access, dependencies and recovery configuration.
- A replica shares many failure and deletion modes and is not an independent backup.
- Continuous recovery depends on a usable base and the required WAL chain; monitor retention and restoreability, not just successful job completion.
Exercise recovery on an authorized isolated target. Verify a known recovery point, application compatibility, representative records/invariants and access, then measure actual recovery time and attainable data loss. Keep restored deletion/retention obligations and traffic cutover explicit.
| Evidence | Claim supported | |
|---|---|---|
| Documented procedure | A recovery approach is described. | |
| Successful backup | The backup operation completed. | |
| Successful restore | The restoration was exercised. |
None automatically establishes full application recovery.
Maintain health without hiding risk
Assess connections, long transactions, disk/WAL growth, vacuum/freeze, replication slots and lag against workload and retention.
- Slots can retain WAL; replicas can lag or conflict with recovery.
- Investigate cause and consequences before dropping slots, cancelling work or changing durability.
- Define primary/failover authority and fencing against split-brain; promotion alone does not prove clients moved or application writes are correct.
When upgrading
For minor/major upgrades, check supported server/extension/driver combinations, storage needs and tooling.
- Compare in-place, logical replication or dump/restore strategies against downtime and reversibility. Read major upgrades for the compatibility inventory,
pg_upgradechoices, rehearsal and cutover on infrastructure you control. - On a managed service, read managed upgrades for provider prechecks, clones, extension allowlists, replica handling and restore-based rollback.
- Rehearse meaningful data and query/role compatibility, validate the new target, and define cutover, stale-writer prevention and forward recovery.
- There is no in-place downgrade; avoid claiming binary rollback after new writes unless that path is demonstrated.
Execute and report within scope
Use the named target and supported operational tooling. Confirm impact, resource/traffic boundaries and recovery route before consequential live work; existing authorization remains valid. Continue independent planning when access is unavailable. Protect backups and reports from secrets/personal-data exposure, retire temporary restored targets only within authorized cleanup, and report actual actions, evidence, remaining risks and operating ownership.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/database-postgresql-development/skills/postgresql-operations/SKILL.md
Popularity
- Repository stars
- 2
- Repository forks
- 1
- 7-day trend score
- 0
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/joao-aires/agent-skills-public/postgresql-operations)