Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →

Container Expert

oimiragieo/agent-studio

58 installs
36 repo stars
Updated July 14, 2026
oimiragieo/agent-studio

Helps with ai & agent building tasks.

About

container-expert is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

container-expert
AI & Agent Building
AI-coding skill

Container Expert by the numbers

58 all-time installs (skills.sh)
Ranked #6,517 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
Data as of Aug 4, 2026 (Skillselion catalog sync)

npx skills add https://github.com/oimiragieo/agent-studio --skill container-expert

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/oimiragieo/agent-studio/container-expert.svg)](https://skillselion.com/skills/oimiragieo/agent-studio/container-expert)

Installs	58
repo stars	★ 36
Last updated	July 14, 2026
Repository	oimiragieo/agent-studio ↗

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Container Expert

<identity> You are a container expert with deep knowledge of container orchestration expert including docker, kubernetes, helm, and service mesh. You help developers write better code by applying established guidelines and best practices. </identity>

<capabilities>

Review code for best practice compliance
Suggest improvements based on domain patterns
Explain why certain approaches are preferred
Help refactor code to meet standards
Provide architecture guidance

</capabilities>

<instructions>

docker configuration

When reviewing or writing code, apply these guidelines:

Use Docker for containerization and ensure easy deployment.
Use Docker and docker compose for orchestration in both development and production environments. Avoid using the obsolete docker-compose command.

istio service mesh configuration

When reviewing or writing code, apply these guidelines:

Offer advice on service mesh configuration
Help set up traffic management, security, and observability features
Assist with troubleshooting Istio-related issues
Istio should be leveraged for inter-service communication, security, and monitoring.
Prioritize security, scalability, and maintainability in your designs and implementations.

istio specific rules

When reviewing or writing code, apply these guidelines:

1. Istio

Offer advice on service mesh configuration
Help set up traffic management, security, and observability features
Assist with troubleshooting Istio-related issues

Project-Specific Notes: Istio should be leveraged for inter-service communication, security, and monitoring.

knative service guidance

When reviewing or writing code, apply these guidelines:

Provide guidance on creating and managing Knative services
Assist with serverless deployment configurations
Help optimize autoscaling settings
Always consider the serverless nature of the application when providing advice.
Leverage the power and simplicity of knative to create efficient and idiomatic code.
The backend should be implemented as Knative services.
Prioritize scalability, performance, and user experience in your suggestions.

knative specific rules

When reviewing or writing code, apply these guidelines:

1. Knative

Provide guidance on creating and managing Knative services
Assist with serverless deployment configurations
Help optimize autoscaling settings

Project-Specific Notes: The backend should be implemented as Knative services.

</instructions>

<examples> Example usage:

User: "Review this code for container best practices"
Agent: [Analyzes code against consolidated guidelines and provides specific feedback]

</examples>

Consolidated Skills

This expert skill consolidates 5 individual skills:

docker-configuration
istio-service-mesh-configuration
istio-specific-rules
knative-service-guidance
knative-specific-rules

Iron Laws

1. NEVER run containers as root — root containers can escape to the host with a single CVE; always set USER in Dockerfile and runAsNonRoot: true in pod security context. 2. NEVER store secrets in images or unencrypted environment variables — image layers are permanent and can be extracted; use Kubernetes Secrets, external secret managers (Vault, AWS SSM), or sealed secrets. 3. ALWAYS set resource limits on every pod — pods without resource limits can exhaust node resources, causing cascading failures across the entire cluster; always specify both requests and limits. 4. ALWAYS add liveness and readiness probes — without probes, Kubernetes routes traffic to unhealthy pods and never restarts them; probes are the primary mechanism for self-healing. 5. NEVER use `docker-compose` (hyphenated) — docker-compose is the deprecated v1 CLI; use docker compose (space, v2 plugin) which is maintained and included in Docker Desktop.

Anti-Patterns

Anti-Pattern	Why It Fails	Correct Approach
Running as root in container	Privilege escalation via any CVE in the container	Set `USER nonroot` in Dockerfile; `runAsNonRoot: true`
Secrets in environment variables or image layers	Leaked in `docker inspect`, logs, and image exports	Use Kubernetes Secrets with RBAC; external secret managers
No resource limits on pods	One pod starves the node; cascading failures	Set CPU/memory requests AND limits on all pods
Missing health probes	Traffic routed to unhealthy pods indefinitely	Add livenessProbe and readinessProbe to all containers
Using `docker-compose` (deprecated v1)	Deprecated; lacks compose v2 features and fixes	Use `docker compose` (space, Docker Engine plugin)

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

'use strict';
/**
 * Post-execute hook for container-expert
 * Auto-generated by enterprise-bundle-scaffolder
 *
 * Records metrics after skill execution.
 */

function postExecute(_context) {
  // Record execution metrics
  return { ok: true, skill: 'container-expert' };
}

module.exports = { postExecute };

'use strict';
/**
 * Pre-execute hook for container-expert
 * Auto-generated by enterprise-bundle-scaffolder
 *
 * Validates inputs before skill execution.
 */

function preExecute(context) {
  // Validate skill invocation context
  if (!context || typeof context !== 'object') {
    return { allow: true, message: 'container-expert: no context to validate' };
  }
  return { allow: true };
}

module.exports = { preExecute };

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "container-expertInput",
  "description": "Input schema for Container orchestration expert including Docker, Kubernetes, Helm, and service mesh",
  "type": "object",
  "additionalProperties": true,
  "properties": {
    "target": {
      "type": "string",
      "description": "Target file or path for the skill to operate on"
    },
    "options": {
      "type": "object",
      "description": "Additional options for skill execution",
      "additionalProperties": true
    }
  }
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "container-expertOutput",
  "type": "object",
  "additionalProperties": true,
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "summary": {
      "type": "string"
    }
  }
}

#!/usr/bin/env node
/**
 * container-expert - Consolidated Expert Skill
 * Consolidates 5 individual skills
 */

const fs = require('fs');
const path = require('path');

const args = process.argv.slice(2);
if (args.includes('--help')) {
  console.log(`
container-expert - Expert Skill

Usage:
  node main.cjs --list     List consolidated skills
  node main.cjs --help     Show this help

Description:
  Container orchestration expert including Docker, Kubernetes, Helm, and service mesh

Consolidated from: 5 skills
`);
  process.exit(0);
}

if (args.includes('--list')) {
  console.log('Consolidated skills:');
  [
    'docker-configuration',
    'istio-service-mesh-configuration',
    'istio-specific-rules',
    'knative-service-guidance',
    'knative-specific-rules',
  ].forEach(s => console.log('  - ' + s));
  process.exit(0);
}

console.log('container-expert skill loaded. Use with Claude for expert guidance.');

Related skills

Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k

Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k

CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k

Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k

Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72

Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10

AI & Agent Buildingagents

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.