Ship & operate
32,510 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
microsoft/skills/.github/plugins/azure-skills/skills/microsoft-foundry/models/deploy-model/capacity Skill
2,884★ repoDiscovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.
The same file is in 7 other repositories
microsoft/skills/.github/plugins/azure-skills/skills/microsoft-foundry/models/deploy-model/preset Skill
2,884★ repoIntelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).
The same file is in 7 other repositories
microsoft/skills/.github/plugins/azure-skills/skills/python-appservice-deploy Skill
2,884★ repoDeploy Python (Flask/Django/FastAPI) code to Azure App Service Linux. WHEN: "Flask App Service", "Django App Service", "FastAPI App Service", "deploy Python to App Service". DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform/Bicep/IaC, full infra — use azure-prepare.
The same file is in 3 other repositories
microsoft/skills/.github/plugins/microsoft-365-agents-toolkit/skills/teams-app-developer/slack-to-teams Skill
2,884★ repoSub-skill of microsoft-365-agents-toolkit. Routed expert system with 100+ micro-expert files for migrating Slack bots to Teams, cross-platform bridging, and dual-platform bot development. USE FOR: migrating Slack bot to Teams, adding Teams support to Slack bot, building dual-platform bots, converting Block Kit to Adaptive Cards, identity/OAuth bridging, deploying bots to Azure or AWS, configuring AI model providers. DO NOT USE FOR: general web development, non-bot projects, standalone Teams development without Slack (use parent skill instead).
NVIDIA/skills/skills/aiq-deploy Skill
2,853★ repoUse when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
NVIDIA/skills/skills/doca-bf4-deployment Skill
2,853★ repoWARNING: guides potentially IRREVERSIBLE BlueField-4 hardware operations (PLDM firmware burns, ISO reflashes, power cycles, BMC factory resets) that can brick firmware, corrupt boot media, or cause outages — a maintenance window and rollback plan are required, and every mutating step is governed by doca-hardware-safety, loaded alongside. Use this skill for BlueField-4 (BF4) day-1 platform bring-up from the BMC: installing the BlueField/DOCA bundle ISO onto the DPU (Grace, the Arm complex) over UEFI HTTP Boot, PXE, or Redfish Virtual Media; the PLDM firmware-update flow (BMC, NIC firmware, SBIOS, ERoT) via the Redfish UpdateService and pldmtool; and a Grace Ubuntu image with optional cloud-init. Trigger on BlueField-4/BF4 bring-up phrasings even without "BF4": {bring up my new BlueField-4}, {the BlueField ISO will not boot over HTTP from the BMC}, {attach BF4 virtual media via Redfish}, {BF4 firmware Task stuck at Running}. BF3 bring-up, application launch, and library APIs belong to other skills.
NVIDIA/skills/skills/doca-collectx-deployment Skill
2,853★ repoUse this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box. Trigger even when the user never says CollectX or clx — implicit phrasings: {collector emits nothing downstream}, {add a provider to the clx collector}, {turn on the Prometheus endpoint}, {ship counters to Fluent Bit from the DPU}, {daemon starts but no schema rows appear}. This skill owns the CollectX collection mechanism plus the operator's own doca-telemetry / doca-telemetry-exporter usage; it ROUTES the productized DOCA Telemetry Service (DTS) to public docs (AGENTS.md Non-goal #7), the reader API to doca-telemetry, and the publisher API to doca-telemetry-exporter. Refuse to invent clx symbols, provider names, schema fields, flags, or config paths — describe the class and route to the live source.
NVIDIA/skills/skills/doca-container-deployment Skill
2,853★ repoUse this skill when the user is hands-on deploying an in-bundle DOCA service container (Argus, DMS, Firefly, or UROM service) on a BlueField — kubelet standalone watching a static-pod manifests directory, YAML pod-spec drop, kubelet status / ENTRYPOINT logs / per-service liveness, smoke-before-bulk, and the layered error taxonomy (pod-spec, scheduling, image pull, runtime, mount, network, version, host). Trigger even when the user does not say "container deployment" — typical implicit phrasings include "how do I run my built service on the BlueField?", "where do I drop the pod-spec YAML?", "pod stuck in Pending / ImagePullBackOff / CrashLoopBackOff", "container Running but service isn't ready", "pod restart-loops after edit", or "DMS and Firefly together". Refuse and route elsewhere for per-service config schemas, DOCA install, library-API questions, external NVIDIA services (BlueMan, HBN, SNAP, Virtio-net), or full Kubernetes-cluster ops — those belong to other skills.
NVIDIA/skills/skills/doca-telemetry-exporter Skill
2,853★ repoUse this skill when the user is doing hands-on DOCA Telemetry Exporter programming on a host where DOCA is installed — defining a doca_telemetry_exporter_schema, creating sources, picking counter/gauge/event types, running capability queries before assuming limits, registering schemas before the first emit, or debugging DOCA_ERROR_* failures from the exporter API. Trigger even when the user does not explicitly mention "DOCA Telemetry Exporter" or "doca_telemetry_exporter_*" — typical implicit phrasings include "publishing counters from my DOCA app", "emit returns AGAIN under bulk load", "consumer sees nothing but emit reports success", "NOT_FOUND on first submit", or "should I link the exporter or the telemetry service". Refuse and route elsewhere for the receiving DOCA Telemetry Service, plain stdout logging via doca_log, non-DOCA Prometheus scrape sinks, or real-time event subscription back into the app via doca-comch — those belong to other skills.
NVIDIA/skills/skills/doca-telemetry-utils Skill
2,853★ repoUse this skill when the user is invoking `doca_telemetry_utils` on a host with DOCA installed — discovering the diagnostic-counter schema, translating counter names to binary Data IDs, validating per-device counter support before committing a DOCA Telemetry exporter config, or reverse-resolving a captured Data ID. Trigger even when the user does not explicitly mention "doca_telemetry_utils" or "Data ID" — typical implicit phrasings include "my exporter ships but the collector sees nothing", "this metric silently drops downstream", "which counters does this BlueField expose", "translate this 0x... back to a counter name", "what do node / pcie_index / depth mean here", or "is this counter supported on this device before I commit it". Refuse and route elsewhere for developer-side collector / exporter library programming, DTS deployment, or DOCA install / repair — those belong to doca-telemetry, doca-public-knowledge-map, and doca-setup.
NVIDIA/skills/skills/doca-telemetry Skill
2,853★ repoUse this skill when reading **DOCA hardware-counter events** from a `doca_dev` via the per-domain DOCA Telemetry reader libraries — `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, `_pci`. This is the **counter-READER** surface — there is no NetFlow / IPFIX / local-socket collector framework here; the bundle previously framed it that way and that framing is wrong. Each domain ships its own `doca_telemetry_{domain}_*` API: cap-query `_cap_is_supported(devinfo)`, `_create()` on a `doca_dev`, `_start()`, then per-domain read / sample. Trigger even when the user does not say "DOCA Telemetry" — typical implicit phrasings: "read PCC counters from my BlueField app", "sample DPA counter exports", "expose PHY / PCI / DIAG counters from this `doca_dev`". Refuse and route elsewhere for the publishing / export side (`doca-telemetry-exporter`), DOCA Telemetry Service (DTS) as deployed (out of scope), NetFlow / IPFIX collectors, and plain stdout logging.
NVIDIA/skills/skills/dynamo-recipe-runner Skill
2,853★ repoSelect, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.
NVIDIA/skills/skills/i4h-workflow-create Skill
2,853★ repoCreate a new agentic env by forking an existing env. Use for new env/task scaffolding, not scene edits or baking.
NVIDIA/skills/skills/i4h-workflow-dataset-annotate Skill
2,853★ repoUse a VLM to verify whether each episode satisfies the env's task description. Use when the user asks to annotate, label episodes, filter demos, or gate finetuning on a success classifier.
NVIDIA/skills/skills/i4h-workflow-dataset-convert Skill
2,853★ repoConvert an agentic HDF5 recording into a LeRobot dataset (parquet, meta, videos). Use when asked to convert HDF5, prepare for training, or export to LeRobot; not for viewing — use [[i4h-lerobot-viz]].
NVIDIA/skills/skills/i4h-workflow-dataset-mimic Skill
2,853★ repoExpand an HDF5 recording by cloning trajectories with action/state noise. Use when asked to mimic, expand, or augment a dataset; not for recording new demos (use [[i4h-workflow-dataset-teleop]]).
NVIDIA/skills/skills/i4h-workflow-dataset-replay Skill
2,853★ repoReplay a recorded HDF5 episode inside Isaac Sim for visual verification. Use when the user asks to replay, play back, or step through an HDF5 recording.
NVIDIA/skills/skills/i4h-workflow-dataset-teleop Skill
2,853★ repoRecord episodes for an agentic env via teleoperation (keyboard, SO-ARM leader, or VR) into HDF5. Use when the user wants to teleop or record human demos.
NVIDIA/skills/skills/i4h-workflow-e2e Skill
2,853★ repoRun the full end-to-end agentic pipeline (record → mimic → annotate → replay → convert → visualize → finetune → validate). Use when asked to run the whole pipeline or do an e2e, smoke, or demo run.
NVIDIA/skills/skills/i4h-workflow-finetune Skill
2,853★ repoFine-tune a GR00T or openpi PI0 policy on a LeRobot dataset. Use when asked to finetune, train, or post-train a policy on demos; not for evaluating a checkpoint (use [[i4h-workflow-validate]]).
NVIDIA/skills/skills/i4h-workflow-scene-edit Skill
2,853★ repoEdit an env's scene in place — objects, cameras, task, success bounds, randomization. Use when asked to edit a scene or launch/run/open an env in edit mode (`--bridge`), incl. a just-created env.
NVIDIA/skills/skills/i4h-workflow-setup Skill
2,853★ repoVerify host requirements and run `workflows/agentic/setup.sh`. Use when asked to set up, install, or bootstrap the agentic workflow, or hits missing `.venv`, third-party checkout, or engine errors.
NVIDIA/skills/skills/i4h-workflow-validate Skill
2,853★ repoValidate, evaluate, or run i4h envs. Use for policy/checkpoint rollouts and scripted state-machine smoke runs.
NVIDIA/skills/skills/i4h-workflow Skill
2,853★ repoOverview of `workflows/agentic/` (IsaacLab-Arena + GR00T/openpi). Use when the user asks what i4h workflow is, what's supported, or where to start.
NVIDIA/skills/skills/launch-nemo-rl Skill
2,853★ repoPlaybook for launching, monitoring, stopping, and debugging NeMo-RL recipes on a Kubernetes cluster via the nrl-k8s CLI. Covers ephemeral vs long-lived RayCluster modes, iterating on runs, and debugging hung or failed training jobs.
Nemo mbridge perf moe optimization workflow
NVIDIA/skills/skills/nemo-mbridge-perf-moe-optimization-workflow Skill
2,853★ repoSystematic workflow for MoE training optimization in Megatron Bridge, based on the Megatron-Core MoE paper. Covers the Three Walls framework, parallel folding, recompute strategy, dispatcher choice, and CUDA-graph bring-up.
Nemo relay plugin observability
NVIDIA/skills/skills/nemo-relay-plugin-observability Skill
2,853★ repoUse this skill when choosing or configuring NeMo Relay observability through the built-in plugin, subscribers, or exporters, including raw ATOF events, ATIF trajectories, OpenTelemetry traces, OpenInference export, or custom event handling.
Physical ai infrastructure setup and resilient scaling
NVIDIA/skills/skills/physical-ai-infrastructure-setup-and-resilient-scaling Skill
2,853★ repoUse when the user wants to set up, scale, validate, or harden NVIDIA physical AI infrastructure for synthetic data generation workflows across local MicroK8s or Azure AKS, including Kubernetes clusters, inference endpoint deployment, OSMO deployment, workload submission readiness, and infrastructure failure recovery. Trigger keywords: physical ai infrastructure, resilient scaling, SDG infrastructure, microk8s, azure aks, NVCF deployment, NIM Operator, OSMO deploy, workflow scaling. Don't trigger for: OSMO log summarization or workload-only operations unless infrastructure setup, scaling, validation, or recovery is requested.
NVIDIA/skills/skills/tao-launch-workflow Skill
2,853★ repoShared launch intake for any TAO workflow or action. Use when the user wants to run TAO AutoML, train, evaluate, infer, export, generate TensorRT engines, or launch DEFT/workflow jobs on an execution platform.
NVIDIA/skills/skills/tao-run-automl Skill
2,853★ repoRun AutoML / hyperparameter optimization (HPO) for NVIDIA TAO networks using AutoMLRunner. Handles algorithm selection (bayesian, hyperband, asha, bohb, llm, hybrid, autoresearch), WandB experiment tracking, job execution on any TAO SDK platform, result interpretation, and per-rec custom evaluation hooks. Use when the user mentions TAO AutoML, hyperparameter optimization, HPO, automl, automl_settings, AutoMLRunner, tao_automl, bayesian search, hyperband, ASHA, LLM-guided search, autoresearch, or wants to tune training hyperparameters for any TAO network. Platform-agnostic — runs on any SDK (Brev, SLURM, Kubernetes, Docker).
NVIDIA/skills/skills/tao-run-on-kubernetes Skill
2,853★ repoKubernetes execution platform — submits TAO container jobs as single-pod k8s Jobs with NVIDIA GPU scheduling. Use when running on EKS / GKE / AKS / on-prem clusters with the NVIDIA GPU Operator installed, or when integrating TAO into an existing k8s-native ML platform.
NVIDIA/skills/skills/tao-run-on-local-docker Skill
2,853★ repoLocal or remote Docker execution for TAO SDK job containers using a Docker daemon with NVIDIA GPU runtime. Use when running TAO jobs on the current machine, a directly attached Docker host, or a remote GPU box exposed through DOCKER_HOST. Trigger phrases include "run locally", "local Docker", "remote Docker", "use my GPU", "run on my machine", "host Docker daemon".
NVIDIA/skills/skills/tao-run-platform Skill
2,853★ repoTAO Execution SDK for submitting and monitoring GPU training jobs on supported platforms (Brev, SLURM, local Docker, Kubernetes). Use when the user wants to run TAO jobs through the SDK, get job tracking, S3 I/O wrapping, multi-node distributed training, or platform-specific features that docker-run can't provide. Trigger phrases include "use the TAO SDK", "call tao_sdk", "AutoMLRunner", "ActionWorkflow", "Job handles", "S3 I/O wrapping", "TAO platform run".
NVIDIA/skills/skills/tao-setup-nvidia-gpu-host Skill
2,853★ repoHost setup for TAO GPU backends. Checks and, after user approval, installs NVIDIA driver branch 580, CUDA Toolkit 13.0, and NVIDIA Container Toolkit 1.19.0 for Docker/local-Docker and Kubernetes GPU worker hosts. The `--check-only` path works on any Linux distribution; `--install` automates debian-family (Ubuntu/Debian/Pop!_OS/Mint/Zorin/Raspbian), rhel-family (Fedora/RHEL/Rocky/AlmaLinux), and suse-family (openSUSE/SLES) hosts, and prints actionable manual-install steps for everything else. Use when the user asks to "set up an NVIDIA GPU host", "check TAO Docker GPU runtime", or prepare a Kubernetes GPU worker for TAO.
NVIDIA/skills/skills/vss-deploy-dense-captioning Skill
2,853★ repoUse this skill when deploying standalone RT-VLM dense captioning or calling its REST API (uploads, captions, streams, chat-completions, Kafka). Not for VSS profile deploy or video-search ingestion.
Vss deploy detection tracking 2d
NVIDIA/skills/skills/vss-deploy-detection-tracking-2d Skill
2,853★ repoUse this skill when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice. Trigger when the user says things like 'deploy rtvi-cv', 'start warehouse 2d', 'add a stream', 'check rtvi-cv health', or 'stop the perception container'. Not for VLM, embedding, or analytics — use the matching vss-* skill.
Vss deploy detection tracking 3d
NVIDIA/skills/skills/vss-deploy-detection-tracking-3d Skill
2,853★ repoDeploy and operate the RTVI-CV-3D microservice as MV3DT (`MODE=mv3dt`): per-camera DeepStream perception plus BEV Fusion over calibrated cameras. Supports the bundled sample dataset, custom video files, and RTSP streams, and chains to `vss-generate-video-calibration` when calibration is missing. Use `vss-deploy-profile` for the full warehouse blueprint and `vss-deploy-detection-tracking-2d` for single-camera 2D detection.
NVIDIA/skills/skills/vss-deploy-profile Skill
2,853★ repoUse to select, configure, deploy, verify, debug, or tear down a VSS profile (base, search, lvs, warehouse, edge). Not for standalone microservices — use the vss-deploy-* skill.
NVIDIA/skills/skills/vss-deploy-video-embedding Skill
2,853★ repoUse this skill when deploying, operating, or integrating the VSS 3.2 GA RT-Embed Video Embedding microservice. Covers Docker Compose bring-up, GPU and storage prerequisites, the `/v1` REST API (file uploads, text and video embeddings, live RTSP streams, health and metrics), Redis/Kafka/OTel integration, common failure modes, and teardown.
rohitg00/pro-workflow/skills/pro-workflow Skill
no license2,776★ repoComplete AI coding workflow system. Orchestration patterns, 18 hook events, 8 agents, cross-agent support, reference guides, and searchable learnings. Works with Claude Code, Cursor, and 32+ agents.
The same file is in 1 other repository
jeremylongshore/claude-code-plugins-plus-skills/skills/.curated/adk-agent-builder Skill
2,659★ repoScaffold production-ready AI agents on Google's Agent Development Kit (ADK): ReAct-style single agents, multi-agent orchestration (Sequential/Parallel/Loop), tool wiring, evaluation, and optional Vertex AI Agent Engine deployment. Use when building, scaffolding, or deploying ADK agents on Google Cloud, or when wiring ADK tools and orchestration patterns. Trigger with "build an ADK agent", "scaffold an agent on ADK", or "deploy to Agent Engine".
The same file is in 2 other repositories
jeremylongshore/claude-code-plugins-plus-skills/skills/.curated/adk-deployment-specialist Skill
2,659★ repo'Deploy and orchestrate Vertex AI ADK agents using A2A protocol. Manages AgentCard discovery, task submission, Code Execution Sandbox, and Memory Bank. Use when asked to "deploy ADK agent" or "orchestrate agents". Trigger with phrases like ''deploy'', ''infrastructure'', or ''CI/CD''.
The same file is in 1 other repository
jeremylongshore/claude-code-plugins-plus-skills/skills/.curated/adobe-ci-integration Skill
2,659★ repo'Configure CI/CD pipelines for Adobe integrations with GitHub Actions,
The same file is in 1 other repository
jeremylongshore/claude-code-plugins-plus-skills/skills/.curated/adobe-deploy-integration Skill
2,659★ repo'Deploy Adobe-powered applications to Vercel, Cloud Run, and Adobe App Builder
The same file is in 1 other repository
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/hyperflow/skills/deploy Skill
2,628★ repoUse when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/hyperflow/skills/hyperflow Skill
2,628★ repoUse when applying Hyperflow's orchestration doctrine in Codex, Antigravity, Grok, or another single-agent surface. Auto-invoke for non-trivial engineering work: build, implement, add, refactor, debug, fix, review, audit, plan, scope, design, brainstorm, ship, or deploy. Trigger with /hyperflow:hyperflow, "use hyperflow", "apply the doctrine", or automatically on any task-shaped message.
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/hyperflow/skills/workflow Skill
2,628★ repoUse when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use the portable workflow adapter. Trigger with /hyperflow:workflow, "run a workflow", "dynamic workflow", "big task", "large migration", "repo-wide audit".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-deploy Skill
2,628★ repoHyperflow ship phase. Use when the user is ready to release — verbs like ship, push, release, deploy, "cut a release", "ready to push". Runs pre-push gates (lint + typecheck + build + tests + security sweep), then asks before pushing. Never --no-verify, never force-push to main.
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/flux-migrate Skill
2,628★ repoBuild zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence. Use when asked to "write migration", "schema change", "add column", "rename table", "drop column", or "migrate safely".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/forge-infra Skill
2,628★ repoBuild production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/helm-arbiter Skill
2,628★ repoScope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/helm-brief Skill
2,628★ repoUse when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/helm-handoff Skill
2,628★ repoUse when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/helm-plan Skill
2,628★ repoUse when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/helm-recon Skill
2,628★ repoProduct landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/helm Skill
2,628★ repoHead of product — orchestrate the product team, write briefs, plan initiatives, hand off to Apex.
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/relay-deploy Skill
2,628★ repoSet up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/relay-docker Skill
2,628★ repoBuild production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/relay-ship Skill
2,628★ repoEnd-to-end ship workflow — merge base, run tests, review diff, bump version, commit, push, create PR. Use when asked to "ship", "push to main", "create a PR", "get this merged", or "deploy this branch".
jeremylongshore/claude-code-plugins-plus-skills/plugins/ai-agency/tonone/skills/touch-release Skill
2,628★ repoSet up mobile release pipeline — Fastlane, code signing, CI, beta distribution, versioning. Use when asked about "app store setup", "release pipeline", "fastlane", "beta distribution", or "signing".