agentsclimarketplace

Ship & operate

32,342 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

  • Vps deploy

    getpipher/skills/skills/vps-deploy/skills/vps-deploy Skill

    0★ repo

    Use when setting up new VPS projects, auditing VPS health, reviewing deploy workflows, debugging deployment issues, or hardening server security. Covers Docker, nginx, SSL, SSH, and CI/CD patterns for shared VPS infrastructure.

  • Solo automate

    kalepail/skills/skills/solo-automate Skill

    0★ repo

    Automate and integrate Solo through MCP, CLI, local HTTP API, hosted API v1, documentation resources, prompts, and solo:// deep links. Use when scripting Solo, discovering live schemas, configuring MCP clients, consuming Solo docs programmatically, or choosing an integration surface. Do not use for normal interactive Solo work already owned by a focused skill.

  • Release note

    AHappyAtlas/ai-knowledge-center/examples/multi-agent-skills/ai-knowledge/skills/release-note Skill

    0★ repo

    Local-first project context, verification gates, and repo-scoped MCP for coding agents.

  • Surface witness

    knowledgeco/airworthiness/skills/surface-witness Skill

    0★ repo

    Independently audit an implemented product surface against its declared constitution, state manifest, genealogy, responsive claims, and acceptance criteria. Use after a major interface milestone, design-system extraction, component-library migration, broad AI-generated UI work, before release, or whenever a product appears to be converging on generic AI or library defaults. Inspect rendered or executable artifacts before maker explanations; run logo-swap, monochrome, thumbnail, library-residue, mobile-mutation, copy-substitution, state, exception, and distinctiveness-budget tests; separate machine evidence from perceptual judgment; attempt to refute findings; disclose witness independence; and leave beauty, distinctiveness, brand, and ship verdicts pending for the operator rather than fabricating them.

  • Cloudflare email service

    Pdbjork/hermosskills-site/skills/cloudflare-email-service Skill

    no license0★ repo

    Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing). Use when building email sending (Workers binding or REST API), email routing, Agents SDK email handling, or integrating email into any app — Workers, Node.js, Python, Go, etc. Also use for email deliverability, SPF/DKIM/DMARC, wrangler email setup, MCP email tools, or when a coding agent needs to send emails. Even for simple requests like "add email to my Worker" — this skill has critical config details.

    The same file is in 1 other repository

  • Cloudflare

    Pdbjork/hermosskills-site/skills/cloudflare Skill

    no license0★ repo

    Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

    The same file is in 3 other repositories

  • Ecc tdd workflow

    Pdbjork/hermosskills-site/skills/ecc-tdd-workflow Skill

    no license0★ repo

    Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

    The same file is in 2 other repositories

  • Extend existing cron not duplicate

    Pdbjork/hermosskills-site/skills/extend-existing-cron-not-duplicate Skill

    no license0★ repo

    When the user asks for a recurring review cadence (weekly portfolio review, daily digest, monthly check-in) on a project that already has a cron job, ALWAYS inspect existing cron jobs first via `cronjob action='list'` and extend the matching job's prompt with `cronjob action='update'`. Never schedule a parallel cron that does overlapping work — duplicates the same data collection, double-delivers to chat, and complicates delivery semantics.

  • Static site ship

    Pdbjork/hermosskills-site/skills/static-site-ship Skill

    no license0★ repo

    Ship a redesigned (or new) static website end-to-end on a VPS — design the site, build it, validate it, deploy to a static mirror under /var/www or equivalent, smoke-test nginx (with the right Host header) AND the backend capture service, write a handoff report, and ping the user. Load when the user asks to "redesign", "build", "ship", "deploy", or "publish" a website, especially a research/education/foundation/nonprofit public-facing site where privacy-by-default, consent-first forms, and "no false claims" discipline matter. Skip for SPA / SSR app deploys (Next.js, Vite, etc.) — those have their own build pipelines. Skip for hosted-platform-only deploys (Vercel/Netlify/Cloudflare Pages with no VPS mirror).

  • Stripe go live workflow

    Pdbjork/hermosskills-site/skills/stripe-go-live-workflow Skill

    no license0★ repo

    Operational workflow for taking a working test-mode Stripe integration to live AND for verifying an already-live integration end-to-end. Covers the Dashboard walkthrough, the "never see the live key" safety rule, the test-mode dry run, the live deploy ritual, and the Express/Node verify-the-pipes ritual. Load when a user says "go live," "flip to live," "launch payments," "we're ready for real cards," "real money now," "production time," "I need money," "verify the live Stripe pipes," "smoke test the checkout," or "show me money," or has either a working test-mode Stripe integration that needs to ship OR an already-live Express/Worker integration that needs end-to-end verification. Default assumption when a user says "go live" is wrong: the integration may already be live from a previous session. Always audit state first. Skip for API design questions, key-management theory, or pure code-review tasks — those are covered by `stripe-best-practices`.

  • Routine architect

    ribbons-digital/skills/routine-architect Skill

    0★ repo

    Use this skill to design a recurring routine for non-coding work before running it. Invoke when the user wants to turn repetitive non-coding work into an autonomous routine (daily digests, inbox or channel triage, news or market monitoring, knowledge-base or vault upkeep, content pipelines, data hygiene in external tools), asks to "design a routine", "automate this workflow", "do this every morning/day/week", or keeps manually re-issuing the same non-coding prompt. Also invoke proactively, without being asked, when the agent notices the same non-coding request recurring across 3 or more sessions or items - pause and propose a routine before continuing item by item. For repetitive coding tasks in a repository (migrations, test or lint burn-downs, CI triage), use loop-architect instead. The deliverable is a reviewed Routine Card (goal, exit or cadence, iteration unit, verification, state, stop conditions, human gates, trigger, write surfaces) plus a runnable routine prompt.

  • Using ops method

    gulmezeren2-byte/industrial-engineering-ai-skills/skills/using-ops-method Skill

    0★ repo

    Entry point for any operations or supply-chain data analysis - routes the work through a fixed method (brief, data contract, honest metrics, driver decomposition, stress test, decision memo) and calls the specialized skills at the right step. Use when starting any ops analysis, KPI study, delivery/forecast/inventory question, operasyon analizi, veri analizi, or when unsure which ops skill applies. Differentiator - enforces sequence and validation, not just tool choice.

  • Weekly ops report

    gulmezeren2-byte/industrial-engineering-ai-skills/skills/weekly-ops-report Skill

    0★ repo

    Turn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision. Use when the user mentions weekly report, haftalık rapor, yönetim raporu, ops review, KPI summary, or asks to summarize operational data for managers. Differentiator - contract-first reporting with plain-language findings and driver decomposition, never a chart dump.

  • Azure devops cli

    angpysha/api2skill/.agents/skills/azure-devops-cli Skill

    0★ repo

    Azure DevOps operations via Azure CLI (azure-devops extension). Configure org/project from pipeline.manifest.json, create PRs after Phase 9 approval, list pipelines, and manage work items. Use when pr.type is azure-devops or azure-pipelines/ is present.

  • Land

    ohyesgocool/feature-loop/skills/land Skill

    0★ repo

    Post-merge landing: take merged MR(s) to verified-in-production by executing the project's landing runbook — watch the main pipeline(s) to green, apply or hand off migrations, deploy in the runbook's order, then canary-verify (health checks, smoke checks) before declaring shipped. Runbook-driven: reads docs/landing.md; on first run it drafts one by inspecting the repo (CI config, migrations, health endpoints) and confirms it with you. Every step is tagged [agent] (executed directly) or [human] (prod-locked — handed to you as exact commands and waited on, never assumed). Hard stops: red pipeline, failed migration, failed canary, unconfirmed human step. Never auto-rolls-back; prepares the revert and asks. Use when: "land this", "deploy the merge", after /ship-feature merges, "take it to prod", running post-merge follow-ups (migrations, deploy order, canary).

  • Ship feature

    ohyesgocool/feature-loop/skills/ship-feature Skill

    0★ repo

    Loop engineering for AI coding agents: plan → build → MR → independent AI review → fix → re-review until clean, with a merge gate and a self-learning blind-spot ledger. Agent Skills format, Claude Code native, MIT.

  • Post deploy smoke

    jcdavis131/cursor-agent-skills/skills/post-deploy-smoke Skill

    0★ repo

    After a deploy, confirm the live URL actually serves the expected content (not just that the API returned 200) by polling it with a bounded retry loop that greps for an expected string per URL. Use after any deploy to verify propagation, after a rebrand/rename to confirm the new content is live, or before telling the user a deploy is "done".

  • Readiness report

    jcdavis131/cursor-agent-skills/skills/readiness-report Skill

    0★ repo

    Delivers a structured production-readiness handoff — numbered items needing operator input, each classified pre-existing vs introduced and tagged with repo issue IDs, plus exact verification commands. Use when a multi-task build is ready for operator review, before a deploy gate, or when decisions are the operator's to make.

  • Website resilience

    paulgrape/skill-auditor/templates/website-resilience Skill

    0★ repo

    Graceful-failure essentials for a website — custom error pages with correct status codes, 503 maintenance pages, graceful degradation without JavaScript, web app manifest, and uptime monitoring. Use when building error pages, offline behaviour, or resilience of a site.

  • Automation test cases

    vaibhavsaxena022/skills/automation-test-cases Skill

    0★ repo

    Design UI/API automation test cases that are stable and maintainable. Use when writing or reviewing Selenium / REST Assured / Playwright automation. Covers selector strategy, independence, data handling, and what to automate.

  • Dockerize service

    vaibhavsaxena022/skills/dockerize-service Skill

    0★ repo

    Generate a production-ready Dockerfile (and optional docker-compose) for a service. Use when asked to containerize or dockerize a Java (Maven/Gradle) or Python service. Produces a small, multi-stage, non-root image.

  • Feature workflow

    vaibhavsaxena022/skills/feature-workflow Skill

    0★ repo

    Drive a feature from request to reviewed code in disciplined steps. Use for non-trivial feature work. Sequences understand → explore → design → implement-in-small-steps → test → self-review, checking in at the right moments.

  • Incident postmortem

    vaibhavsaxena022/skills/incident-postmortem Skill

    0★ repo

    Write a blameless postmortem after a production incident. Use when documenting an outage or serious bug. Captures timeline, impact, root cause, and concrete follow-up actions — focused on systems, not people.

  • Observability

    vaibhavsaxena022/skills/observability Skill

    0★ repo

    Add production observability to a service. Use when a service is hard to debug in prod or lacks logging/metrics/tracing. Adds structured logs, key metrics, and trace context — without noise.

  • Workflow mapper

    SamyakJhaveri/loam/cultivation/marketplace/business-process/skills/workflow-mapper Skill

    0★ repo

    Maps business processes from natural language descriptions into structured workflows, identifies automation opportunities using the GREEN/YELLOW/RED framework, and generates visual workflow diagrams. Use when user says "map my workflow", "describe my process", "where should I automate", "workflow audit", or describes any business process.

  • Auto phase

    SamyakJhaveri/loam/seed/.claude/skills/auto-phase Skill

    0★ repo

    Autonomous multi-phase release execution. Reads a PHASE-PLAN.md with stages 1-N and executes them end-to-end, running validation + critique per stage, committing with clean scope, and advancing automatically. Halts only when a validation gate fails twice or a critique surfaces an unresolvable issue. Use for multi-stage release plans, phased restructures, or any numbered-phase execution. NOT for single-stage work (use /ship), plan creation (use brainstorming), or work without a written phase plan. Use when you have a numbered-phase plan ready for execution.

  • Critique swarm

    SamyakJhaveri/loam/seed/.claude/skills/critique-swarm Skill

    0★ repo

    Parallel adversarial critique with 4 specialized agents plus synthesis. Use before merging a feature branch, before committing a complex plan, or when you want independent multi-angle review of a plan or implementation. Complements /multi-review (which reviews code quality) by reviewing plan/scope quality. NOT for single-file trivial changes (use /validate), standard code review (use /multi-review), or post-implementation shipping (use /ship).

  • Ship

    SamyakJhaveri/loam/seed/.claude/skills/ship Skill

    0★ repo

    Orchestrates the full shipping pipeline in strict order. Runs session-critique, then validate (both waves), then commit, then PR. Use when work is complete and ready to ship. Enforces ordering to prevent premature commits and skipped critiques. Accepts optional argument 'critique-only' to run just the critique step. NOT for mid-implementation checks (use /validate), code review without shipping (use /multi-review), or committing without the full pipeline (use /commit directly only if critique + validate already passed).

  • Build and release

    ats4321/claude-engineering-skills/skills/build-and-release Skill

    0★ repo

    Build systems, packaging, and release discipline for any repo. Load when building, packaging, publishing, or deploying; when discovering how a repo builds (npm/pnpm scripts, pyproject, Makefile, cargo); when working with entry points and editable installs; when publishing multi-package or aliased npm artifacts and coordinating dist-tags; when deployment shape (static vs server) constrains the build; or when verifying a build before declaring a task done. Includes release checklists and dry-run discipline.

  • Change control

    ats4321/claude-engineering-skills/skills/change-control Skill

    0★ repo

    Safe-change discipline for editing ANY repository. Auto-load before editing files, fixing bugs, refactoring, committing, pushing, publishing, deleting, uploading, or running any irreversible command. Covers read-before-edit, smallest-correct-diff at the root cause (not the symptom), checking every caller before changing a shared function, verifying flag/command behavior (e.g. DRY_RUN) before destructive actions, commit hygiene, when to branch, and never presenting unverified work as done. Trigger keywords: edit, fix, refactor, commit, push, publish, release, delete, migrate, rename, deploy, "make a change", "apply the fix".

  • Observability and diagnostics

    ats4321/claude-engineering-skills/skills/observability-and-diagnostics Skill

    0★ repo

    Make systems diagnosable BEFORE they fail — structured logging, honest levels, actionable errors, surfaced skips, and reconstructable runs. Auto-load when adding or reviewing logging, error messages, metrics, or health checks; when a production/runtime failure could not be diagnosed from available output; when asked "add logging" or "why can't we tell what happened"; or when designing what a long-running job or agent should record. NOT for diagnosing a live failure (debugging-playbook — this skill provides the evidence that playbook consumes) and NOT for measuring speed (performance-engineering).

  • Release check

    yousefkadah/laravel-ai-kit/skills/release-check Skill

    0★ repo

    Use right before opening a pull request or shipping a change. A final gate covering tests, formatting, secrets, tenant-safety, and post-deploy steps.

  • Ci cd and automation

    kulapoo/opencode-agent-harness/.opencode/skills/ci-cd-and-automation Skill

    0★ repo

    Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

  • Git workflow and versioning

    kulapoo/opencode-agent-harness/.opencode/skills/git-workflow-and-versioning Skill

    0★ repo

    Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

  • Observability and instrumentation

    kulapoo/opencode-agent-harness/.opencode/skills/observability-and-instrumentation Skill

    0★ repo

    Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

  • Shipping and launch

    kulapoo/opencode-agent-harness/.opencode/skills/shipping-and-launch Skill

    0★ repo

    Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

  • Pre ship

    Syo-M/codex-frontend-skills/.agents/skills/pre-ship Skill

    0★ repo

    Pre-merge verification covering scope, typecheck, lint, affected tests, security, accessibility, and a single pass or fail report. 日本語の依頼例:「出荷前チェック」「マージ前確認」「完成か確認」「PR前チェック」。

  • Pre ship

    Syo-M/codex-frontend-skills/plugins/codex-frontend-skills/skills/pre-ship Skill

    0★ repo

    Pre-merge verification covering scope, typecheck, lint, affected tests, security, accessibility, and a single pass or fail report. 日本語の依頼例:「出荷前チェック」「マージ前確認」「完成か確認」「PR前チェック」。

  • Setup domain ops

    cat2000/domain-knowledge-ops/.cursor/skills/setup-domain-ops Skill

    0★ repo

    One-time setup: credentials, company/business intro → industry module template (confirm), Confluence space URL(s), Jira board id(s). Writes team-roots.json as v3 (libraries + teams mounting them). See docs/TEAM_ROOTS_V3.md.

  • Premise review

    finnfotschki/mindful-agent-collaboration/skills/premise-review Skill

    0★ repo

    Periodically review the premises steering recurring human-agent work—goals, criteria, thresholds, readiness evidence, reliability assumptions, standing rules, memory, routing, delegation modes, gates, and resilience—on an output-independent trigger. Use at calendar or milestone boundaries, after long-running automation, before scaling a workflow, or when rules and memory have accumulated. Propose changes for human decision; never treat successful output as proof that the frame remains appropriate.

  • Task profile

    finnfotschki/mindful-agent-collaboration/skills/task-profile Skill

    0★ repo

    Profile a non-trivial task step by step after any required workflow-readiness screen. Route deterministic operations to exact tools; rate structure, verifiability, and judgment share; then apply separate architecture and governance gates to assign autonomous, controlled, assistive, or human-final. Use when deciding how much work an agent may perform, decomposing mixed workflows, planning recurring delegation, or responding to requests to automate or handle a consequential multi-step task.

  • Workflow readiness

    finnfotschki/mindful-agent-collaboration/skills/workflow-readiness Skill

    0★ repo

    Screen a recurring workflow before task profiling or automation by checking task-fit, task-specific agent reliability, effective human intervention points, and system resilience. Use before creating recurring agent runs, expanding a pilot, granting end-to-end workflow ownership, or deciding whether an automation initiative is mature enough to profile. Return ready for task profiling, pilot/assistive only, or not ready; unknown reliability or resilience never supports autonomous delegation.

  • Deploy checklist

    IcodeNet/agent-skills/skills/deploy-checklist Skill

    0★ repo

    Pre-deploy and release checklist with rollback planning. Use when deploying, releasing, shipping, or preparing a pre-deploy review. Do not use for coding the feature itself or for live incident command (use incident-response).

  • Incident response

    IcodeNet/agent-skills/skills/incident-response Skill

    0★ repo

    Handles live production incidents and postmortems. Use when production is down, degraded, or on fire; when coordinating an outage; or when writing a postmortem. Do not use for routine bug fixes in development (use debug).

  • Observability

    IcodeNet/agent-skills/skills/observability Skill

    0★ repo

    Design metrics, logs, traces, alerts, and SLOs alongside a feature or service. Use when adding observability, defining SLIs/SLOs, designing dashboards or alerts, or when a feature is about to ship with no way to tell if it works in production. Do not use for handling a live outage (use incident-response).

  • Release

    IcodeNet/agent-skills/skills/release Skill

    0★ repo

    Prepare a release: decide the semantic version bump, write the changelog / release notes from actual changes, and tag. Use when releasing or publishing a package or service version, cutting a release branch, or when asked "what version should this be" or to write release notes. Do not use for the deploy execution itself (use deploy-checklist).

  • Ci cd pipelines

    shinzoxD/knackbox/skills/coding/ci-cd-pipelines Skill

    0★ repo

    Design and review CI/CD pipelines for speed, safety, and clear failure signals. Use whenever the user edits GitHub Actions, GitLab CI, Jenkinsfiles, or asks how to structure tests, builds, caches, deploy gates, and rollbacks in continuous integration.

  • Container review

    shinzoxD/knackbox/skills/coding/container-review Skill

    0★ repo

    Review Dockerfiles and container configs for size, security, and operability. Use whenever the user shares a Dockerfile, compose file, Kubernetes image config, or asks how to harden, slim, or debug a container build.

  • Database migrations

    shinzoxD/knackbox/skills/coding/database-migrations Skill

    0★ repo

    Plan and review database schema migrations for safety and rollback. Use whenever the user writes migrations, alters tables, backfills data, adds indexes, or asks how to deploy schema changes without downtime or lock pain.

  • Helm chart scaffolding

    shinzoxD/knackbox/skills/coding/helm-chart-scaffolding Skill

    0★ repo

    Scaffold and review Helm charts with safe defaults for values, templates, and hooks. Use whenever the user asks for a Helm chart, Chart.yaml, values.yaml production review, Helm upgrade hooks, or packaging a service for Helm install/upgrade.

  • Kubernetes review

    shinzoxD/knackbox/skills/coding/kubernetes-review Skill

    0★ repo

    Review Kubernetes manifests and Helm values for security, reliability, and operability. Use whenever the user shares Deployment, Service, Ingress, StatefulSet, Helm charts, or asks about probes, RBAC, resource limits, network policies, or production-ready k8s YAML.

  • Logging observability

    shinzoxD/knackbox/skills/coding/logging-observability Skill

    0★ repo

    Design logging, metrics, and tracing that operators can use under pressure. Use whenever the user asks about structured logs, metrics, OpenTelemetry, dashboards, SLIs/SLOs, alerting, or how to instrument a service for production debugging.

  • Observability alerts

    shinzoxD/knackbox/skills/coding/observability-alerts Skill

    0★ repo

    Design actionable alerts that page humans only for real pain. Use whenever the user writes alert rules, fixes alert fatigue, designs on-call notifications, escalations, or SLO burn alerts.

  • Terraform review

    shinzoxD/knackbox/skills/coding/terraform-review Skill

    0★ repo

    Review Terraform and OpenTofu configuration and plans for blast radius, state risk, IAM overreach, and safer apply order. Use whenever the user shares .tf files, a terraform plan, asks if apply is safe, or reviews infrastructure-as-code modules and state backends.

  • Incident postmortems

    shinzoxD/knackbox/skills/documents/incident-postmortems Skill

    0★ repo

    Write blameless incident postmortems with timeline, impact, root cause, and action items. Use whenever the user asks for a postmortem, RCA, incident write-up, outage report, or lessons learned after a production failure — even from rough Slack notes or pager logs.

  • Release notes

    shinzoxD/knackbox/skills/documents/release-notes Skill

    0★ repo

    Write clear user-facing and developer release notes from commits, PRs, and changelogs. Use whenever the user asks for release notes, a changelog entry, what's new for a version, ship notes for customers or engineers, or a summary of changes between tags — even if they only paste commit subjects or merged PR titles.

  • Runbook writing

    shinzoxD/knackbox/skills/documents/runbook-writing Skill

    0★ repo

    Write operational runbooks that on-call engineers can follow under stress. Use whenever the user asks for a runbook, playbook, ops procedure, alert response guide, or how to document incident response steps for a system.

  • Sla slo writing

    shinzoxD/knackbox/skills/documents/sla-slo-writing Skill

    0★ repo

    Write SLAs and SLOs that operations can measure and support can explain. Use whenever the user drafts service levels, uptime commitments, error budgets, customer-facing availability language, or internal reliability targets.

  • Incident comms

    shinzoxD/knackbox/skills/writing/incident-comms Skill

    0★ repo

    Write customer and stakeholder communications during incidents. Use whenever the user needs a status page update, outage notice, customer incident email, or internal incident broadcast — separate from the engineering postmortem write-up.

  • Press release

    shinzoxD/knackbox/skills/writing/press-release Skill

    0★ repo

    Write press-style announcements with a lead, facts, and quotes without hype fluff. Use whenever the user needs a press release, media announcement, wire-style launch note, or journalist-facing company news.