relay-audit

Audit CI/CD pipelines for slowness, security issues, and reliability gaps.

69|8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tonone-ai/tonone --skill relay-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relay-audit
Source: https://github.com/tonone-ai/tonone/tree/main/team/relay/skills/relay-audit
Command: npx skills add https://github.com/tonone-ai/tonone --skill relay-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit existing CI/CD pipelines for slowness, security issues, and reliability gaps, enabling teams to quickly identify bottlenecks and risk areas.

Core Features & Use Cases

  • Detects slow steps, missing caching, insecure configurations, and weak rollout strategies across GitHub Actions, GitLab CI, CircleCI, and Jenkins.
  • Flags security issues such as unpinned actions, leaked secrets, overly permissive credentials, and proposes concrete mitigations.
  • Use case: Run an audit when CI/CD pipelines underperform or fail to meet reliability targets, then implement recommended fixes.

Quick Start

Detect the CI/CD environment and follow the defined steps to generate a structured pipeline audit report.

Frequently Asked Questions about relay-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a CI/CD pipeline for slow build times and security gaps?

To audit a CI/CD pipeline, the tool reads configuration files to check step timings, caching, and security practices. It then outputs a structured report highlighting bottlenecks, insecure configurations, and weak rollout strategies alongside recommended fixes.

What security issues should I look for in GitHub Actions and GitLab CI configurations?

Common security issues in CI/CD configurations include unpinned actions, leaked secrets, and overly permissive credentials. An audit flags these vulnerabilities and proposes concrete mitigations to secure your deployment pipeline across platforms like GitHub Actions and GitLab CI.

Does CI/CD pipeline auditing work across different platforms like CircleCI and Jenkins?

Yes, CI/CD pipeline auditing supports GitHub Actions, GitLab CI, CircleCI, and Jenkins. The audit detects slow steps, missing caching, insecure configurations, and weak rollout strategies across these popular platforms.

When should I run a reliability audit on my deployment pipeline?

You should run a reliability audit when CI/CD pipelines underperform or fail to meet reliability targets. The audit checks deployment health and weak rollout strategies, outputting a structured report that enables teams to quickly identify and implement recommended fixes.

What is the best way to identify missing caching in a slow CI/CD pipeline?

The best way to identify missing caching is to run an audit that reads pipeline configurations and checks step timings. The audit detects slow steps and missing caching mechanisms, producing a structured report with concrete recommendations for optimization.