deploying-postgres-k8s

1 stars 2 forks
17
A

Deploys PostgreSQL on Kubernetes using the CloudNativePG operator with automated failover.Use when setting up PostgreSQL for production workloads, high availability, or local K8s development.Covers operator installation, cluster creation, connection secrets, and backup configuration.NOT when using managed Postgres (Neon, RDS, Cloud SQL) or simple Docker containers.

Also in: docker database

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install mjunaidca/mjs-agent-skills/deploying-postgres-k8s
skilz install mjunaidca/mjs-agent-skills/deploying-postgres-k8s --agent opencode
skilz install mjunaidca/mjs-agent-skills/deploying-postgres-k8s --agent codex
skilz install mjunaidca/mjs-agent-skills/deploying-postgres-k8s --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/mjunaidca/mjs-agent-skills
2. Copy the agent skill directory:
cp -r mjs-agent-skills/.claude/skills/deploying-postgres-k8s ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Stars
1
Forks
2
Type
Technical
Meta-Domain
cloud infrastructure
Primary Domain
kubernetes
Market Score
17

Agent Skill Grade

A
Score: 94/100 Click to see breakdown

Score Breakdown

Spec Compliance
12/15
PDA Architecture
25/30
Ease of Use
24/25
Writing Style
10/10
Utility
19/20
Modifiers: +4

Areas to Improve

  • Missing References Directory
  • No Complete Workflow Example
  • Limited Checklist Usage

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-24

Developer Feedback

I've been digging through PostgreSQL deployment patterns lately, and your approach to containerizing stateful databases on Kubernetes actually solves some of the messiness I've seen in production setups—curious how you're handling persistence across node failures without overcomplicating the configuration.

Links:

The TL;DR

You're at 94/100, solid A-grade territory. This is based on Anthropic's best practices for skill design. Your writing style is basically flawless (10/10), and your PDA architecture scores well at 25/30, but you're leaving a few points on the table with missing reference files and incomplete workflow examples.

What's Working Well

  • Writing clarity is chef's kiss — Pure imperative form throughout ("Deploy", "Connect", "Create"), zero marketing fluff. The technical density matches what Claude needs without overthinking it.
  • Your trigger phrases nail discoverability — CloudNativePG, Kubernetes, PostgreSQL, high availability, operator pattern. Someone looking for K8s database solutions will find this immediately.
  • Strong validation patterns — You've got kubectl wait, rollout status checks, and a solid troubleshooting section. That's not fluff; that's practical.
  • Token efficiency is real — 365 lines sounds long, but it's packed with actionable content and clear commands. No cruft.

The Big One: Missing References Architecture

Here's what's holding you back from 98+: all your content lives in a single SKILL.md file. You've got backup restore procedures, monitoring setup, and troubleshooting crammed inline, which bloats the main file and makes layering impossible.

The fix: Create a references/ directory with three files:

  • `references/backup-resto...

Report Security Issue

Found a security vulnerability in this agent skill?