Agent skill

Relay Pipeline

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Build a full CI/CD pipeline from scratch. An agent skill from jeremylongshore/tons-of-skills-marketplace.

Install Relay Pipeline

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace relay-pipeline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/relay-pipeline .claude/skills/relay-pipeline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "relay-pipeline" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/relay-pipeline into .claude/skills/relay-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay-pipeline", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/relay-pipeline

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace relay-pipeline --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/relay-pipeline .agents/skills/relay-pipeline && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "relay-pipeline" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/relay-pipeline into .agents/skills/relay-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay-pipeline", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace relay-pipeline --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/relay-pipeline .cursor/skills/relay-pipeline && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "relay-pipeline" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/relay-pipeline into .cursor/skills/relay-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay-pipeline", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/relay-pipeline

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace relay-pipeline --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/relay-pipeline .gemini/skills/relay-pipeline && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "relay-pipeline" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/relay-pipeline into .gemini/skills/relay-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay-pipeline", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace relay-pipeline

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/relay-pipeline .github/skills/relay-pipeline && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "relay-pipeline" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/relay-pipeline into .github/skills/relay-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay-pipeline", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace relay-pipeline --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/relay-pipeline .opencode/skills/relay-pipeline && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "relay-pipeline" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/relay-pipeline into .opencode/skills/relay-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relay-pipeline", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: relay-pipeline
GitHub stars: 2.8k
Token cost: ~2.4k tokens
SKILL.md length: 402 words
Files: 2
Skills in repo: 3,342
Repo updated: Oct 10, 2026
First seen: Oct 8, 2026
Licence: MIT

At a glance

Build a full CI/CD pipeline from scratch. An agent skill from jeremylongshore/tons-of-skills-marketplace.

Works in 6 steps: Read the Project → Determine What to Run → Write the Pipeline Config → …
Asked to set up CI/CD
SKILL.md covers Step 0: Read the Project, Step 1: Determine What to Run, Step 2: Write the Pipeline… and Step 3: Add Cache Strategy, plus 3 more sections
Calls go, cargo and mvn; needs GCP_SA_KEY and FLY_API_TOKEN

What it does

Relay Pipeline is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions and Python. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

Asked to set up CI/CD
Create pipeline
Automate deploys

Example prompts

“set up CI/CD”
“create pipeline”
“automate deploys”
“/relay-pipeline”

Requirements

Python 3
Node.js
Docker
A credential in GCP_SA_KEY
A credential in FLY_API_TOKEN
Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Read the Project
Determine What to Run
Write the Pipeline Config
Add Cache Strategy
Secrets Checklist
Output

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
- WebFetch
- WebSearch
- Task
- TodoWrite
…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- go
- cargo
- mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- GCP_SA_KEY
- FLY_API_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Relay Pipeline loads about 2.4k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 402 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~33
When it runs · the whole SKILL.md, loaded when a task matches: ~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 402 words, ~2,419 tokens.

Download SKILL.mdSave it as .claude/skills/relay-pipeline/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: relay-pipeline
description: Build a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT

Build CI/CD Pipeline

You are Relay — the DevOps engineer from the Engineering Team.

You write the pipeline. You don't present options. Given the project's stack and deployment target, you produce the actual CI config file ready to commit.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Step 0: Read the Project

bash

ls -a
cat package.json 2>/dev/null || cat pyproject.toml 2>/dev/null || cat go.mod 2>/dev/null || cat Cargo.toml 2>/dev/null || cat pom.xml 2>/dev/null || true
ls .github/workflows/ 2>/dev/null || true
ls -a | grep -E "(fly\.toml|render\.yaml|vercel\.json|netlify\.toml|app\.yaml|Dockerfile|docker-compose)" 2>/dev/null || true

Determine:

Language and package manager — Node/npm/pnpm/yarn, Python/uv/pip, Go, Rust/cargo, Java/maven/gradle
Framework — Next.js, FastAPI, Express, Django, Echo, Axum, Spring Boot
Runtime version — check .node-version, .python-version, .tool-versions, Dockerfile
Deployment target — Cloud Run, Fly.io, ECS, Vercel, Render, Railway, Kubernetes, Netlify
Existing CI — GitHub Actions, GitLab CI, Cloud Build, CircleCI, none

If no CI config exists, default to GitHub Actions.

Step 1: Determine What to Run

Make these decisions now — don't ask:

What exists	What to run in CI
`eslint`/`ruff`/`golangci-lint`/`clippy` in project	Run it
No linter configured	Skip lint stage
Test files exist	Run tests with coverage
No tests	Run build only; add a comment to add tests
`next build`/`go build`/`cargo build`/`mvn package`	Run build stage
Interpreted language, no compile step	Skip build stage
Dockerfile or platform deploy file	Add deploy stage
No deploy config	Output pipeline without deploy; note what to add

CI budget: 10 minutes max. If the naive pipeline would exceed that, add caching and parallelism by default.

Step 2: Write the Pipeline Config

Output a complete, ready-to-commit pipeline config.

GitHub Actions — Node.js (npm/pnpm/yarn)

yaml

name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  ci:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4

      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
        with:
          node-version-file: .node-version # or .nvmrc, or hardcode "22"
          cache: npm # swap for pnpm or yarn as needed

      - run: npm ci

      - run: npm run lint # remove if no linter

      - run: npm test -- --coverage # remove if no tests

      - run: npm run build # remove if no build step

  deploy:
    needs: ci
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main' && github.event_name == 'push'
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
      # Add deploy step here — see relay-deploy for the full deployment config

GitHub Actions — Python (uv)

yaml

name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  ci:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4

      - uses: astral-sh/setup-uv@f0ec1fc3b38f5e7cd731bb6ce540c5af426746bb # v5
        with:
          enable-cache: true # caches .venv keyed to uv.lock

      - run: uv sync --frozen

      - run: uv run ruff check . # remove if ruff not configured

      - run: uv run pytest --cov --cov-report=term-missing # remove if no tests

  deploy:
    needs: ci
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main' && github.event_name == 'push'
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
      # Add deploy step here — see relay-deploy for the full deployment config

GitHub Actions — Go

yaml

name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  ci:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4

      - uses: actions/setup-go@d35c59abb061a4a6fb18e82ac0862c26744d6ab5 # v5
        with:
          go-version-file: go.mod
          cache: true # caches Go module cache keyed to go.sum

      - run: go vet ./...

      - run: go test -race -coverprofile=coverage.out ./...

      - run: go build ./...

  deploy:
    needs: ci
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main' && github.event_name == 'push'
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
      # Add deploy step here — see relay-deploy for the full deployment config

Show full SKILL.md (162 more words)Show less

Deploy to Cloud Run (add to any pipeline above)

yaml

      - uses: google-github-actions/auth@6fc4af4b145ae7821d527454aa9bd537d1f2dc5f # v2
        with:
          credentials_json: ${{ secrets.GCP_SA_KEY }}
          # Secret to configure: GCP_SA_KEY — base64-encoded service account JSON
          # Required roles: roles/run.admin, roles/storage.admin, roles/iam.serviceAccountUser

      - uses: google-github-actions/setup-gcloud@6189d56e4096ee891640bb02ac264be376592d6a # v2

      - name: Build and push image
        run: |
          gcloud auth configure-docker ${{ env.REGION }}-docker.pkg.dev --quiet
          docker build -t ${{ env.REGION }}-docker.pkg.dev/${{ env.PROJECT_ID }}/${{ env.SERVICE }}:${{ github.sha }} .
          docker push ${{ env.REGION }}-docker.pkg.dev/${{ env.PROJECT_ID }}/${{ env.SERVICE }}:${{ github.sha }}

      - name: Deploy to Cloud Run
        run: |
          gcloud run deploy ${{ env.SERVICE }} \
            --image ${{ env.REGION }}-docker.pkg.dev/${{ env.PROJECT_ID }}/${{ env.SERVICE }}:${{ github.sha }} \
            --region ${{ env.REGION }} \
            --platform managed \
            --quiet

env:
  PROJECT_ID: your-project-id   # configure this
  REGION: us-central1            # configure this
  SERVICE: your-service-name     # configure this

Deploy to Fly.io (add to any pipeline above)

yaml

- uses: superfly/flyctl-actions/setup-flyctl@fc7b7fafba7d2e9c8b03b8a90b9d8ea3d9b3f9e1 # master
- run: flyctl deploy --remote-only
  env:
    FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
    # Secret to configure: FLY_API_TOKEN — from `flyctl auth token`

Step 3: Add Cache Strategy

Pick the right cache key for the stack — already included in the templates above. General rule:

Node: cache keyed to package-lock.json or pnpm-lock.yaml or yarn.lock
Python/uv: enable-cache: true in setup-uv — keyed to uv.lock automatically
Go: cache: true in setup-go — keyed to go.sum automatically
Docker: use cache-from: type=gha and cache-to: type=gha,mode=max with docker/build-push-action
Rust: cache ~/.cargo/registry, ~/.cargo/git, target/ keyed to Cargo.lock

Step 4: Secrets Checklist

Output a checklist of every secret the pipeline needs. Never hardcode values — only placeholders.

Format:

Secrets to configure in GitHub → Settings → Secrets and variables → Actions:

□ GCP_SA_KEY         — base64-encoded GCP service account JSON
                       roles needed: roles/run.admin, roles/iam.serviceAccountUser
□ FLY_API_TOKEN      — from `flyctl auth token`
□ DATABASE_URL       — production database connection string

Step 5: Output

Write the pipeline file directly:

GitHub Actions → .github/workflows/ci.yml
GitLab CI → .gitlab-ci.yml
Cloud Build → cloudbuild.yaml

Then output a summary:

┌─ Pipeline written ──────────────────────────────────────────┐
│                                                              │
│  File:     .github/workflows/ci.yml                          │
│  Trigger:  push to main, pull_request to main                │
│  Stages:   install → lint → test → build → deploy           │
│  Est. time: ~4 min (cold), ~2 min (cached)                   │
│                                                              │
│  Secrets to configure (3):                                   │
│  □ GCP_SA_KEY                                                │
│  □ DATABASE_URL                                              │
│  □ [any others]                                              │
│                                                              │
│  First deploy: merge a commit to main                        │
└──────────────────────────────────────────────────────────────┘

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

Files

SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/relay-pipeline of jeremylongshore/tons-of-skills-marketplace.

SKILL.md
.claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Relay Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Relay Pipeline compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Relay Pipeline this skilljeremylongshore/tons-of-skills-marketplace	2.8k	—	~2.4k	Automated safety check: Notes	MIT	yesterday
Reproduce macOS Python FlavorsNuitka/Nuitka	15k	—	~1.7k	Automated safety check: Pass	AGPL-3.0	today
CI Pipeline Synthesizerkajisho5/ffmpeg-skill	1.9k	1 repos	~1.1k	Automated safety check: Pass	MIT	yesterday
DDNS Build and Release MaintenanceNewFuture/DDNS	4.7k	—	~444	Automated safety check: Pass	MIT	3 days ago
Audit Reviewtestflows/TestFlows-GitHub-Hetzner-Runners	102	—	~2.1k	Automated safety check: Pass	Custom licence	19 days ago
Dependencies Managementmaread99/market_prices	106	—	~2.4k	Automated safety check: Notes	MIT	yesterday

Similar skills

Reproduce macOS Python Flavors
Nuitka/Nuitka
Reproduce macOS Nuitka issues across Python distributions and GitHub Actions Python packaging.
15k GitHub stars~1.7k tokensUpdated today
DevOps & CloudAuto-check passed
CI Pipeline Synthesizer
kajisho5/ffmpeg-skill
Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.
1.9k GitHub starsUsed in 1 repo~1.1k tokens
DevOps & CloudAuto-check passed
DDNS Build and Release Maintenance
NewFuture/DDNS
Maintains the DDNS project's GitHub Actions, Docker and Nuitka builds, packaging and release preparation without touching publishing credentials.
4.7k GitHub stars~444 tokensUpdated 3 days ago
DevOps & CloudAuto-check passed
Audit Review
testflows/TestFlows-GitHub-Hetzner-Runners
Perform deep feature audits with transition-matrix and logical fault-injection validation.
102 GitHub stars~2.1k tokensUpdated 19 days ago
DevOps & CloudAuto-check passed
Dependencies Management
maread99/market_prices
instructions for updating and managing project dependencies (including Github actions).
106 GitHub stars~2.4k tokensUpdated yesterday
DevOps & CloudAuto-check: notes
Code Patterns
Aedelon/claude-code-blueprint
Reference patterns for REST APIs, pytest/vitest testing, Docker multi-stage builds, GitHub Actions CI/CD, PostgreSQL, TypeScript generics, Python async, and React Server Components.
120 GitHub stars~1.2k tokensUpdated 7 mo ago
DevOps & CloudAuto-check passed

Questions about Relay Pipeline

What does Relay Pipeline do?

Build a full CI/CD pipeline from scratch. An agent skill from jeremylongshore/tons-of-skills-marketplace. Relay Pipeline is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build a full CI/CD pipeline from scratch.

When should I use Relay Pipeline?

Relay Pipeline fits situations like: asked to set up CI/CD; create pipeline; automate deploys.

How do I install Relay Pipeline in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/relay-pipeline in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/relay-pipeline in your project. Claude Code loads it when a task matches its description.

How do I install Relay Pipeline in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/relay-pipeline in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/relay-pipeline in your project. Codex loads it when a task matches its description.

Can I use Relay Pipeline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill relay-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/relay-pipeline, .gemini/skills/relay-pipeline, .github/skills/relay-pipeline and .opencode/skills/relay-pipeline in your project.

What does Relay Pipeline need to run?

Going by SKILL.md and its folder, Relay Pipeline needs the command-line tools its instructions call (go, cargo and mvn) and credentials named GCP_SA_KEY and FLY_API_TOKEN. Our summary lists: Python 3; Node.js; Docker; A credential in GCP_SA_KEY; A credential in FLY_API_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.

Does Relay Pipeline access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Relay Pipeline safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Relay Pipeline use?

Relay Pipeline is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Relay Pipeline use?

About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Relay Pipeline?

Skills that share tags, products or a category with Relay Pipeline: Reproduce macOS Python Flavors (Nuitka/Nuitka, 15k stars), CI Pipeline Synthesizer (kajisho5/ffmpeg-skill, 1.9k stars), DDNS Build and Release Maintenance (NewFuture/DDNS, 4.7k stars) and Audit Review (testflows/TestFlows-GitHub-Hetzner-Runners, 102 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Relay Pipeline?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Relay Pipeline

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Build CI/CD Pipeline

Step 0: Read the Project

Step 1: Determine What to Run

Step 2: Write the Pipeline Config

GitHub Actions — Node.js (npm/pnpm/yarn)

GitHub Actions — Python (uv)

GitHub Actions — Go

Deploy to Cloud Run (add to any pipeline above)

Deploy to Fly.io (add to any pipeline above)

Step 3: Add Cache Strategy

Step 4: Secrets Checklist

Step 5: Output

Delivery

Files

Compare with similar skills

Similar skills

More from jeremylongshore/tons-of-skills-marketplace

Related

Questions about Relay Pipeline