agentsclimarketplace

Ship & operate

32,362 rows, by stacks then stars

1,245 of these skill files have been read, by 1,077 distinct authors, and what they tell an agent counted. What Ship & operate authors agree on, and what they forbid

  • Ml model deployment

    SWEStash/swe-workflow-skills/plugins/ml/skills/ml-model-deployment Skill

    1★ repo

    Deploy ML models to production — serving infrastructure, monitoring, drift detection, safe rollouts. Triggers: deploy model, serve model, model API, model monitoring, data drift, concept drift, model degradation, A/B test model, canary model, inference endpoint, prediction API, retrain trigger.

  • Observability design

    SWEStash/swe-workflow-skills/plugins/ml/skills/observability-design Skill

    1★ repo

    Design production observability — SLIs, SLOs, SLAs, error budgets, OpenTelemetry traces/metrics/logs, structured logging, alerting, dashboards. Triggers: SLO, SLI, SLA, error budget, observability, monitoring, OpenTelemetry, OTel, tracing, distributed tracing, structured logging, alerting, dashboard, metrics, correlation ID, alert fatigue.

  • Git workflow

    SWEStash/swe-workflow-skills/plugins/mobile/skills/git-workflow Skill

    1★ repo

    Write commit messages, PR descriptions, and manage branching strategy following conventional commits.

  • Mobile release

    SWEStash/swe-workflow-skills/plugins/mobile/skills/mobile-release Skill

    1★ repo

    Ship mobile apps through the app stores — signing and provisioning, store review and rejection handling, phased/staged rollouts with halt criteria, crash monitoring, versioning and build numbers, beta channels (TestFlight, Play tracks), forced updates, and the no-instant-rollback reality of mobile. Triggers: app store release, publish to App Store, Play Store, TestFlight, staged rollout, app review rejected, code signing, provisioning profile, mobile release, hotfix a mobile bug. General semver/registry/library publishing → release-management.

  • Retrospective

    SWEStash/swe-workflow-skills/plugins/pm/skills/retrospective Skill

    1★ repo

    Facilitate sprint retros, project post-mortems, and incident post-mortems with actionable, owned improvements. Triggers: retrospective, retro, post-mortem, postmortem, lessons learned, what went wrong, what went well, incident review, blameless, action items, sprint review, after action review.

  • Git workflow

    SWEStash/swe-workflow-skills/plugins/qa/skills/git-workflow Skill

    1★ repo

    Write commit messages, PR descriptions, and manage branching strategy following conventional commits.

  • Tdd workflow

    SWEStash/swe-workflow-skills/plugins/qa/skills/tdd-workflow Skill

    1★ repo

    Guide test-driven development with red-green-refactor. For NEW code via test-first — use test-suite-design for adding tests to existing code.

  • Git workflow

    SWEStash/swe-workflow-skills/plugins/security/skills/git-workflow Skill

    1★ repo

    Write commit messages, PR descriptions, and manage branching strategy following conventional commits.

  • Incident response

    SWEStash/swe-workflow-skills/plugins/security/skills/incident-response Skill

    1★ repo

    Structured production incident workflow — triage, mitigation, investigation, recovery, comms. Triggers: production is down, site is down, incident, outage, users seeing errors, on-call, alert fired, p0, p1, sev1, sev2, broken in prod, rollback, emergency deploy. For active incidents under time pressure.

  • Rollback strategy

    SWEStash/swe-workflow-skills/plugins/security/skills/rollback-strategy Skill

    1★ repo

    Design safe rollback plans before deploying — identify irreversible changes, classify rollback complexity, create tested undo procedures. Triggers: rollback plan, rollback strategy, how do I undo this, can we revert, what if the deploy fails, safe to deploy, feature flag rollout, blue-green, database migration rollback, irreversible change.

  • Cicd pipeline

    SWEStash/swe-workflow-skills/skills/cicd-pipeline Skill

    1★ repo

    Design CI/CD pipelines for automated build, test, deploy — GitHub Actions, GitLab CI, quality gates. Triggers: CI/CD, pipeline, GitHub Actions, GitLab CI, workflow, automated deployment, build pipeline, continuous integration, continuous deployment, automate tests on PR, deploy automatically, quality gate.

  • Containerization

    SWEStash/swe-workflow-skills/skills/containerization Skill

    1★ repo

    Write production-grade Dockerfiles, docker-compose, and Kubernetes manifests following security and reliability best practices. Triggers: Dockerfile, docker-compose, containerize, Docker image, Kubernetes, k8s manifest, container, pod, deployment yaml, multi-stage build, docker build, image size, container security.

  • Deployment checklist

    SWEStash/swe-workflow-skills/skills/deployment-checklist Skill

    1★ repo

    Pre-deploy verification and release safety checks — config, migrations, monitoring, rollback readiness, comms. Triggers: deployment checklist, ready to deploy, pre-deploy, release checklist, go-live, ship checklist, deploy safety, is this safe to ship, release readiness.

  • Deployment repo

    SWEStash/swe-workflow-skills/skills/deployment-repo Skill

    1★ repo

    Design a deployment (GitOps) repo that orchestrates multiple services in a polyrepo — version pinning, environment promotion, compatibility matrices, system config. Triggers: deployment repo, GitOps repo, polyrepo, multi-repo, version pinning, compatibility matrix, environment promotion, multi-service deployment, orchestration repo, which versions work together.

  • Git workflow

    SWEStash/swe-workflow-skills/skills/git-workflow Skill

    1★ repo

    Write commit messages, PR descriptions, and manage branching strategy following conventional commits.

  • Gitops delivery

    SWEStash/swe-workflow-skills/skills/gitops-delivery Skill

    1★ repo

    Design GitOps continuous delivery with ArgoCD or Flux — declarative reconciliation, cross-repo CI/CD triggers, drift detection, progressive delivery. Triggers: ArgoCD, Flux, FluxCD, GitOps, git-based deployment, declarative delivery, auto-sync, drift detection, cross-repo trigger, reconciliation loop, pull-based deployment, canary GitOps.

  • Incident response

    SWEStash/swe-workflow-skills/skills/incident-response Skill

    1★ repo

    Structured production incident workflow — triage, mitigation, investigation, recovery, comms. Triggers: production is down, site is down, incident, outage, users seeing errors, on-call, alert fired, p0, p1, sev1, sev2, broken in prod, rollback, emergency deploy. For active incidents under time pressure.

  • Infrastructure as code

    SWEStash/swe-workflow-skills/skills/infrastructure-as-code Skill

    1★ repo

    Write and review IaC with Terraform, CloudFormation, Pulumi, or CDK — modularity, security, state management. Triggers: Terraform, CloudFormation, Pulumi, infrastructure as code, IaC, provision, cloud resources, terraform module, state management, terraform plan, CDK, drift, remote state.

  • Ml model deployment

    SWEStash/swe-workflow-skills/skills/ml-model-deployment Skill

    1★ repo

    Deploy ML models to production — serving infrastructure, monitoring, drift detection, safe rollouts. Triggers: deploy model, serve model, model API, model monitoring, data drift, concept drift, model degradation, A/B test model, canary model, inference endpoint, prediction API, retrain trigger.

  • Mobile release

    SWEStash/swe-workflow-skills/skills/mobile-release Skill

    1★ repo

    Ship mobile apps through the app stores — signing and provisioning, store review and rejection handling, phased/staged rollouts with halt criteria, crash monitoring, versioning and build numbers, beta channels (TestFlight, Play tracks), forced updates, and the no-instant-rollback reality of mobile. Triggers: app store release, publish to App Store, Play Store, TestFlight, staged rollout, app review rejected, code signing, provisioning profile, mobile release, hotfix a mobile bug. General semver/registry/library publishing → release-management.

  • Observability design

    SWEStash/swe-workflow-skills/skills/observability-design Skill

    1★ repo

    Design production observability — SLIs, SLOs, SLAs, error budgets, OpenTelemetry traces/metrics/logs, structured logging, alerting, dashboards. Triggers: SLO, SLI, SLA, error budget, observability, monitoring, OpenTelemetry, OTel, tracing, distributed tracing, structured logging, alerting, dashboard, metrics, correlation ID, alert fatigue.

  • Release management

    SWEStash/swe-workflow-skills/skills/release-management Skill

    1★ repo

    Cut and publish software releases right-sized to the project — semver decisions, changelogs, tagging, automated version bumps (release-please, changesets, semantic-release), publishing gates, npm/PyPI/container registry publishing, pre-release channels, monorepo versioning. Triggers: cut a release, release this, publish to npm, publish to PyPI, publish this package, version bump, what version should this be, semver, changelog, tag a release, release notes, GitHub release, prerelease, release automation, release PR. Deploy-time safety → deployment-checklist; commit/PR hygiene → git-workflow.

  • Resilience engineering

    SWEStash/swe-workflow-skills/skills/resilience-engineering Skill

    1★ repo

    Design systems that survive failure — failure-mode analysis, resilience patterns (timeouts, retries with backoff, circuit breakers, bulkheads, load shedding, graceful degradation), chaos experiments, disaster recovery with RTO/RPO, backup restore testing, game days. Triggers: chaos engineering, disaster recovery, DR plan, what if the database goes down, single point of failure, failover, circuit breaker, RTO, RPO, game day, high availability. An incident happening NOW → incident-response; undoing a bad deploy → rollback-strategy.

  • Retrospective

    SWEStash/swe-workflow-skills/skills/retrospective Skill

    1★ repo

    Facilitate sprint retros, project post-mortems, and incident post-mortems with actionable, owned improvements. Triggers: retrospective, retro, post-mortem, postmortem, lessons learned, what went wrong, what went well, incident review, blameless, action items, sprint review, after action review.

  • Rollback strategy

    SWEStash/swe-workflow-skills/skills/rollback-strategy Skill

    1★ repo

    Design safe rollback plans before deploying — identify irreversible changes, classify rollback complexity, create tested undo procedures. Triggers: rollback plan, rollback strategy, how do I undo this, can we revert, what if the deploy fails, safe to deploy, feature flag rollout, blue-green, database migration rollback, irreversible change.

  • Tdd workflow

    SWEStash/swe-workflow-skills/skills/tdd-workflow Skill

    1★ repo

    Guide test-driven development with red-green-refactor. For NEW code via test-first — use test-suite-design for adding tests to existing code.

  • Pre deploy check

    feel-flow/agent-skills-examples/task/pre-deploy-check Skill

    1★ repo

    デプロイ前の必須チェックを実行する。ブランチ確認、テスト実行、ビルド確認を行う。

  • Ollygarden otel collector config decomposition

    ollygarden/skills/skills/ollygarden-otel-collector-config-decomposition Skill

    1★ repo

    Decide and execute plain-file decomposition for OpenTelemetry Collector YAML. Use for "should I split this collector config?", "break up this otelcol YAML", "organize it by signal or team", or "create environment overlays". Leaves simple configs intact and proves warranted splits equivalent after merge. Not for Helm, Kustomize, or Terraform packaging; use otel-collector for component facts and ollygarden-otel-collector-config-validation for behavioral proof.

  • Ollygarden otel collector config validation

    ollygarden/skills/skills/ollygarden-otel-collector-config-validation Skill

    1★ repo

    Behaviorally validate an OpenTelemetry Collector processor or connector against realistic telemetry. Use for "does my filter drop the right spans?", "prove this transform before shipping", "validate passes but behavior is wrong", or testing filter, transform, redaction, tail_sampling, routing, signaltometrics, count, or spanmetrics. Running the harness executes a pinned remote container and requires explicit confirmation. Not for syntax lookup (use `otel-collector`/`otel-ottl`), generic telemetry generation (`otel-telemetrygen`), or receiver/exporter testing.

  • Ollygarden otel collector k8s daemonset

    ollygarden/skills/skills/ollygarden-otel-collector-k8s-daemonset Skill

    1★ repo

    OllyGarden's opinionated, optimization-first OpenTelemetry Collector configuration for a Kubernetes node agent (DaemonSet). Use when authoring or reviewing a node-level/agent collector config for logs, metrics, and traces on Kubernetes, or when the user wants to reduce telemetry volume, cost, cardinality, or noise at collection time. Triggers on "collector daemonset config", "node agent collector", "otel collector on kubernetes", "reduce telemetry cost in the collector", "tune kubeletstats/hostmetrics/filelog", "drop noisy spans/logs/metrics in the collector".

  • Ollygarden otel go setup

    ollygarden/skills/skills/ollygarden-otel-go-setup Skill

    1★ repo

    Ollygarden's recommended pattern for setting up the OpenTelemetry SDK in Go services using otelconf. Covers project structure, the Providers struct, no-op fallback, runtime attribute injection, and the zap log bridge. Use when adding OTel to a Go project, structuring telemetry code, or reviewing an existing setup — including when DB spans show up as trace roots or GORM/database spans are disconnected from HTTP spans. Triggers on "go otel setup", "go telemetry pattern", "Providers struct go otel", "gorm WithContext", "root client span go".

  • Ollygarden otel java setup

    ollygarden/skills/skills/ollygarden-otel-java-setup Skill

    1★ repo

    Ollygarden's recommended pattern for setting up OpenTelemetry in Java services. Covers the Javaagent vs Spring Boot Starter vs manual autoconfigure decision-making, the Maven BOM dependency pattern, and the setup checklist (no query strings in telemetry, startup DB span hygiene, declarative YAML config, standard OTEL_* env vars honored). Use when adding OTel to a Java project, choosing a setup path, or reviewing dependency declarations. Triggers on "java otel setup", "javaagent vs starter", "opentelemetry-bom", "url.query", "query parameter PII".

  • Ollygarden otel js setup

    ollygarden/skills/skills/ollygarden-otel-js-setup Skill

    1★ repo

    Ollygarden's recommended pattern for setting up OpenTelemetry in Node.js services. Covers project structure, which auto-instrumentations to disable, the entry-point ordering, the programmatic NodeSDK fallback, and the setup checklist (no query strings in telemetry, startup/non-request span hygiene, declarative YAML config, standard OTEL_* env vars honored, lean resource with service.instance.id) closed by a required verification report. Use when adding OTel to a Node.js project, structuring telemetry code, or reviewing an existing setup. Triggers on "node otel setup", "NodeSDK pattern", "auto instrumentation node", "url.query", "query parameter PII", "service.instance.id".

  • Push release

    Miyamura80/MCP-Template/.agents/skills/push-release Skill

    1★ repo

    Cut a new release - bump the version in pyproject.toml, tag, and push to trigger PyPI publish and MCP Registry publish via GitHub Actions. Use when the user asks to release, ship a version, bump and tag, cut a hotfix, or publish to PyPI.

  • Automation audit ops

    Lukk17/agent-standards/.agents/skills/automation-audit-ops Skill

    1★ repo

    Evidence-first automation inventory and overlap audit workflow for ECC. Use when the user wants to know which jobs, hooks, connectors, MCP servers, or wrappers are live, broken, redundant, or missing before fixing anything.

  • Deployment patterns

    Lukk17/agent-standards/.agents/skills/deployment-patterns Skill

    1★ repo

    Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

  • Docker patterns

    Lukk17/agent-standards/.agents/skills/docker-patterns Skill

    1★ repo

    Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.

  • Finance billing ops

    Lukk17/agent-standards/.agents/skills/finance-billing-ops Skill

    1★ repo

    Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.

  • Git workflow

    Lukk17/agent-standards/.agents/skills/git-workflow Skill

    1★ repo

    Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.

  • Github ops

    Lukk17/agent-standards/.agents/skills/github-ops Skill

    1★ repo

    GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.

  • Observability and logging

    Lukk17/agent-standards/.agents/skills/observability-and-logging Skill

    1★ repo

    Structured logging and production observability for services. Logging discipline (one abstraction, levels, correlation IDs, never log secrets), health and metrics and tracing, SLOs, resilient outbound calls (timeouts, retry with backoff, circuit breaker), graceful shutdown, and the canonical startup-readiness log. Use when adding logging, instrumenting a service, or making it operable in production.

  • Tdd workflow

    Lukk17/agent-standards/.agents/skills/tdd-workflow Skill

    1★ repo

    Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with around 90% line coverage of real logic including unit, integration, and E2E tests.

  • K8s nextjs deploy

    andreab67/agent-skills/k8s-nextjs-deploy Skill

    1★ repo

    Kubernetes deployment patterns for Next.js applications — Deployment/Service/Ingress manifests, Harbor image pull secrets, Traefik ingress with cert-manager TLS, Linkerd service mesh, multi-app namespaces, and K8s secret rotation. Use this skill whenever the user mentions deploying a Next.js app to Kubernetes, ImagePullBackOff, CrashLoopBackOff, Harbor pull secret, Traefik ingress, cert-manager, a missing secretKeyRef, or namespace recovery — even if they just say "the pod won't start" or "deploy this to k8s" without further detail.

  • Nextjs monorepo ci

    andreab67/agent-skills/nextjs-monorepo-ci Skill

    1★ repo

    Design, fix, and extend GitLab CI/CD pipelines for Next.js monorepos — multi-stage pipelines (validate, security, build, obfuscate, package, notify), Kaniko image builds, Semgrep SAST/secrets, gitleaks, javascript-obfuscator standalone output, Harbor registry, and IndexNow notify stage. Use this skill whenever the user mentions GitLab CI, a failing CI job, gitleaks, Kaniko, javascript-obfuscator, Harbor push, or any pipeline work in a Next.js monorepo — even if they just say "CI is broken" or "add a new app to the pipeline" without more detail.

  • Postgres ops

    andreab67/agent-skills/postgres-ops Skill

    1★ repo

    Operational PostgreSQL workflows for production environments — diagnosing slow queries, lock contention, bloat, replication lag, and connection-pool exhaustion; designing and reviewing backups (pg_dump, pg_basebackup, PITR via WAL archiving); planning upgrades and major-version migrations; configuring pgBouncer/RDS Proxy/PgCat; tuning postgresql.conf for OLTP and analytics workloads; writing and reviewing schema migrations across EF Core, Alembic, Flyway, and raw SQL; setting up observability with postgres_exporter to Prometheus, log shipping to Loki, and slow-query alerting; hardening for DoD/federal use (STIG, role separation, RLS, pgaudit, TLS). Use this skill whenever the user mentions Postgres, PostgreSQL, pg_, EXPLAIN ANALYZE, autovacuum, pgBouncer, replication lag, schema migrations, or anything involving a Postgres incident, performance problem, upgrade, backup, or compliance audit — even if they don't say "Postgres" explicitly but the context is clearly a relational database on PostgreSQL. Do NOT use for greenfield CRUD scaffolding — use nextjs-react-postgres-builder for that.

  • Dockerfile

    petr-korobeinikov/skills/skills/dockerfile Skill

    1★ repo

    Compose, optimize, and fix Dockerfiles for fast, cache-friendly builds and the smallest secure final image — multi-stage, deps-before-source layer caching, and a final base driven toward scratch / distroless / slim. Keeps builds portable when BuildKit is unavailable and secrets out of layers, runs non-root, pins bases, and gates on a linter.

  • Clarify scope

    stevennitesh/programming-agent-skills/skills/.archive/clarify-scope Skill

    1★ repo

    Use when cheap repo evidence cannot resolve a material decision about target behavior, public or caller contract, test strategy, data/state/security, release or rollback risk, ownership boundary, or durable decision records before safe implementation can proceed.

  • Subagent workflow

    stevennitesh/programming-agent-skills/skills/.archive/subagent-workflow Skill

    1★ repo

    Use when the user explicitly asks for subagents, parallel agents, worker agents, independent code review, multi-agent codebase exploration, subagent-ready handoffs, or an approved plan/issue calls for authorized, bounded delegation that is cheaper than local work.

  • Stand ci

    lgtm-hq/ai-skills/skills/stand-ci Skill

    1★ repo

    CI/CD and GitHub Actions guidelines. Use when writing workflows or Actions. Shell script code must be in dedicated .sh or .py files. Actions must be pinned to SHAs, not versions.

  • Observability designer

    GustavoGutierrez/engineering-skills/skills/observability-designer Skill

    1★ repo

    Trigger: observability design, observability strategy, telemetry architecture, instrument a system, distributed observability, AI observability, workflow monitoring, design alerts. Design correlation-first observability strategies covering logs, metrics, traces, AI telemetry, and workflow visibility for distributed and AI-native systems.

  • Release planner

    GustavoGutierrez/engineering-skills/skills/release-planner Skill

    1★ repo

    Trigger: release planning, rollout strategy, release waves, phased rollout, migration sequencing, canary release, rollback planning, go no-go criteria. Design a complete release execution plan connecting technical deployment with operational coordination and stakeholder communication.

  • Workflow designer

    GustavoGutierrez/engineering-skills/skills/workflow-designer Skill

    1★ repo

    Design state machines, orchestration workflows, saga patterns, and resilience strategies for distributed systems, AI agents, and complex async processes. Use when asking for a workflow, state machine, orchestration design, saga, HITL checkpoint, or process resilience strategy.

  • Dhq deploy

    jsirish/workflow-skills/skills/dhq-deploy Skill

    no license1★ repo

    Deploy a project to production using the DeployHQ CLI (dhq). Use when asked to deploy, trigger a deployment, or ship code via DeployHQ.

  • Server deploy

    jsirish/workflow-skills/skills/server-deploy Skill

    no license1★ repo

    Push local databases and assets to a remote pre-prod or staging server using deploy.sh. Use during major version upgrades or when deploying pre-computed public/assets to a staging environment. See server-sync for the reverse direction.

  • Llm observability and evals

    wanghong5233/agent-engineering-kit/cursor/.cursor/skills/llm-observability-and-evals Skill

    1★ repo

    Design observability and eval contracts for production LLM/Agent systems. Use when adding ask/retrieval/tool/model flows, debugging quality regressions, defining trace/log/metric fields, building golden sets, or proving an Agent feature works. Do NOT use for cost-only work.

  • Writing pitfall archive

    wanghong5233/agent-engineering-kit/cursor/.cursor/skills/writing-pitfall-archive Skill

    1★ repo

    Write or refactor a pitfall archive (recurring failures → invariants; Google SRE blameless multi-incident form). Use when editing `*DEPLOYMENT*`/`*MANUAL*`/`*RUNBOOK*`/`*PITFALL*`/`*坑*`/`*手册*` under `docs/`, or user asks 沉淀部署经验/踩坑/故障复盘/去AI味/不再犯同样错误. Do NOT use for single postmortems.

  • Content pipeline ops

    buildwitharup/cortex/skills/content-pipeline-ops Skill

    1★ repo

    Use when the user wants to build or fix an end-to-end content workflow — from intake and briefing through production, review, and publication. Also triggers on "content pipeline", "content workflow", "content operations", "content calendar", "editorial process", "content production", "content review process", "content ops", "content management workflow".

  • World class web release

    frankxai/starlight-design-intelligence/skills/world-class-web-release Skill

    no license1★ repo

    Use for any high-value website, landing page, homepage, partner page, product surface, brand experience, or redesign where language, typography, imagery, motion, implementation, and production proof must feel distinctive and human. Also use when upgrading a web-design quality system or release gate.

  • Cicd deployment

    tdyzzsp47/claude-skills/skills/cicd-deployment Skill

    1★ repo

    CI/CDパイプライン構築・デプロイ戦略・リリース管理をカバーするスキル。新規プロジェクトのCI設計から既存パイプラインの改善、デプロイ戦略の選定、リリース運用の整備まで幅広く対応する。

  • Git workflow

    tdyzzsp47/claude-skills/skills/git-workflow Skill

    1★ repo

    ブランチ戦略・コミット規約・PR運用を定めるGit運用スキル。新規リポジトリのルール策定時、開発フロー整備時、AIエージェント並列開発の調整時に使う。