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

  • Senior fullstack

    roedyrustam/claudevibeskills/src/senior-fullstack Skill

    no license0★ repo

    Expert fullstack architecture skill covering advanced backend patterns, infrastructure, testing, and system design. Use this skill whenever the user is working on fullstack architecture decisions, API design, background job queues, caching strategies, database connection pooling, CI/CD pipelines, Docker containerization, end-to-end testing with Playwright, WebSocket real-time features, or deployment configurations. Trigger on mentions of Redis, BullMQ, Prisma, Drizzle, PostgreSQL, Docker, GitHub Actions, connection pooling, rate limiting, Playwright, or any backend/infra topic that goes beyond simple CRUD. Also trigger for performance bottlenecks, scalability concerns, or production readiness reviews.

  • Secrets hygiene

    SkillMedev/security-compliance-hardening/skills/secrets-hygiene Skill

    0★ 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

  • Model card writer

    SkillMedev/data-science-ml/skills/model-card-writer Skill

    0★ 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

  • Ship

    nsollazzo/skills/ship Skill

    0★ repo

    Take a finished change from working tree to a green, mergeable PR by chaining simplify → verify → code-review → smart-commit → branch hygiene → PR → babysit. Use when the user says "ship", "ship it", "ship this", or wants the full clean→verify→review→commit→PR→green pipeline in one command. Default stops at approved + CI green + mergeable; does NOT merge unless --merge.

  • Meta workflow rl

    QrCommunication/skills/skills/orchestrate/skills/meta-workflow-rl Skill

    no license0★ repo

    Meta-workflow generique injectable avec creation interactive (--create) - UN seul point d'entree pour tous les templates

  • Deploy log doctor

    Starr-del/ShipSafe/skills/deploy-log-doctor Skill

    0★ repo

    Diagnose failed build and deploy logs from Vercel, Netlify, Cloudflare Pages, or GitHub Actions. Use this whenever the user pastes a build log, says a deploy failed, mentions 'build error', 'deployment failed', 'works locally but not in production', or shows any CI output containing an error — even if they don't ask for a diagnosis explicitly. Runs fully offline — no API keys, no network, no credentials.

  • Dns cutover

    Starr-del/ShipSafe/skills/dns-cutover Skill

    0★ repo

    Generate the exact DNS records for pointing a custom domain at Vercel, Netlify, Cloudflare Pages, or GitHub Pages — and validate the user's actual records before they flip the domain. Use whenever the user mentions custom domains, DNS, nameservers, 'domain not working', CNAME/A records, or connecting a purchased domain to a deployed site. Runs fully offline — no API keys, no network, no credentials.

  • Migration reversibility

    Starr-del/ShipSafe/skills/migration-reversibility Skill

    0★ repo

    Check SQL migration files for irreversible or deploy-breaking operations before running them against production. Use whenever the user writes a migration, mentions ALTER/DROP/migrate, prepares a release containing schema changes, or asks if a deploy is safe — for Supabase, Prisma, Drizzle, or raw SQL alike. Runs fully offline — no API keys, no network, no credentials.

  • Rollback readiness

    Starr-del/ShipSafe/skills/rollback-readiness Skill

    0★ repo

    Score how safely a project can be deployed AND rolled back — the final pre-push check. Use whenever the user says they're about to deploy, ship, launch, or push to production, asks 'is this ready to deploy', finishes a feature destined for prod, or at the end of any session that produced deployable changes. Run this proactively; it is the capstone check of the preflight pack. Runs fully offline — no API keys, no network, no credentials.

  • Schedule

    sdhilip200/api-warehouse/skills/schedule Skill

    0★ repo

    Use whenever the user wants to schedule, deploy, or automate the pipeline — run it on a cron, package it for Cloud Run, Azure Container Apps, or AWS ECS/Fargate, or set up any recurring cloud execution. Trigger even if they don't say "schedule": phrases like "run it every day", "containerize the pipeline", "deploy to the cloud", "automate the pipeline", or "set up a job" all qualify.

  • Ship check

    aliasunder/agent-plugins/plugins/ship-check/skills/ship-check Skill

    0★ repo

    Plugin marketplace for Claude Code and Claude Cowork — fresh-eyes code review agents, workflow orchestrators, and specialized skills

  • Aws

    muxammadmamajonov/dot-claude/.claude/skills/aws Skill

    0★ repo

    Use for AWS architecture, IAM, cost, or infra work. Triggers — EC2, ECS, EKS, Lambda, S3, RDS, DynamoDB, SQS/SNS, VPC, CloudFormation, CDK, Terraform on AWS, 'deploy to AWS'.

  • Azure

    muxammadmamajonov/dot-claude/.claude/skills/azure Skill

    0★ repo

    Use for Microsoft Azure work. Triggers — AKS, App Service, Azure Functions, Azure SQL, Cosmos DB, Service Bus, Blob Storage, Entra ID/RBAC, ARM, Bicep, Terraform on Azure, 'deploy to Azure'.

  • Cloudflare

    muxammadmamajonov/dot-claude/.claude/skills/cloudflare Skill

    0★ repo

    Use for Cloudflare edge work. Triggers — Workers, Pages, D1, R2, KV, Durable Objects, Queues, Hyperdrive, Workers AI, WAF, Turnstile, Wrangler, 'deploy to edge'.

  • Devops

    muxammadmamajonov/dot-claude/.claude/skills/devops Skill

    0★ repo

    Use for CI/CD pipelines, environments (staging/prod), secrets management, and infrastructure-as-code — automated build/test/deploy, reproducible infra, guards against destructive operations.

  • Docker kubernetes

    muxammadmamajonov/dot-claude/.claude/skills/docker-kubernetes Skill

    0★ repo

    Use for Docker containerization, Compose for local dev, or Kubernetes deploys (k8s, EKS, GKE, AKS) — Dockerfiles, Helm charts, manifests, image CI/CD, CrashLoopBackOff/OOMKilled errors.

  • Gcp

    muxammadmamajonov/dot-claude/.claude/skills/gcp Skill

    0★ repo

    Use for Google Cloud work. Triggers — GKE, Cloud Run, Cloud Functions, BigQuery, Cloud SQL, Spanner, Pub/Sub, Cloud Storage, Firestore, Vertex AI, Terraform on GCP, 'deploy to Google Cloud'.

  • Headless automation

    muxammadmamajonov/dot-claude/.claude/skills/headless-automation Skill

    0★ repo

    Use when running the project OS non-interactively (CI, pipelines, unattended) — safe-headless commands, STOP-gates become recorded assumptions, deterministic exit codes, no-secret logging.

  • Observability

    muxammadmamajonov/dot-claude/.claude/skills/observability Skill

    0★ repo

    Use when adding or auditing logging, metrics, distributed tracing, alerting, SLOs, or dashboards — new services, incident blind spots, readiness review.

  • Production readiness

    muxammadmamajonov/dot-claude/.claude/skills/production-readiness Skill

    0★ repo

    Use as the final pre-launch gate — verify reliability, observability, scaling, and disaster recovery are real, after security/QA/performance/accessibility audits pass. Blocks launch on critical gaps.

  • Securing applications

    nhattrung0911/shipwright/skills/securing-applications Skill

    0★ repo

    Use when building or reviewing anything that handles untrusted input, authentication, authorization, secrets, user data, PII/privacy, payments, file uploads, CORS/headers, external dependencies, LLM/AI features, or deployment config — and as a mandatory gate before shipping or claiming a feature done. Covers OWASP Top 10:2025 + LLM risks + data privacy. Stack- and agent-agnostic.

  • Shipping production websites

    nhattrung0911/shipwright/skills/shipping-production-websites Skill

    0★ repo

    Use when starting, planning, scoping, or auditing any website or web app intended to reach real users — greenfield builds, "build me a site/dashboard/SaaS/landing page", adding a major feature, or pre-launch production-readiness checks. Stack-agnostic.

  • Workflow distiller

    AvyanshKatiyar/mined-skills/plugins/workflow-distiller Skill

    0★ repo

    Mine your own Claude Code history for the skills you should have. Scans ~/.claude/projects session transcripts (read-only, local-only, aggregates-only) for repeated friction→fix patterns, proposes ranked skill candidates, and drafts SKILL.md files following best practice. Use when the user asks "what skills should I make", "distill my workflows", "mine my transcripts", "turn my habits into skills", "find my repeated workflows", or wants skill ideas grounded in what they actually do every week.

  • Kubernetes basics

    SkillMedev/devops-platform-engineer/skills/kubernetes-basics Skill

    0★ 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

  • Observability stack

    SkillMedev/devops-platform-engineer/skills/observability-stack Skill

    0★ 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

  • Terraform expert

    SkillMedev/devops-platform-engineer/skills/terraform-expert Skill

    0★ 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

  • Escalation summary

    SkillMedev/customer-support-copilot/skills/escalation-summary Skill

    0★ 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

  • Refund deescalation

    SkillMedev/customer-support-copilot/skills/refund-deescalation Skill

    0★ 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

  • Health check

    cody-hutson/pmo-platform/operations/skills/health-check Skill

    no license0★ repo

    Intent-driven project-state drift auditor. Audits a single project for drift between its tracked state and its canonical sources (MCP + local), then emits a categorized 5-section punch list — Confirmed / Auto-Actionable / Decisions / Unknowns / Rollup-Diffs — that is never auto-applied. Eight modes: full (total sweep), timeline (date/milestone drift), attribution (owner drift), comms (comms-coverage drift), plan (one named plan), raid (RAID-log drift), sources (canonical-source inventory), rollup (project↔portfolio rollup compose/refresh). Invokable interactively as /health-check and schedulable for file output. Triggers: "health check this project", "is this project's state still accurate", "run a drift check", "check for stale dates", "audit the timeline", "check ownership drift", "are comms overdue", "did this plan land", "audit the RAID log", "are our sources current", "roll up to portfolio", "refresh this project's rollup", "did anything drift since last cycle", "is the tracked state current."

  • Pmo release train engineer

    cody-hutson/pmo-platform/operations/skills/pmo-release-train-engineer Skill

    no license0★ repo

    Release Train Engineer Specialist (SAFe) — facilitates the Agile Release Train: PI-planning facilitation, cross-team program-increment dependency and risk management, and program-level flow/impediment escalation. SAFe-conditional — active only when the instance runs a SAFe delivery_approach; dormant (does not fire) under a non-SAFe delivery_approach. Composes delivery-engine (sprint/exec/RAID mechanics) + ppm-agent (strategic push-to-resolution) — invokes them, never re-implements them. Modes: PI-Planning Facilitation · ART Dependency & PI-Risk Management · Program-Flow & Impediment Escalation · ART Release-Readiness Synthesis. Triggers: "facilitate PI planning", "run the PI planning", "map the ART dependencies", "what's blocking the release train", "program increment risk", "ART impediment escalation", "is the ART ready for the PI release", "release train readiness".

  • Pmo devops sre

    cody-hutson/pmo-platform/release/skills/pmo-devops-sre Skill

    no license0★ repo

    DevOps/SRE Specialist — owns deploy mechanics + reliability/rollback triggers; composes `release-executor` — invokes it, never re-implements it. Executes the go/no-go the operator/Release-Manager already made; never makes the go/no-go itself. Modes: Pipeline · Deploy-Exec · Reliability. Use when a release needs its deploy run, its pipeline/rollout configured, or a reliability signal turned into a rollback proposal. Triggers: "configure the deploy pipeline", "run the deploy", "push the release through the pipeline", "set up the rollout", "we have a regression — trigger the rollback", "is the deploy healthy".

  • Pmo qa lead

    cody-hutson/pmo-platform/release/skills/pmo-qa-lead Skill

    no license0★ repo

    QA Lead Specialist — composes pmo-qa-auditor + build-reviewer into program-level QA leadership. Owns the system-level test strategy, binds acceptance scope to delivery readiness, governs defect disposition, and gates dev-testing — invoking the composed reviewers, never re-implementing them. Modes: Strategy · Acceptance · Defect-Governance · Dev-Test. Use when a release needs a QA-leadership read rather than a single review pass. Triggers: "what's the test strategy for this release", "does this meet the acceptance criteria", "is this acceptable to ship", "govern the defects on this release", "how should we disposition these findings", "gate the dev-testing on this PR", "run the dev-test quality gate", "QA-lead read on this release".

  • Pmo release manager

    cody-hutson/pmo-platform/release/skills/pmo-release-manager Skill

    no license0★ repo

    Release Manager Specialist — owns the release tail (go/no-go decision · deploy authorization · close-out); composes `release-planner` + `release-executor` — invokes them, never re-implements them. Makes the go/no-go the operator ratifies and sequences Stage 9 → 12 → 13; owns no standalone release mechanics. Modes: Go/No-Go Evidence · Deploy Execution · Close-out. Use when a release needs its tail driven end-to-end — the go/no-go evidence assembled, the deploy driven, or the release closed out. Triggers: "act as release manager", "run the release tail", "assemble the go/no-go evidence", "drive the deploy", "close out the release", "is this release ready to ship".

  • Pmo skill refiner selftest canary

    cody-hutson/pmo-platform/release/skills/pmo-skill-refiner-selftest-canary Skill

    no license0★ repo

    Smoke test for the pmo-skill-refiner factory — produced via the refiner's Create-New workflow during an AC demonstration. Reports the count of skill directories currently present in `release/skills/` and flags any that are missing from the `deploy.sh` per-module skill arrays (`OPERATIONS_SKILLS` / `RELEASE_SKILLS` / `CORE_SKILLS` / `CANARY_SKILLS`). Report-only (no decision-class outputs, no recommendations, no actions). Permanent fixture per ADR-04 (Stage 5 design for ) — functions as an always-on smoke test that detects factory regressions. Use when the user wants to check skill-roster consistency ("check the skill roster", "count tracked skills", "audit skill deployment drift", "verify skills/ folder matches deploy.sh", "are all my skills deployed").

  • Release executor

    cody-hutson/pmo-platform/release/skills/release-executor Skill

    no license0★ repo

    Executes approved release plans. Modes: Execute release · Verify release · Rollback release · Close release. Creates snapshots, applies file changes, closes IMP items, updates release log, runs verification, runs automated Stage 13 close-out. Requires an approved plan with Dry-Run Record. Triggers: "execute the release", "deploy v[X.Y]", "ship v[X.Y]", "verify the release", "rollback v[X.Y]", "go live with v[X.Y]", "close the release", "finalize v[X.Y]", "stage 13 close", "run the close-out", "automated close-out".

  • Release hub

    cody-hutson/pmo-platform/release/skills/release-hub Skill

    no license0★ repo

    Release orchestrator — the whole-release control plane. Takes a milestone and drives it through the pipeline by composing the stage skills; owns sequencing and readiness-gating, never the stage work itself. Mode R (Milestone Readiness) is a pre-flight that confirms a bundled milestone is ready to START before a run is committed — composing triage/dup, staleness/architecture, dependency, and bundle-coherence checks into one GO / NO-GO with per-finding dispositions. Invoke by name with a milestone; never auto-fires on a bare "release" mention. Modes: Milestone Readiness · Orchestrate Release. Triggers: "run the release hub on [milestone]", "is [milestone] ready to start", "check milestone readiness for [milestone]", "orchestrate the release for [milestone]".

  • Release planner

    cody-hutson/pmo-platform/release/skills/release-planner Skill

    no license0★ repo

    Plans the PMO platform release lifecycle. Modes: Backlog analysis · Release planning · Dry run. Analyzes the improvement backlog, maps dependencies, suggests release bundles, generates release plans, and produces dry-run diffs. Read-only — never modifies governance files. Triggers: "review the backlog", "plan the release", "bundle the release", "dry run", "show me the diffs", "what's in v[X.Y]."

  • Project postmortem

    scoobydrew83/skills/plugins/coordinated-skills/skills/project-postmortem Skill

    0★ repo

    Generate an evidence-grounded project retrospective — pulled from git history and decision docs, not memory — that grades the project on separate dimensions, splits what went right from wrong, reduces the failure to its root ordering error, extracts transferable lessons for the next project, and names what survives. Use whenever a project ships, stalls, or gets sunset and someone wants the writeup — "post-mortem", "retrospective", "what went wrong with X", "we're sunsetting X, write it up", or mid-project "why did this go sideways". The method cites commit hashes or sources for every claim, builds a timeline of when validation happened vs building, separates pros from cons including uncomfortable symmetries, and ends with a per-dimension scorecard plus a what-survives list — then runs a check that fails any vanity scorecard or uncited narrative. Distinct from drift-check (audits live docs) and conductor-memory/session-bookend (capture session state for continuity); this extracts backward-looking lessons.

  • Browser automation

    search-atlas-group/amm-founding-circle/skills/browser-automation Skill

    0★ repo

    Verify web pages with real browser evidence: screenshots, console checks, form interactions, and responsive views. Use when a task affects anything a user can see or click.

  • Host your agent

    search-atlas-group/amm-founding-circle/skills/host-your-agent Skill

    0★ repo

    Get your agent off your laptop. Installs an auto-save hook so an overnight run never loses work, plus a scheduled unattended runner (launchd on Mac / Task Scheduler on Windows / cron on Linux) that fires one of your own recurring jobs on a schedule and leaves a finished morning artifact. Use when you want an agent to run while your machine sleeps, when you're tired of hand-running ./run.sh and babysitting a terminal, when a crash or dead laptop keeps killing a session, or when you want to "set it and forget it" for a job you do every day.

  • Karvey context

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-context Skill

    0★ repo

    Read-only dashboard of the current project spec state: project config (project.json), capabilities, active/archived changes, sprint status, and a deploy-queue / landing report (which changes are in dev, in prod, ready to release, and versions per repo). Use at any point in the Karvey pipeline. Triggers include "karvey context", "estado del proyecto", "project status", "qué specs hay", "what specs exist", "cambios activos", "active changes", "cola de despliegue", "deploy queue", "landing report", "qué hay en dev", "what's in dev", "qué falta liberar", "what's left to release".

  • Karvey deploy

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-deploy Skill

    0★ repo

    Execute the ordered deployment flow (feature branch → dev → PR master) honoring the team's hard rules. Pull before start and before merge. Pipeline-triggered, never manual. Prod requires explicit human OK. Bumps semver + changelog before push, auto-detects the deploy platform, and runs a post-deploy canary loop (dev and prod) to guard zero-downtime. Use after karvey-qa passes. Triggers include "karvey deploy", "desplegar", "deploy", "liberar", "release", "subir a dev", "push to dev", "pasar a prod", "promote to prod".

  • Vibeops deploy

    rifatshampod/vibeops/codex/skills/vibeops-deploy Skill

    0★ repo

    Build and deploy the app to its live environment, with health checks and one-command rollback. Only runs when the user explicitly asks to deploy, ship, go live, push to production, or update the live site. Never triggers on ambient or future-tense mentions of deploying. Requires .infra/config.yml to exist before running.

  • Vibeops

    rifatshampod/vibeops/codex/skills/vibeops Skill

    0★ repo

    Deploy, host, ship, or put an app online. Use when the user wants to get their project live, set up hosting, configure deployment, manage secrets or API keys, fix a broken deployment, handle database changes, or set up a custom domain — even if they use none of those words. Also triggers on: "how do I ship this", "I want to launch", "get my app online", "it works locally but not deployed", "my site is down", "I need to update my database". Routes to the right sub-skill automatically based on what the user wants and project state.

  • Assess

    rifatshampod/vibeops/skills/assess Skill

    0★ repo

    Assess a project's infrastructure needs and recommend how to deploy it. Use this whenever the user wants to ship, deploy, host, publish, or 'put online' an app, or asks how to get their project live — even if they don't say the word 'infrastructure'. Also triggers when a user shares a project and asks 'what do I need', 'where should I host this', 'how much will it cost', or 'is my app ready to deploy'. Read-only and safe to run anytime.

  • Deploy

    rifatshampod/vibeops/skills/deploy Skill

    0★ repo

    Build and deploy the app to its live environment, with health checks and one-command rollback. Only runs when the user explicitly asks to deploy, ship, go live, push to production, or update the live site. Never triggers on ambient or future-tense mentions of deploying. Requires .infra/config.yml to exist before running.

  • Vibeops

    rifatshampod/vibeops/skills/vibeops Skill

    0★ repo

    Deploy, host, ship, or put an app online. Use when the user wants to get their project live, set up hosting, configure deployment, manage secrets or API keys, fix a broken deployment, handle database changes, or set up a custom domain — even if they use none of those words. Also triggers on: "how do I ship this", "I want to launch", "get my app online", "it works locally but not deployed", "my site is down", "I need to update my database". Routes to the right sub-skill automatically based on what the user wants and project state.

  • Press release

    alectivism/organization-ai-skills/org-content/skills/press-release Skill

    0★ repo

    Wire-ready press releases in your organization's voice — for research, program results, partnerships, events, and announcements. Use for "write a press release", "draft a PR", "announcement for media".

  • Zapier workflow builder

    alectivism/organization-ai-skills/org-ops/skills/zapier-workflow-builder Skill

    0★ repo

    Design Zapier workflows (Zaps) for any automation need — architecture, troubleshooting, Copilot prompts. Use for "build a Zap", "Zapier help", "automate this", or any workflow Zapier could solve.

  • Pg workflow

    Exekiel179/pingouin-psych-stats/skills/pg-workflow Skill

    0★ repo

    Run and resume the stateful Pingouin psychology statistics workflow. Use when the user wants an end-to-end, auditable analysis from intake through screening, analysis, approval, reporting, and archive, or asks to continue an existing analysis run.

  • Deploy

    waseemnasir2k26/skynetlabs-all-claude-code/skills/client-delivery-and-planning/deploy Skill

    no license0★ repo

    Multi-target deploy router for SkynetLabs with deploy gotchas baked in as hard rules. Detect the deploy target from the repo, route to the correct procedure, and BLOCK the wrong path before it ships. Targets in active use: - Vercel — React/Next sites (your-site-react, your-app) via `vercel` CLI / git push - Hostinger manual ZIP — example.com (Next.js standalone on Hostinger Node app). HARD RULE: deploys via manual ZIP archive upload, NOT GitHub auto-deploy, NOT Vercel. Warn + refuse if anyone routes it to GitHub push or Vercel. - WordPress theme/plugin — ZIP upload or Hostinger MCP deployWordpressTheme/Plugin - Static site — plain HTML/CSS via Hostinger MCP deployStaticWebsite Runs a pre-deploy gate (build passes, no exposed secrets, security review, git committed), executes the routed procedure, then verifies the URL is live and records the rollback path. Trigger when user says: "deploy", "ship to prod", "push live", "/deploy", "deploy my site", "deploy to vercel/hostinger", "upload the theme", "publish the site", or asks how to get a build live.

  • Plan eng review

    waseemnasir2k26/skynetlabs-all-claude-code/skills/client-delivery-and-planning/plan-eng-review Skill

    no license0★ repo

    Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance, observability, deployment. Walks through issues interactively with opinionated recommendations. CHANGELOG: 1.1.0 — Added §5 Observability & Debuggability and §6 Deployment & Rollout (folded down from plan-ceo-review and re-framed for "is this implementable safely?" lens vs CEO's "should we ship this?"). 1.0.0 — Initial release: Architecture, Code Quality, Tests, Performance.

  • Ship

    waseemnasir2k26/skynetlabs-all-claude-code/skills/client-delivery-and-planning/ship Skill

    no license0★ repo

    Ship workflow: merge main, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.

  • Fanout ship

    waseemnasir2k26/skynetlabs-all-claude-code/skills/code-quality-and-review/fanout-ship Skill

    no license0★ repo

    Parallel multi-agent ship pattern. Decompose 1 parent task into N independent child tasks → spawn N background agents in isolated git worktrees → each opens PR targeting shared integration branch → smallest-first merge order with self-documenting rebase recipes → final PR integration → main. Collapses N×30min sequential work into ~30min wall-clock. Isolated blast radius (one agent crash ≠ kill others). Granular revert. Small review surface per PR. Background execution = no babysit. Trigger when user says: "fan out", "fanout", "split into N PRs", "parallel build", "parallel agents", "spawn N agents", "/fanout-ship", "ship in parallel", or pastes a parent issue + list of child tasks. Auto-trigger heuristic: task list ≥ 4 INDEPENDENT subtasks touching DISJOINT files, single repo, GitHub-hosted.

  • Ship

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/gstack/ship Skill

    no license0★ repo

    Ship workflow: merge main, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.

  • N8n code javascript

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/n8n-skills/skills/n8n-code-javascript Skill

    no license0★ repo

    Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.

    The same file is in 5 other repositories

  • N8n code python

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/n8n-skills/skills/n8n-code-python Skill

    no license0★ repo

    Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.

    The same file is in 4 other repositories

  • N8n expression syntax

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/n8n-skills/skills/n8n-expression-syntax Skill

    no license0★ repo

    Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.

    The same file is in 5 other repositories

  • N8n mcp tools expert

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/n8n-skills/skills/n8n-mcp-tools-expert Skill

    no license0★ repo

    Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns.

    The same file is in 2 other repositories

  • N8n node configuration

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/n8n-skills/skills/n8n-node-configuration Skill

    no license0★ repo

    Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type.

    The same file is in 2 other repositories