New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Trigger Payload Job

by openshift-eng in openshift-eng/ai-helpers

MUST be used whenever triggering payload testing on a PR. An agent skill from openshift-eng/ai-helpers.

Apache-2.0Auto-check passed

Install Trigger Payload Job

skills CLI
$ npx skills add openshift-eng/ai-helpers --skill trigger-payload-job -a claude-code

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

GitHub CLI
$ gh skill install openshift-eng/ai-helpers trigger-payload-job --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/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ci/skills/trigger-payload-job .claude/skills/trigger-payload-job && 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
trigger-payload-job
GitHub stars
120
Token cost
~1.7k tokens
SKILL.md length
726 words
Files
1
Skills in repo
118
Repo updated
First seen
Licence
Apache-2.0

At a glance

MUST be used whenever triggering payload testing on a PR. An agent skill from openshift-eng/ai-helpers.

  • Works in 4 steps: Idempotency Check → Post Payload Commands → Poll for Bot Response → …
  • SKILL.md covers When to Use This Skill, Prerequisites, Job Triggering Limits and Implementation Steps, plus 3 more sections
  • Calls gh and curl; reaches github.com

What it does

Trigger Payload Job is an agent skill from openshift-eng/ai-helpers. MUST be used whenever triggering payload testing on a PR. Do not post payload commands without following this skill — the command syntax is specific and other formats will be silently ignored by the bot.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.

Example prompts

  • “/trigger-payload-job”

Workflow steps

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

  1. Idempotency Check
  2. Post Payload Commands
  3. Poll for Bot Response
  4. Extract URLs

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Trigger Payload Job loads about 1.7k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 726 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 726 words, ~1,690 tokens.

Download SKILL.mdSave it as .claude/skills/trigger-payload-job/SKILL.md (or your agent's skills folder).
name
trigger-payload-job
description
MUST be used whenever triggering payload testing on a PR. Do not post payload commands without following this skill — the command syntax is specific and other formats will be silently ignored by the bot.

Trigger Payload Job

This skill triggers payload validation jobs on a GitHub PR by posting the correct Prow commands as PR comments, then polls for the bot response to collect the resulting job URLs.

When to Use This Skill

This skill MUST be used whenever triggering payload testing on a PR. This includes revert PRs, draft experimental revert PRs, or any PR that needs payload validation. Do not post payload commands without following this skill — the command syntax is specific and other formats will be silently ignored by the bot.

Inputs (passed in-context by the caller):

  • pr_url: The GitHub PR URL to trigger jobs on (e.g., https://github.com/openshift/ovn-kubernetes/pull/3040)
  • org, repo, pr_number: Parsed from the PR URL
  • jobs: List of jobs to trigger, each with:
    • job_name: The full job name (e.g., aggregated-hypershift-ovn-conformance-4.22)
    • is_aggregated: Whether this is an aggregated job (has aggregated- prefix)
    • underlying_job_name: For aggregated jobs only — the underlying periodic job name (e.g., periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn-conformance). This MUST be extracted from the aggregated job's junit artifacts by the caller's analysis — it cannot be derived from the aggregated job name.
    • count: For aggregated jobs only — how many runs (default: 10). Use judgement: fewer runs when triggering many jobs to limit resource consumption, more when only one or two jobs need validation.

Prerequisites

  1. GitHub CLI (gh): Installed and authenticated
  2. Repository Access: User must have permission to comment on the PR

Job Triggering Limits

The caller is responsible for enforcing global limits before invoking this skill. However, this skill also enforces the following hard limits per invocation:

  • Non-aggregated jobs: No more than 5 per comment
  • Aggregated jobs: No more than 1 per comment. Aggregated jobs are expensive (they run many iterations), so only trigger one at a time. A second aggregated job should only be triggered after the first completes, and only if confirmation is needed.

If the jobs input exceeds these limits, trigger only the allowed number (prioritizing by the order provided) and return the remainder as skipped in the return format.

Implementation Steps

Step 1: Idempotency Check

Before posting new payload commands, check whether jobs were already triggered on this PR:

bash
gh api "repos/<org>/<repo>/issues/<pr_number>/comments?per_page=100&sort=created&direction=desc" \
  --jq '[.[] | select(.user.login == "openshift-ci[bot]" and (.body | contains("pr-payload-tests")))] | .[0] | .body'

If a pr-payload-tests.ci.openshift.org/runs/ci/<uuid> URL is found, reuse it — skip to Step 3 to extract prow job URLs from that page.

Show full SKILL.md (358 more words)Show less
Step 2: Post Payload Commands

First, validate each job entry. If any job has is_aggregated == true but underlying_job_name is empty or null, skip that job and return an error for it — do NOT post a comment with an incomplete command.

Build the comment body with one command per line. Use the correct command for each job type:

  • Aggregated jobs (is_aggregated == true):
    • If the aggregated job failed 10/10 runs, use /payload-job <underlying_job_name> instead of /payload-aggregate. A single successful run is sufficient to validate the revert when the original failure was 100%.
    • Otherwise, use /payload-aggregate <underlying_job_name> <count>
  • Non-aggregated jobs (is_aggregated == false): /payload-job <job_name>
bash
gh pr comment "<pr_url>" --body "<commands>"

Example with a mix of job types:

bash
gh pr comment "https://github.com/openshift/ovn-kubernetes/pull/3040" --body "/payload-aggregate periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn-conformance 10
/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn"

Common mistakes to avoid:

  • Do NOT use /payload <version> <stream> <filter> — this triggers a different workflow and does NOT include the PR's changes in the payload
  • Do NOT use the aggregated job name with /payload-job — aggregated jobs are not directly triggerable; you must use /payload-aggregate with the underlying job name
  • Do NOT use /payload-aggregate for non-aggregated jobs
Step 3: Poll for Bot Response

After posting the comment, wait ~30 seconds for the openshift-ci[bot] to process the commands, then poll for its reply:

bash
sleep 30
gh api "repos/<org>/<repo>/issues/<pr_number>/comments?per_page=100&sort=created&direction=desc" \
  --jq '[.[] | select(.user.login == "openshift-ci[bot]" and (.body | contains("pr-payload-tests")))] | .[0] | .body'

If no reply is found, retry up to 3 times with 30-second intervals. If still no reply after ~2 minutes, record the comment URL and report that manual checking is required.

Step 4: Extract URLs

From the bot reply, extract:

  1. payload_test_url: The pr-payload-tests.ci.openshift.org/runs/ci/<uuid> URL. This is the primary endpoint for checking overall job completion status — the page shows "AllJobsFinished" when all triggered jobs have completed.

  2. Individual prow job URLs: Fetch the payload_test_url page and extract prow job links:

bash
curl -sL "<payload_test_url>" | grep -oE 'https://prow\.ci\.openshift\.org/view/gs/[^/]+/logs/[^"]+' | sort -u

Each prow URL corresponds to one triggered job run.

Return Format

Return the collected data in this format:

PAYLOAD_JOB_RESULT:
  pr_url: <the PR URL>
  comment_url: <URL of the comment posted>
  payload_test_url: <pr-payload-tests URL, or empty if not found>
  prow_jobs:
    - job_name: <job name>
      prow_url: <individual prow URL>
    - ...
  skipped_jobs:
    - job_name: <job name>
      reason: "job trigger limit reached (max 5 non-aggregated, max 1 aggregated per invocation)"
    - ...
  status: triggered|reused|no_response|failed
  error: none|<description>

Error Handling

  • If the bot never replies, return status: no_response with the comment URL so the caller can check manually later.
  • If the PR doesn't exist or the user lacks permissions, return status: failed with the error message.
  • Do not retry indefinitely — 3 poll attempts is the maximum.

See Also

  • Used by: payload-experimental-reverts — triggers payload jobs for draft experimental revert PRs
  • Used by: stage-payload-reverts — triggers payload jobs for revert PRs

© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/ci/skills/trigger-payload-job of openshift-eng/ai-helpers.

Open the folder on GitHubat commit a627176

Compare with similar skills

Trigger Payload Job 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.

Trigger Payload Job compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Trigger Payload Job this skillopenshift-eng/ai-helpers120—~1.7kAutomated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow83k5 repos~1.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    83k GitHub starsUsed in 5 repos~1.3k tokens
    Research & ScienceAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed

  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.8k tokensUpdated today
    Research & ScienceAuto-check: notes

More from openshift-eng/ai-helpers

All 118 skills in this repo

  • Investigate CI Reliability

    openshift-eng/ai-helpers

    Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.

    120 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed

  • Address Review PR

    openshift-eng/ai-helpers

    Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.

    120 GitHub stars~2.9k tokensUpdated 2 days ago
    Auto-check passed

  • Categorize Activity Types

    openshift-eng/ai-helpers

    Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.

    120 GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

  • Has Review Work

    openshift-eng/ai-helpers

    Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.

    120 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed

  • Must Gather Analyzer

    openshift-eng/ai-helpers

    Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.

    120 GitHub stars~2.3k tokensUpdated 2 days ago
    Auto-check passed

  • Payload Autodl JSON

    openshift-eng/ai-helpers

    Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file

    120 GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Trigger Payload Job

What does Trigger Payload Job do?

MUST be used whenever triggering payload testing on a PR. An agent skill from openshift-eng/ai-helpers. Trigger Payload Job is an agent skill from openshift-eng/ai-helpers. MUST be used whenever triggering payload testing on a PR.

How do I install Trigger Payload Job in Claude Code?

Run `npx skills add openshift-eng/ai-helpers --skill trigger-payload-job -a claude-code`. Or copy the skill folder (plugins/ci/skills/trigger-payload-job in openshift-eng/ai-helpers) into .claude/skills/trigger-payload-job in your project. Claude Code loads it when a task matches its description.

How do I install Trigger Payload Job in Codex?

Run `npx skills add openshift-eng/ai-helpers --skill trigger-payload-job -a codex`. Or copy the skill folder (plugins/ci/skills/trigger-payload-job in openshift-eng/ai-helpers) into .agents/skills/trigger-payload-job in your project. Codex loads it when a task matches its description.

Can I use Trigger Payload Job 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 openshift-eng/ai-helpers --skill trigger-payload-job -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trigger-payload-job, .gemini/skills/trigger-payload-job, .github/skills/trigger-payload-job and .opencode/skills/trigger-payload-job in your project.

What does Trigger Payload Job need to run?

Going by SKILL.md and its folder, Trigger Payload Job needs the command-line tools its instructions call (gh and curl).

Does Trigger Payload Job access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Trigger Payload Job safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Trigger Payload Job use?

Trigger Payload Job is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Trigger Payload Job use?

About 1.7k tokens (SKILL.md is roughly 6.8k 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 Trigger Payload Job?

Skills that share tags, products or a category with Trigger Payload Job: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Trigger Payload Job?

openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.

Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.