Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment.

MITAuto-check: notesDevOps & Cloud

Install Relay Recon

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace relay-recon --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-recon .claude/skills/relay-recon && 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/

Facts

Skill name
relay-recon
GitHub stars
2.8k
Token cost
~896 tokens
SKILL.md length
308 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment.

  • Works in 6 steps: Detect Environment → Read All Pipeline Configs → Map the Pipeline Flow → …
  • Asked how does this deploy
  • SKILL.md covers Steps and Delivery
  • Needs API_KEY

What it does

Relay Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".

Its SKILL.md is about 900 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. 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 how does this deploy
  • Map the pipeline
  • Understand CI/CD

Example prompts

  • “how does this deploy”
  • “map the pipeline”
  • “understand CI/CD”
  • “/relay-recon”

Requirements

  • Docker
  • A credential in API_KEY
  • Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion

Workflow steps

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

  1. Detect Environment
  2. Read All Pipeline Configs
  3. Map the Pipeline Flow
  4. Identify Key Details
  5. Assess Risks
  6. Present the Recon Report

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
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    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:

    • API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Relay Recon loads about 896 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 308 words of instructions outside code blocks.

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

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, Bash, Glob, Grep, WebFetch, WebSearch, 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). 308 words, ~896 tokens.

Download SKILL.mdSave it as .claude/skills/relay-recon/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
relay-recon
description
Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".
allowed-tools
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version
0.6.4
author
tonone-ai <hello@tonone.ai>
license
MIT

Pipeline Reconnaissance

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

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

Steps

Step 0: Detect Environment
bash
ls -a

Identify the CI platform, deployment targets, container configs, and infrastructure-as-code files.

Step 1: Read All Pipeline Configs

Read every pipeline and deployment configuration in the project:

bash
cat .github/workflows/*.yml 2>/dev/null
cat .gitlab-ci.yml 2>/dev/null
cat cloudbuild.yaml 2>/dev/null
cat .circleci/config.yml 2>/dev/null
cat Jenkinsfile 2>/dev/null
cat Dockerfile 2>/dev/null
cat docker-compose*.yml 2>/dev/null

Also check for deployment configs: Kubernetes manifests, fly.toml, render.yaml, vercel.json, netlify.toml, app.yaml, terraform files.

Step 2: Map the Pipeline Flow

Trace the full path from code commit to production:

  1. Trigger — what events start the pipeline (push, PR, tag, manual, schedule)
  2. Build — how the artifact is produced (Docker build, npm build, go build, etc.)
  3. Test — what tests run and what can fail silently
  4. Deploy — how and where the artifact is deployed
  5. Verify — any post-deploy checks (smoke tests, health checks)
Step 3: Identify Key Details

Document:

  • Secrets locations — where secrets are referenced and what they're used for
  • Deployment targets — all environments (dev, staging, prod) and their URLs/identifiers
  • Manual steps — anything that requires human intervention
  • Rollback capability — whether rollback exists and how to trigger it
  • Average deploy time — estimate based on pipeline steps
  • Branch strategy — what branches trigger what environments
Step 4: Assess Risks

Evaluate:

  • Single points of failure in the pipeline
  • Steps with no error handling or retry logic
  • Missing stages (no tests, no smoke tests, no rollback)
  • Blast radius of a bad deploy (all traffic at once vs. gradual)
  • Recovery time estimate if something goes wrong
Step 5: Present the Recon Report

Format as:

## Pipeline Map

**CI Platform:** [platform]
**Deploy Target:** [target]
**Estimated Deploy Time:** [X minutes]

### Flow
trigger (push to main) → install → lint → test → build → deploy staging → smoke test → deploy prod

### Environments
| Environment | Branch   | URL              | Auto-deploy |
|-------------|----------|------------------|-------------|
| staging     | develop  | staging.app.com  | yes         |
| production  | main     | app.com          | yes         |

### Secrets
- `DATABASE_URL` — used in deploy step
- `API_KEY` — used in test + deploy

### Risk Assessment
- **Rollback:** [exists/missing] — [how to trigger]
- **Blast radius:** [all-at-once / gradual]
- **Recovery time:** ~[X] minutes
- **Gaps:** [missing stages or protections]

Factual and actionable. Map for someone taking over the project.

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.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Relay Recon 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 Recon compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Relay Recon this skilljeremylongshore/tons-of-skills-marketplace2.8k—~896Automated safety check: NotesMIT
Monitor CInrwl/nx29k6 repos~4.7kAutomated safety check: PassMIT
Terraform and OpenTofu Guideagentscope-ai/QwenPaw36k6 repos~4.2kAutomated safety check: PassApache-2.0
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
Azure Pipelines Log Downloaderansible/ansible71k—~825Automated safety check: PassGPL-3.0
GitHub Actions Templatesbartstc/vite-ts-react-template12214 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Monitor CI

    nrwl/nx

    Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 6 repos~4.7k tokens
    DevOps & CloudAuto-check passed
  • Terraform and OpenTofu Guide

    agentscope-ai/QwenPaw

    Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.

    36k GitHub starsUsed in 6 repos~4.2k tokens
    DevOps & CloudAuto-check passed
  • Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed
  • Downloads Azure Pipelines CI logs for an Ansible pull request or build so the agent can analyze test failures, after asking you first.

    71k GitHub stars~825 tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • GitHub Actions Templates

    bartstc/vite-ts-react-template

    Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.

    122 GitHub starsUsed in 14 repos~1.9k tokens
    DevOps & CloudAuto-check passed
  • Nushell

    ccusage/ccusage

    Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.

    19k GitHub stars~938 tokensUpdated today
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Relay Recon

What does Relay Recon do?

Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Relay Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment.

When should I use Relay Recon?

Relay Recon fits situations like: asked how does this deploy; map the pipeline; understand CI/CD.

How do I install Relay Recon in Claude Code?

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

How do I install Relay Recon in Codex?

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

Can I use Relay Recon 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-recon -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-recon, .gemini/skills/relay-recon, .github/skills/relay-recon and .opencode/skills/relay-recon in your project.

What does Relay Recon need to run?

Going by SKILL.md and its folder, Relay Recon needs credentials named API_KEY. Our summary lists: Docker; A credential in API_KEY. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion.

Does Relay Recon 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 Recon 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 Recon use?

Relay Recon 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 Recon use?

About 896 tokens (SKILL.md is roughly 3.6k 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 Recon?

Skills that share tags, products or a category with Relay Recon: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Analyze GitHub Action Logs (withastro/astro, 63k stars) and Azure Pipelines Log Downloader (ansible/ansible, 71k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Relay Recon?

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.