pipeline plugins

by ScaleVector GmbH

Deploy a GitHub issues pipeline to dltHub Platform in one shot

by ScaleVector GmbH

Full-path guided start: ingest → visualize → transform → deploy in 3-5 prompts

by o11y.dev

Expert OpenTelemetry guidance for collector configuration, pipeline design, production telemetry instrumentation, and deployment architecture across Kubernetes, ECS, serverless, and standalone environments.

by Alberto Leal

The non-interactive `rg`/`fd`/`rga` → `fzf --filter` pipeline — scan with a regex tool, then fuzzy-rank the lines without a TUI. Use when fuzzy-matching file paths, code lines, or document/PDF text from a script or one-shot command, reproducing the fuzzy-search MCP on the bare CLI, or piping fuzzy-ranked results into xargs/an editor. The CLI technique; for the INTERACTIVE picker use the fzf skill, for tool-call ergonomics use the fuzzy-search MCP.

by Dr. Alex M. Mawla, PhD

20 ENCODE API tools + 47 expert skills for genomics research. Search experiments, download files with MD5 verification, run pipelines, and cross-reference 14 databases.

by App Vitals

The autonomous delivery agent for Claude Code — conversational planning, queue-driven execution, policy-controlled code review, a five-phase test-readiness pipeline, and autonomous deploy (merge → canary → promote) for any software project.

by Sven Roth

Orchestrate the full Shipwright SDLC pipeline — from user description to deployed application

by Matthew Boston

Orchestrates specialized agents to autonomously implement entire features end-to-end

by Matt Corbett

Sales & Revenue Operations specialist team — agents (revops-lead, pipeline-forecast-analyst, funnel-conversion-strategist, quota-territory-architect), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A RevOps team for a sales-ops leader or founder accountable for pipeline, forecast accuracy, and quota attainment — it reads pipeline as coverage-against-quota, forecasts from stage-weighted history, designs quota to capacity, and treats win-rate and sales-cycle as a funnel system. Inherits ravenclaude-core protocols.

by Haytham Zahran

Takes one feature from idea to reviewed pull request — spec, plan, build, review, ship — stopping to ask you at every step that leaves your machine.

by Dan Lee

Self-evolving development pipeline — 3 lean agents across 6 phases with compound discovery loop, proactive research, and strict evaluation. No external dependencies.

by Rocky Hong

Bootstrap or sync the development pipeline in any repo. /super-bootstrap is a thin orchestrator: it installs/syncs the generic harness runway (CLAUDE.md, AGENTS.md foreign-executor contract, skeleton docs, path-scoped rules, the core plugin pin, default-on harness hooks (commit-channel routing raw commits to the gateway-inline commit door; consult-check pair injecting prompt-time doc recall); a plugin-owned runway-version SessionStart hook flagging a runway receipt that lags the installed plugin and routing to the re-run; monorepo tier per-package fan-out; adopt mode retiring a consumer's superseded fork skills/agents and backfilling skeleton sections added since bootstrap; opt-in earn-gated scale module: parked + test-queue + outward + venue map), seeds product GAP cards on greenfield, and gates stack-matched skill/MCP/hook curation on substantive seed docs. Bundles commit, todo, log, triage, triage-report, help, merge, drain, check-docs-consistency, and optional release-init — all namespaced under super-bootstrap: except the entry. Per-skill contracts live in each SKILL.md frontmatter (canonical catalog); plugin README carries the index. Solo dev workflow.

by Aviv Sinai

Bitbucket CLI - manage repos, PRs, branches, issues, webhooks, and pipelines for both Data Center and Cloud

by Aviv Sinai

GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues

by Viraj Patel

Generate a repo's delivery pipeline for whichever CI system it uses — one /cicd:workflow skill that resolves the tool from config and reads that tool's reference. Tools always install through mise; multi-repo and monorepo layouts are both supported.

by Ivan-WG

Infrastructure in one plugin: CI/CD ordering, container/image hygiene, Kubernetes limits and probes, deploy strategy with rollback, and secrets handling (devops-practices); Dockerfile and compose discipline (docker-best-practices); and local dev environments generated from evidence — manifests, lockfiles, .env DSNs, CI images — via /devops:init (compose-init). One /devops:review loads the Docker skill when a Dockerfile or compose file is in scope, backed by a PreToolUse guard on workflow files and a devops-engineer worker + devops-reviewer pair. Owns infra-layer observability wiring; defers in-code instrumentation to resilience's observability skill.

by Junjie Luo

Skills for the haipipe data + NN + endpoint pipeline. Tier-1 user umbrellas (/haipipe-data, /haipipe-nn, /haipipe-end, /haipipe-project, /haipipe-individual) parse intent and dispatch to per-stage / per-target / per-risk-profile Tier-2 specialists. Covers stages 0-2 (per-individual data contract), 1-4 (project-wide data build), 5 (model training), 6 (endpoint packaging + deploy targets: SageMaker, Databricks, Flask, MLflow), and per-project scaffolding.

by Ivan-WG

A program-level product owner for long, multi-session, multi-branch builds. /overseer:start "Build a CRM that manages clients" inventories the project and every installed plugin (user, project, local scope), asks one clarifying round, writes a milestone roadmap, then delivers each milestone on its own branch by briefing the taskmaster pipeline and task-runner execution with skill-pinned dispatch prompts. An accept script refuses to close a milestone until the app was driven in a real browser at three widths with a clean console — a green suite alone does not count. State under .claude/overseer/ lets /overseer:resume continue in a fresh session; a SessionStart hook announces it.

by Andrew Maston

Pipeline orchestration — queue, dev/test/review automation, merge runner, spend governance.

by Benedikt Winkler

A GitHub-driven agent pipeline — plan, implement, review, revise — installable into any repository. GitHub labels are the state machine; a cockpit session dispatches stage agents into isolated worktrees and runs the human gates.

by Ivan-WG

Meta-bundle: the whole idea-to-shipped pipeline in one install — the core-suite baseline (candor, code-review, git-workflow, hindsight, secret-scanning, skill-router, stack-scan) plus taskmaster clarification and cards, task-runner execution with delegation contracts, approaches deliberation, code-architecture plan-before-code and verification, testing, debugging, and the ui-ux and security lanes the cards dispatch into. Replaces taskmaster-suite, process-suite and quality-principles-suite (2026-09-14). Fifteen members: over the host's 200k skill-listing floor by design — the README names the settings line. Uninstall cleanly with /workflow-suite:uninstall.

by Het Patel

A feature-shipping pipeline (planner, coder, tester, reviewer) driven by /ship: plan with a finalize gate, then ship one service or fan out across many in parallel (phase-batched), configurable via an optional agent-orchestration.config.json registry, coordinating through a shared ./pipeline bus with a live local dashboard.

Career agents for anyone: sync LinkedIn, CV and personal website from one source of truth, review and score all three, find and apply to jobs, track the pipeline, prep and mock every interview stage, write posts with visuals, grow reach, go multi-platform and multilingual, review offers, see it all on a dashboard, and run it unattended on a schedule with email, calendar and digest integrations. Automation modes draft/assisted/auto: LinkedIn MCP for reads and messages, a browser operator agent for profile edits, posts and applications.

by Paul Lovy

Build a whole character for Godot 4.7 from one TOML spec: a humanform body from a brief, baked, with hair, follow-through flesh, rig-anything's move set and wardrobe garments, exported as the glb, .moves.json and garment glbs MovesController and wardrobe.gd read. Stages know what they need and check the file before running, so garments before moves or flesh after garments refuse and name the order; each stage stores an input hash and its report on the rig, so a rebuild skips what has not changed and a fresh Blender session resumes from the saved .blend. Tuned numbers live in the plugins that own them - gait styles, flesh limit shares, garment presets - so a new character is a description, a style and an outfit, with no code.