agentsclimarketplace

Ship & operate

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

  • Docker expert

    AtulPurohit/Antigravity-Awesome-Skills/skills/docker-expert Skill

    no license5★ repo

    Build optimized, secure Docker images with multi-stage builds. Configure Docker Compose for full development and production stacks.

  • Feature flag architecture

    AtulPurohit/Antigravity-Awesome-Skills/skills/feature-flag-architecture Skill

    no license5★ repo

    Professional Feature Flag Architecture Expert skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.

  • Gcp engineer

    AtulPurohit/Antigravity-Awesome-Skills/skills/gcp-engineer Skill

    no license5★ repo

    Professional Gcp Engineer skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.

  • Github actions

    AtulPurohit/Antigravity-Awesome-Skills/skills/github-actions Skill

    no license5★ repo

    Professional Github Actions Expert skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.

  • Gitlab ci

    AtulPurohit/Antigravity-Awesome-Skills/skills/gitlab-ci Skill

    no license5★ repo

    Professional Gitlab Ci Expert skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.

  • Helm packager

    AtulPurohit/Antigravity-Awesome-Skills/skills/helm-packager Skill

    no license5★ repo

    Professional Helm Packager Expert skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.

  • Infrastructure as code

    AtulPurohit/Antigravity-Awesome-Skills/skills/infrastructure-as-code Skill

    no license5★ repo

    Professional Infrastructure As Code Expert skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.

  • Kubernetes operator

    AtulPurohit/Antigravity-Awesome-Skills/skills/kubernetes-operator Skill

    no license5★ repo

    Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.

  • Mobile ci cd

    AtulPurohit/Antigravity-Awesome-Skills/skills/mobile-ci-cd Skill

    no license5★ repo

    Automate mobile app build, test, and deployment pipelines for iOS and Android using Fastlane, EAS Build, or GitHub Actions.

  • Monitoring setup

    AtulPurohit/Antigravity-Awesome-Skills/skills/monitoring-setup Skill

    no license5★ repo

    Set up comprehensive monitoring with Prometheus, Grafana, and alerting. Covers metrics, dashboards, SLOs, and on-call runbooks.

  • Postmortem writer

    AtulPurohit/Antigravity-Awesome-Skills/skills/postmortem-writer Skill

    no license5★ repo

    Professional Postmortem Writer Expert skill. Orchestrate technical collaboration, design reviews, sprint planning, and system diagnostics.

  • Release manager

    AtulPurohit/Antigravity-Awesome-Skills/skills/release-manager Skill

    no license5★ repo

    Professional Release Manager Expert skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.

  • Semantic versioning

    AtulPurohit/Antigravity-Awesome-Skills/skills/semantic-versioning Skill

    no license5★ repo

    Professional Semantic Versioning Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.

  • Serverless architecture

    AtulPurohit/Antigravity-Awesome-Skills/skills/serverless-architecture Skill

    no license5★ repo

    Professional Serverless Architecture Expert skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.

  • Sre runbook

    AtulPurohit/Antigravity-Awesome-Skills/skills/sre-runbook Skill

    no license5★ repo

    Professional Sre Runbook Expert skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.

  • Terraform builder

    AtulPurohit/Antigravity-Awesome-Skills/skills/terraform-builder Skill

    no license5★ repo

    Build infrastructure as code with Terraform. Covers module design, state management, AWS/GCP/Azure resources, and production-grade practices.

  • Cds ship

    Enakoneschniy/claude-dev-stack/vendor/cds-workflow/skills/cds-ship Skill

    5★ repo

    Create PR, run review, and prepare for merge after verification passes

  • Gsd ship

    Enakoneschniy/claude-dev-stack/vendor/cds-workflow/skills/gsd-ship Skill

    5★ repo

    [DEPRECATED] Use /cds-ship instead

  • Rollback

    benmarte/autoimprove/skills/rollback Skill

    5★ repo

    Emergency cleanup of all autoimprove experiment worktrees. Use this if a session was interrupted, Claude crashed mid-experiment, or you want to abort the loop and clean up all branches and worktrees.

  • Loop workflow planner

    ytvee-dev/webdev-agent-kit/skills/loop-workflow-planner Skill

    5★ repo

    Define a platform-neutral bounded loop for standard or deep work using measurable acceptance criteria, verification, retry limits, independent review, memory, and stop conditions. Skip lookups, tiny edits, and one-off explanations.

  • Dockerfile optimizer

    basejb/skills/skills/dockerfile-optimizer Skill

    no license5★ repo

    Dockerfile을 빌드 속도·이미지 크기·보안·배포 안정성 관점에서 분석하고 개선안을 제안하는 스킬. "Dockerfile 점검/최적화/리뷰", "이미지 크기 줄여줘", "빌드 느려", "도커 보안 점검", "root 사용 경고" 같은 요청에 발동. Node.js· Python·Go 프로젝트의 패키지 매니저를 lockfile로 감지하여 multi-stage· 레이어 캐시·non-root 사용자·.dockerignore 등을 자동 진단한다.

  • Devops

    DongDuong2001/pudo-code-system/skills/devops Skill

    5★ repo

    Modular, scalable, automated development intelligence.

  • Docker

    DongDuong2001/pudo-code-system/skills/devops/docker Skill

    5★ repo

    Modular, scalable, automated development intelligence.

  • Github actions

    DongDuong2001/pudo-code-system/skills/devops/github-actions Skill

    5★ repo

    Modular, scalable, automated development intelligence.

  • Gitlab ci

    DongDuong2001/pudo-code-system/skills/devops/gitlab-ci Skill

    5★ repo

    Modular, scalable, automated development intelligence.

  • Jenkins

    DongDuong2001/pudo-code-system/skills/devops/jenkins Skill

    5★ repo

    Modular, scalable, automated development intelligence.

  • Kubernetes

    DongDuong2001/pudo-code-system/skills/devops/kubernetes Skill

    5★ repo

    Modular, scalable, automated development intelligence.

  • Terraform

    DongDuong2001/pudo-code-system/skills/devops/terraform Skill

    5★ repo

    Modular, scalable, automated development intelligence.

  • Kr patent full workflow

    lsj4232/KR_PATENT_SKILL/kr-patent-full-workflow Skill

    5★ repo

    한국 특허 명세서 작성의 전체 워크플로우를 처음부터 끝까지 순차 실행하는 오케스트레이터 메타 스킬. 다른 kr-patent-* 스킬들(inventor-meeting, symbol-design, spec-drafting, definition-insertion, embodiment-addition, consistency-check, docx-builder, skill-updater)을 적절한 순서로 호출하여 발명자 IDS 입력 → 권리범위 보강 → 최종 docx 출력까지 한 흐름으로 진행. "/full", "처음부터 끝까지", "전체 워크플로우", "명세서 한 건 처음부터", "풀 프로세스", "전체 자동", "end-to-end", "토탈 패키지" 같은 표현이 보이면 사용. 사용자가 어느 단계부터 시작해야 할지 자동 판단(IDS만 있으면 미팅부터, 청구항 확정됐으면 부호 설계부터, 본문 1차 초안 있으면 권리범위 보강부터). 각 단계에서 중요 체크포인트는 사용자 승인 받음.

  • Create agentic workflow

    richfrem/agent-plugins-skills/plugins/agent-scaffolders/skills/create-agentic-workflow Skill

    5★ repo

    Scaffolds a Copilot GitHub agent, an agent that runs in GitHub Actions, a GitHub workflow agent, or a GitHub Agentic Workflow (gh-aw) from an existing skill. Supports three target configurations: Target A (Custom Copilot agent), Target B (GitHub Agentic Workflow), and Target C (CI/CD Smart Failure agent).

  • Create azure agent

    richfrem/agent-plugins-skills/plugins/agent-scaffolders/skills/create-azure-agent Skill

    5★ repo

    Deploys a skill as an Azure AI Foundry hosted agent. NOT for Docker runtime skills (use `create-docker-skill`) and NOT for MCP server integrations (use `create-mcp-integration`).

  • Create docker skill

    richfrem/agent-plugins-skills/plugins/agent-scaffolders/skills/create-docker-skill Skill

    5★ repo

    Scaffolds an agent skill with a Docker runtime environment. NOT for normal local skills (use `create-skill`) and NOT for Azure hosted agents (use `create-azure-agent`).

  • Create github action

    richfrem/agent-plugins-skills/plugins/agent-scaffolders/skills/create-github-action Skill

    5★ repo

    Scaffolds a deterministic GitHub Actions CI/CD workflow YAML. NOT for scaffolding interactive agentic workflows (use `create-agentic-workflow`) and NOT for local event-driven hooks (use `create-hook`).

  • Business workflow doc

    richfrem/agent-plugins-skills/plugins/exploration-cycle-plugin/skills/business-workflow-doc Skill

    5★ repo

    Generate Mermaid flowcharts documenting business processes, state machines, and workflow logic from session captures. Use when you need to map multi-step processes, approval flows, user journeys, or decision trees during exploration. Trigger with "map this workflow", "create a process diagram", "flowchart the business process", "document this workflow", or "visualize the state machine".

  • Exploration workflow

    richfrem/agent-plugins-skills/plugins/exploration-cycle-plugin/skills/exploration-workflow Skill

    5★ repo

    SME-facing orchestrator for the Business Exploration Loop. Supports 4 session types (greenfield, brownfield, discovery-only, spike) with adaptive phase selection. Manages state via exploration-dashboard.md, enforces phase gates, and routes to child skills in sequence. Phases can be skipped based on session type. Single canonical entry point — invoke at the start of any exploration session or to resume an in-progress session. Trigger phrases: "start an exploration", "let's explore this idea", "resume my exploration", "where did we leave off", "start discovery".

  • App store release prep

    SkillMedev/skills/skills/app-store-release-prep Skill

    5★ repo

    Produce a reproducible signing, versioning, and store-declaration pipeline so an iOS or Android build passes App Store Connect / Play Console submission. Use when building or uploading a distribution .ipa/.aab, fixing signing/provisioning-profile or entitlement errors, bumping CFBundleVersion/versionCode, filling App Privacy / Data safety forms or PrivacyInfo.xcprivacy, wiring Fastlane lanes, or diagnosing a store rejection. Do NOT use for general (non-mobile) release steps like changelogs, tagging, or backend deploys - use prepare-release instead; do NOT use for store listing titles, descriptions, or keywords - use app-store-copy instead.

    The same file is in 1 other repository

  • Crisis comms external

    SkillMedev/skills/skills/crisis-comms-external Skill

    5★ repo

    Drafts and sequences external communications during an incident or crisis - a first statement within the hour, acknowledge-what-you-know-without-speculating discipline, a single-spokesperson rule, channel sequencing from status page to email to social, and a legal-review escalation boundary, with severity-tiered statement templates. Use when a user says "we have an outage and customers are asking questions", "we had a data breach, what do we say publicly", "draft a public statement about this incident", "the story is blowing up on social, how do we respond", or "when do we need legal to review this statement". Do NOT use for routine technical status posts during normal-severity incidents - use status-page-update instead - for the internal writeup after resolution - use postmortem-writer instead - or for calming one angry customer - use refund-deescalation instead.

    The same file is in 1 other repository

  • Data quality

    SkillMedev/skills/skills/data-quality Skill

    5★ repo

    Designs layered data quality checks across completeness, validity, consistency, uniqueness, timeliness, and accuracy, with severity tiers, freshness SLAs, and anomaly baselines wired into dbt and CI. Use when someone asks "how do I stop bad data reaching dashboards", "set up dbt tests for this model", "our pipeline loaded duplicate rows again", "what data quality checks should this table have", or "how fresh does this source need to be". Do NOT use for detecting distribution drift in ML features and predictions - use data-drift-monitor instead; for one-off exploration and profiling of a new dataset - use eda-playbook instead; for infrastructure and application telemetry - use observability-stack instead; for removing personal data from datasets - use pii-scrubber instead.

    The same file is in 1 other repository

  • Docker compose wizard

    SkillMedev/skills/skills/docker-compose-wizard Skill

    5★ repo

    Produces production-minded docker-compose configurations - pinned images, healthchecks with real intervals, health-gated startup ordering, named volumes, explicit networks, and env-file secrets - plus the matching .env.example. Use when someone asks "write a compose file for this stack", "why does my app start before the database is ready", "how do I add a healthcheck", "my compose setup works on my machine but not in CI", or is reviewing a docker-compose.yml before it ships. Do NOT use for orchestrating across multiple hosts or cluster workloads - use kubernetes-basics instead; for provisioning the underlying cloud infrastructure - use terraform-expert instead; for CI pipelines that build and push the images - use github-actions instead; for auditing how secrets are stored and rotated - use secrets-hygiene instead.

    The same file is in 1 other repository

  • Escalation summary

    SkillMedev/skills/skills/escalation-summary Skill

    5★ repo

    Writes a tight escalation summary to engineering or management with a one-line headline, quantified customer impact, repro steps, prior attempts, and a single clear ask. Use when someone says "I need to escalate this ticket", "write this up for engineering", "this bug needs eng eyes", or a support issue must leave the queue for specialist action. Do NOT use for replying to the customer - use support-ticket-reply instead; do NOT use for assigning incident severity and coordinating an active outage - use sev-triage instead; do NOT use for the after-the-fact incident writeup - use postmortem-writer instead.

    The same file is in 1 other repository

  • Feature flags

    SkillMedev/skills/skills/feature-flags Skill

    5★ repo

    Designs feature-flag systems and lifecycle policy - flag taxonomy (release, ops/kill-switch, experiment, permission), percentage rollouts with stable bucketing, safe defaults, and mandatory removal deadlines so flags don't rot into dead code. Use when someone asks "how should I roll this out behind a flag", "kill switch vs feature flag", "how do I do a percentage rollout", "we have hundreds of stale flags", or is wiring up LaunchDarkly or a homegrown flag service. Do NOT use for designing the A/B test analysis itself - use ab-test-analyzer instead - and do NOT use for CI/CD pipeline gating - use github-actions instead.

  • Github actions

    SkillMedev/skills/skills/github-actions Skill

    5★ repo

    Designs and hardens GitHub Actions CI/CD - pipelines that hit a sub-10-minute PR feedback budget through caching and parallelism, with least-privilege security and safe deploy gates. Use when someone asks "why is my CI so slow", "how do I cache node_modules properly", "set up a deploy workflow", "is pull_request_target safe here", or wants a workflow written or reviewed. Do NOT use for provisioning the cloud infrastructure the pipeline deploys to - use terraform-expert instead; do NOT use for Vercel-specific deploy flows - use vercel-deploy-pipeline instead; for secret storage policy beyond CI, use secrets-hygiene.

    The same file is in 1 other repository

  • Kubernetes basics

    SkillMedev/skills/skills/kubernetes-basics Skill

    5★ repo

    Writes production-ready Kubernetes manifests - Deployments with correct resource requests/limits, readiness/liveness/startup probes, PodDisruptionBudgets, safe rollouts, and graceful shutdown. Use when someone asks "write a Deployment for my service", "my pods keep getting OOMKilled", "why do I get 502s during deploys", "what should my resource limits be", or "why did my pod restart in a loop". Do NOT use for local multi-container development environments - use docker-compose-wizard instead; for CI/CD pipelines that deploy to the cluster, use github-actions; for the Terraform that provisions the cluster itself, use terraform-expert.

    The same file is in 1 other repository

  • Language version migrator

    SkillMedev/skills/skills/language-version-migrator Skill

    5★ repo

    Ports a codebase across a breaking language or runtime version with compatibility shims, batched automated transforms, dual-runtime CI, and old-vs-new output diffing, ending in a flag-flip cutover with a rollback rule. Use when someone says "migrate us from Python 2 to 3", "we're jumping Node majors", "move to the next Java LTS", or any runtime upgrade where source must change to keep compiling or behaving correctly. Do NOT use for an application framework's major version (React, Rails, Spring) - use framework-upgrader instead; for proving a database schema or data migration is safe, use migration-safety-checker; and skip it entirely when the runtime change is purely operational (base image, CI matrix, deploy target) with no syntax or semantic breaks.

    The same file is in 1 other repository

  • Linear workflow

    SkillMedev/skills/skills/linear-workflow Skill

    5★ repo

    Configures a Linear team end to end - team structure, minimal workflow states, cycles, a small label taxonomy, a daily triage rotation, and priority SLAs with breach views. Use when someone asks "set up Linear for my team", "how should we structure teams and labels in Linear", "our Linear backlog is a mess", or "how do we handle inbound bugs in Linear". Do NOT use for writing the tickets themselves - acceptance criteria, story points, Definition of Ready - use jira-ticket-writer instead (its ticket anatomy applies to Linear issues too). For deciding sprint scope and capacity, use sprint-planning.

    The same file is in 1 other repository

  • Model card writer

    SkillMedev/skills/skills/model-card-writer Skill

    5★ repo

    Produces a complete model card - intended use, training data provenance, evaluation results with slices, limitations, and usage guidance - for any model shared beyond its team or affecting people. Use when someone asks "write a model card", "document this model before release", "what should our model documentation include", or is preparing a model for deployment, handoff, or external publication. Do NOT use for producing the underlying evaluation numbers - use model-evaluation-report instead; for ongoing production monitoring plans use data-drift-monitor.

    The same file is in 1 other repository

  • Next on vercel perf

    SkillMedev/skills/skills/next-on-vercel-perf Skill

    5★ repo

    Diagnose and fix Core Web Vitals and page performance of a Next.js app on Vercel - measurement-first. Use when an LCP/INP/CLS score is bad, a page "feels slow", Lighthouse/PageSpeed/Speed Insights is red, the JS bundle is too big, images or fonts are janky, or you want Vercel-specific caching/edge wins. Triggers: "improve Core Web Vitals", "fix LCP", "reduce INP", "stop layout shift", "my Next.js page is slow on Vercel", "shrink my bundle", "next/image optimization", "font is causing CLS", "cache this page". Do NOT use to set up the deploy pipeline or rollbacks - use vercel-deploy-pipeline; for ISR/cache-component semantics and edge runtime choice - use vercel-edge-and-isr; for env/secrets - use vercel-env-management; for model/provider routing - use vercel-ai-gateway; for WAF/bot defense - use vercel-firewall-and-botid.

    The same file is in 1 other repository

  • Observability stack

    SkillMedev/skills/skills/observability-stack Skill

    5★ repo

    Instruments systems with the three pillars - structured logs, RED/USE metrics, and distributed traces - correlated by one trace ID, with cardinality budgets and symptom-based alerts. Use when someone asks "how should I instrument this service", "what metrics should I emit", "why is my metrics bill exploding", "set up OpenTelemetry for my stack", or "we can't tell which service is slow". Do NOT use for tuning an existing noisy pager or alert thresholds - use alert-tuning instead; for defining SLO error-budget policy, use error-budget-policy; for the incident process when alerts fire, use sev-triage and postmortem-writer.

    The same file is in 2 other repositories

  • Oncall handoff

    SkillMedev/skills/skills/oncall-handoff Skill

    5★ repo

    Produces a complete on-call shift handoff note - shift summary, open incidents, watch items with paging thresholds, silenced alerts, in-flight changes, and escalation contacts - checked against a completeness checklist. Use when someone asks "write my on-call handoff", "what should I tell the next on-call", "my shift ends in an hour, help me hand over", or "make a handoff template for our rotation". Do NOT use for writing the incident postmortem after resolution - use postmortem-writer instead. For live severity assessment during an incident, use sev-triage; for external customer-facing incident comms, use status-page-update.

    The same file is in 1 other repository

  • Postmortem writer

    SkillMedev/skills/skills/postmortem-writer Skill

    5★ repo

    Writes blameless incident postmortems with a log-reconstructed timeline, multi-causal contributing factors, and owned, dated action items. Use when someone asks "write the postmortem for yesterday's outage", "run a blameless retro on this incident", "turn these incident notes into a postmortem doc", or after any SEV1 or SEV2 event. Do NOT use for customer-facing incident updates while the incident is live - use status-page-update instead; for transferring context at a shift change, use oncall-handoff; for classifying and running a live incident, use sev-triage.

    The same file is in 1 other repository

  • Press release writer

    SkillMedev/skills/skills/press-release-writer Skill

    5★ repo

    Writes announcement press releases in proper wire format - inverted pyramid structure, a headline under 100 characters carrying the news verb, dateline conventions, quote construction rules (executive quote states vision, customer quote states outcome), and a boilerplate block. Use when a user says "write a press release for our launch", "we're announcing a funding round, draft the release", "turn this announcement into a press release", or "is this press release newsworthy enough". Do NOT use for orchestrating a Product Hunt launch - use product-hunt-launch instead - for running the launch day itself - use launch-day-runbook instead - or for tracking coverage after the release goes out - use media-monitor instead.

    The same file is in 1 other repository

  • Process doc

    SkillMedev/skills/skills/process-doc Skill

    5★ repo

    Documents recurring processes as step-by-step SOPs with decision points, edge cases, and a named owner, so anyone can run the process correctly without asking. Use when someone asks "write an SOP for this", "document our onboarding process", "this only lives in one person's head", or wants to delegate a recurring task safely. Do NOT use for incident-response or on-call operational runbooks - use runbook-writer instead; for customer-facing product documentation, use help-documentation.

    The same file is in 1 other repository

  • Refund deescalation

    SkillMedev/skills/skills/refund-deescalation Skill

    5★ repo

    Handles angry customers and refund requests with a validate-own-act de-escalation sequence and a refund decision matrix that weighs refund cost against customer LTV and chargeback risk. Use when someone asks "this customer is furious, what do I say", "should I approve this refund", "how do I deny a refund without losing the customer", or a conversation is emotionally charged. Do NOT use for routine, non-charged ticket responses - use support-ticket-reply instead; for diagnosing systemic patterns behind falling satisfaction scores, use csat-root-cause.

    The same file is in 1 other repository

  • Secrets hygiene

    SkillMedev/skills/skills/secrets-hygiene Skill

    5★ repo

    Guides detection, emergency rotation, and prevention of leaked secrets and credentials across source code, git history, CI pipelines, logs, and infrastructure config. Use when someone says "I think I committed an API key", "a secret leaked", "scan the repo for credentials", "how should we store secrets", or is setting up secrets management for an application, CI/CD, or Kubernetes. Do NOT use for detecting or redacting personal data like names, emails, or SSNs - use pii-scrubber instead; for routine non-secret environment configuration on Vercel, use vercel-env-management.

    The same file is in 1 other repository

  • Status page update

    SkillMedev/skills/skills/status-page-update Skill

    5★ repo

    Writes customer-facing incident status updates for each lifecycle stage - investigating, identified, monitoring, resolved - with cadence rules and plain-language templates. Use when someone asks "write a status page update", "what do we tell customers about this outage", "draft the resolved notice", or during an active incident needing customer communication. Do NOT use for the internal post-incident analysis - use postmortem-writer once the incident is closed; for deciding severity and internal escalation flow use sev-triage; for summarizing an incident upward to executives use escalation-summary.

    The same file is in 1 other repository

  • Team health check

    SkillMedev/skills/skills/team-health-check Skill

    5★ repo

    Assesses a team's health across three independent dimensions - delivery, morale, and clarity - using observable signals from the last 8 weeks, then maps each red or yellow signal to one manager action with a 2-week horizon. Use when a manager asks "is my team okay", "how do I tell if morale is slipping", "we keep missing sprints and I don't know why", or wants a quarterly team health review. Do NOT use for facilitating a single sprint retrospective - use sprint-retro-facilitator instead - for structuring individual 1:1s - use 1on1-agenda - or for defining how a new team works together - use team-charter instead.

    The same file is in 1 other repository

  • Terraform expert

    SkillMedev/skills/skills/terraform-expert Skill

    5★ repo

    Writes safe, modular, idiomatic Terraform - remote state layout, module structure, plan-review discipline, version pinning, and blast-radius control. Use when someone asks "structure my Terraform repo", "how should I split state between environments", "terraform plan wants to destroy and recreate my database", "should I use count or for_each", or "how do I import existing infrastructure". Do NOT use for CI pipeline authoring in GitHub Actions - use github-actions instead; for Kubernetes manifests the infrastructure hosts, use kubernetes-basics; for managing app secrets outside IaC, use secrets-hygiene.

    The same file is in 1 other repository

  • Vercel ai gateway

    SkillMedev/skills/skills/vercel-ai-gateway Skill

    5★ repo

    Route every LLM call through one unified API on Vercel - plain "provider/model" strings via the AI SDK, automatic provider routing and model fallbacks, observability and per-key cost tracking, and zero data retention. Use when you ask "how do I add an LLM to my Vercel app", "route OpenAI and Anthropic through one API", "add model failover / fallback", "track LLM cost and spend on Vercel", "set a budget per API key", "switch providers without changing code", "AI_GATEWAY_API_KEY", or "stop installing @ai-sdk/openai and @ai-sdk/anthropic separately". Do NOT use for general AI SDK app code (chat UI, tool calling, structured output) - that is the AI SDK itself; do NOT use for deploy config, env wiring, or edge/runtime choice - use vercel-deploy-pipeline, vercel-env-management, and vercel-edge-and-isr instead; do NOT use to rate-limit or block abusive AI traffic - use vercel-firewall-and-botid; and do NOT use for app-level latency/caching tuning of the route - use next-on-vercel-perf.

    The same file is in 1 other repository

  • Vercel deploy pipeline

    SkillMedev/skills/skills/vercel-deploy-pipeline Skill

    5★ repo

    Ship a Next.js app to Vercel the production way: promote a tested preview to production, instant-rollback a bad release, build once with --prebuilt, run a staged/canary rollout with Rolling Releases (GA), and wire the deploy into CI. Use when someone says "deploy to Vercel", "promote preview to production", "vercel promote", "roll back the deploy", "vercel rollback", "instant rollback", "canary release on Vercel", "rolling release", "--prebuilt build", "vercel deploy in GitHub Actions", or "set up CI for my Vercel project". Do NOT use to manage env vars or pull .env - use vercel-env-management instead; do NOT use to tune runtime/cold-start/ISR performance - use next-on-vercel-perf or vercel-edge-and-isr instead.

    The same file is in 1 other repository

  • Vercel edge and isr

    SkillMedev/skills/skills/vercel-edge-and-isr Skill

    5★ repo

    Choose a rendering, runtime, and caching strategy on Vercel - Fluid Compute as the default runtime (Edge Functions are deprecated), ISR/PPR, Next.js 16 Cache Components ('use cache', cacheLife, cacheTag, updateTag, revalidateTag), and the Vercel Runtime Cache API (getCache, expireTag, invalidateByTag) with tag-based invalidation. Use when someone asks "should this page be static or server rendered on Vercel", "how do I set up ISR in Next.js", "revalidate this page on demand", or "why is my Vercel page serving stale content" - including streaming vs PPR decisions, caching an API response across regions, and migrating off unstable_cache. Do NOT use to set env vars (use vercel-env-management), wire git/preview/promote deploys (use vercel-deploy-pipeline), route LLM calls (use vercel-ai-gateway), or block bots/rate-limit (use vercel-firewall-and-botid). For pure Core-Web-Vitals/bundle tuning, hand to next-on-vercel-perf.

    The same file is in 1 other repository