Docker
Contenidors i Docker
coolify
mikkelkrogsholm
"Coolify — open-source self-hostable PaaS for deploying apps, databases, and services via Docker. Use when building with Coolify or asking about its deployment configuration, environment variables, reverse proxy setup, health checks, persistent storage, or Git-based CI/CD integration. Fetch live documentation for up-to-date details."
rustfs
mikkelkrogsholm
"RustFS — S3-compatible distributed object storage written in Rust. Use when building with RustFS or asking about its APIs, configuration, deployment, Docker setup, or integration. Fetch live documentation for up-to-date details."
ai-image
tyrchen
Generate AI images using OpenAI's gpt-image-1 model with customizable aspect ratios and artistic themes. Use when the user wants to create images, generate artwork, or mentions image generation with specific styles like Ghibli, futuristic, Pixar, oil painting, or Chinese painting.
baoyu-post-to-wechat
xuanxuan1983
Post content to WeChat Official Account (微信公众号). Supports both article posting (文章) and image-text posting (图文).
baoyu-compress-image
xuanxuan1983
Cross-platform image compression skill. Converts images to WebP by default with PNG-to-PNG support. Uses system tools (sips, cwebp, ImageMagick) with Sharp fallback.
docker_optimization
vuralserhat86
Docker image optimization patterns including multi-stage builds, layer caching, security hardening, and size reduction techniques. Use when building Docker images, optimizing container size, improving build performance, or implementing Docker security best practices. Reduces image sizes by 70-90% and build times by 50-80%.
deploy_monitoring
vuralserhat86
Health checks, metrics, alerting ve rollback stratejileri.
build
Exgentic
Build the Eval Containers image fleet — or any single artifact or eval combination — with docker buildx bake, and write the per-artifact docker-bake.hcl files the build graph requires. Use when building an image locally, composing a benchmark × agent × model eval, or adding a bake file for a new artifact. For cutting and pushing a tagged release of the whole fleet (with the readiness gate), use the release skill, which wraps this one.
frankenphp
rawveg
FrankenPHP Documentation - Modern PHP application server built on Caddy
kdp-aplus-content
rawveg
Create Amazon-compliant A+ Content for KDP books with text, module layouts, and image specs. Use for A+ Content creation, book detail page design, module selection, compliance checking, rejection avoidance, or KDP marketing materials.
audit-fleet
Exgentic
Run the whole-repository health audit that a release manager reads before cutting a tag — run every mechanical gate, reconcile counts against the README, walk the ten fleet questions (does every benchmark build, does every released benchmark have a fixture, do the docs match disk, are agent versions pinned, is CI real), and classify a red / yellow / green verdict. Use this for "audit the fleet", "is the repo release-ready", a quarterly health check, or as step 25 of the verify release walk. This is the whole-repo cross-cutting pass; for a single Dockerfile use audit-dockerfile, for a single trajectory use audit-trajectory, and for RULES-text-vs-code drift use audit-rules-drift.
audit-benchmark
Exgentic
Produce or refresh one benchmark's AUDIT.md — the standing record of what has actually been checked about it (validity, safety, size, speed, cost, distribution). Use it when adding a benchmark, after changing its Dockerfile or grader, when its AUDIT.md is stale, or as the per-benchmark step of a fleet audit. It fills the machine-measurable fields from real tool runs and leaves human-judgment fields (running, traces-reviewed, replicate-official, cost) explicitly unchecked until a human does them. For the whole-repo sweep use audit-fleet; this skill drives the oracle (core/oracle/README.md) for the grading-soundness rung.
audit-dockerfile
Exgentic
Run a judgment-level health review of one or more benchmark/agent Dockerfiles — the procedural layer that catches what the mechanical Dockerfile rule catalog cannot: unreasonable install order, dead code, image bloat, labels that misdescribe the image, unsafe entrypoints, and subtle smells a reviewer would flag on sight. Use this for "audit the Dockerfiles", when the mechanical catalog flags a yellow, when a new benchmark/agent batch lands, or as step 23 of the verify release walk. This is the per-file Dockerfile pass; for per-fixture trajectories use audit-trajectory, and for the whole-repo sweep use audit-fleet.
add-benchmark
Exgentic
Use when adding a new benchmark image to the fleet — a Dockerized task plus verifier that evaluates an agent. Walks the directory layout, the five authored files, the two version knobs, required labels, and the three deployment surfaces. For packaging the AI system that runs inside a benchmark (install + entrypoint, LLM access), use add-agent instead.
gemini-image-generator
mkdev-me
Generate images using Google Gemini with customizable options
Dify 安全和部署 SKILL
SystemTce
Dify 安全实践和部署运维完整指南，涵盖SSRF防护、代码沙箱、Docker/Kubernetes部署、监控告警和故障恢复
openai-image-gen
malue-ai
Batch-generate images via OpenAI Images API. Random prompt sampler + index.html gallery.
c3-onboard
lagz0ne
Creates C3 architecture documentation from scratch using staged Socratic discovery. This skill should be used when the user asks to: - "adopt C3", "init C3", "initialize C3", "start C3", "bootstrap C3" - "scaffold C3 docs", "create C3 docs", "create .c3", "set up .c3" - "set up architecture docs", "create architecture documentation" - "document this project", "document the codebase", "document the architecture from scratch" - "new C3 project", "first time with C3", "never used C3", "getting started with C3" - "onboard", "onboard this project", "C3 onboarding" DO NOT use when .c3/ already exists (route to c3-audit, c3-change, or c3-query). DO NOT use for updating existing docs (route to c3-change). Implements 3-stage workflow: Inventory → Details → Finalize.
dagger
Tyler-R-Kendrick
Use when building CI/CD pipelines as code with Dagger. Covers Dagger Functions, modules, container-based execution, caching, and SDK usage in TypeScript, Python, and Go. USE FOR: CI/CD pipelines as code, Dagger Functions and modules, container-based build steps, reproducible pipelines DO NOT USE FOR: cloud infrastructure provisioning (use terraform or pulumi), container image authoring (use docker), Kubernetes deployment (use kubernetes)
iac
Tyler-R-Kendrick
Use when working with Infrastructure as Code tools and platforms. Covers Terraform, Pulumi, CloudFormation, Bicep, ARM, Kubernetes, Helm, Docker, Crossplane, and Dagger. USE FOR: choosing IaC tools, comparing Terraform vs Pulumi vs CloudFormation, infrastructure strategy DO NOT USE FOR: specific tool syntax (use the sub-skills: terraform, pulumi, bicep, etc.)
seo-meta-tags
jeremy0x
"Comprehensive SEO and social metadata implementation for HTML, Next.js App Router, and Vite (React & Vue) projects. Use when: (1) Creating, editing, or reviewing meta tags, Open Graph, Twitter Cards, canonical/hreflang links, JSON-LD structured data, theme-color, or favicon/manifest config; (2) Working with html/index.html, nextjs/metadata.ts, nextjs/dynamic-metadata-example.tsx, vite/index.html, vite/SEO.tsx, or vite/SEO.vue; (3) Adding SEO to a new page or route; (4) Migrating from react-helmet, vue-meta, or next-seo; (5) Generating dynamic metadata for content-driven pages; (6) Auditing metadata for completeness or best-practice compliance."
aspire
Tyler-R-Kendrick
Use when configuring dev containers for .NET Aspire projects. Covers the Aspire workload, Docker-in-Docker requirement, dashboard port forwarding, and multi-service orchestration in Codespaces. USE FOR: .NET Aspire dev containers, Aspire workload in Codespaces, Aspire dashboard port forwarding, Aspire + Docker-in-Docker setup DO NOT USE FOR: general .NET dev containers without Aspire (use dotnet), standalone Docker-in-Docker (use docker-in-docker), general devcontainer.json (use devcontainer)
multi-container-workspaces
Tyler-R-Kendrick
Use when setting up dev containers with sidecar services like databases, caches, or message brokers. Covers Docker Compose integration, service networking, and multi-service devcontainer.json configuration. USE FOR: Docker Compose sidecar services, database/cache/queue containers alongside dev containers, multi-service networking, service health checks DO NOT USE FOR: general devcontainer.json schema (use devcontainer), Docker-in-Docker for building images (use docker-in-docker), production Kubernetes deployment (use iac/kubernetes)
tools
Tyler-R-Kendrick
Use when working with fundamental CLI tools and utilities that are essential for software development across all languages and platforms. Covers shells, version control, system package managers, containers, remote access, HTTP clients, data processing, and build runners. USE FOR: CLI tools, developer tooling, shell scripting, version control, system package managers, containers, remote access, build automation, text processing, choosing cross-platform dev tools DO NOT USE FOR: language-specific package managers (use language-specific skills like npm/pip/cargo), IDE configuration, language-specific build tools (use language-specific skills)