deploying-cloud-k8s

1 stars 2 forks
17
A

Deploys applications to cloud Kubernetes (AKS/GKE/DOKS) with CI/CD pipelines.Use when deploying to production, setting up GitHub Actions, troubleshooting deployments.Covers build-time vs runtime vars, architecture matching, and battle-tested debugging.

Also in: kubernetes

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-cloud-k8s
skilz install mjunaidca/mjs-agent-skills/deploying-cloud-k8s --agent opencode
skilz install mjunaidca/mjs-agent-skills/deploying-cloud-k8s --agent codex
skilz install mjunaidca/mjs-agent-skills/deploying-cloud-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-cloud-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
development
Primary Domain
github
Market Score
17

Agent Skill Grade

A
Score: 93/100 Click to see breakdown

Score Breakdown

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

Areas to Improve

  • Missing TOC in long reference file
  • Verbose explanation reduces conciseness
  • Some content duplication between main and reference

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 skills in the Kubernetes deployment space, and the way you structured the progressive disclosure here really stands out—hitting 93/100 suggests you've nailed the balance between comprehensiveness and cognitive load that most DevOps tooling completely fumbles.

Links:

The TL;DR

You're at 93/100, A-grade territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Utility (20/20)—the skill actually solves real problems that trip people up (architecture mismatches, build-time vs runtime variables, troubleshooting K8s issues). Weakest area is Spec Compliance (12/15), but that's mostly about description granularity, not substance.

What's Working Well

  • Excellent problem coverage: You're addressing actual pain points—architecture mismatches, build-time vs runtime variables, platform detection failures. That's not theoretical stuff; that's battle-tested.
  • Strong validation patterns: The Pre-Deployment Checklist with checkboxes and the Quick Diagnosis Flow actually guide people to verify things work before deploying. Most DevOps guides skip this.
  • Practical examples: WRONG/RIGHT comparisons for Buildx, GitHub Actions templates, Helm commands with inline comments—these aren't fluff, they're immediately copy-pasteable.
  • Token efficiency: For a 427-line reference file, you're packing a lot of signal without obvious bloat. The quick start gets people unblocked fast.

The Big One: Add TOC to Your Reference File

Your references/production-patterns.md is 427 lines covering GitOps, Observability, Security, Resilience, and checklists—but no table of contents. Someone scrolling through that gets lost.

The fix: Add a simple T...

Report Security Issue

Found a security vulnerability in this agent skill?