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

Update Vortex CI Runner

by drevops in drevops/vortex

A skill your agent uses when testing a canary build of 'drevops/ci-runner' against a Vortex project before official release, or when incrementing the pinned 'drevops/ci-runner' version after a new…

GPL-3.0Auto-check passedDevOps & Cloud

Install Update Vortex CI Runner

skills CLI
$ npx skills add drevops/vortex --skill update-vortex-ci-runner -a claude-code

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

GitHub CLI
$ gh skill install drevops/vortex update-vortex-ci-runner --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/drevops/vortex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/update-vortex-ci-runner .claude/skills/update-vortex-ci-runner && 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
update-vortex-ci-runner
GitHub stars
133
Token cost
~1.6k tokens
SKILL.md length
778 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
GPL-3.0

At a glance

A skill your agent uses when testing a canary build of 'drevops/ci-runner' against a Vortex project before official release, or when incrementing the pinned 'drevops/ci-runner' version after a new…

  • Works in 2 steps: Canary → Release Pin
  • Testing a canary build of drevops/ci-runner against a Vortex project before official release
  • SKILL.md covers When to Use, Prerequisites, Phase 1: Canary and Phase 2: Release Pin, plus 2 more sections
  • Calls git, gh and docker

What it does

Update Vortex CI Runner is an agent skill from drevops/vortex. Use when testing a canary build of 'drevops/ci-runner' against a Vortex project before official release, or when incrementing the pinned 'drevops/ci-runner' version after a new release. Triggers on phrases like 'test ci-runner canary', 'update ci-runner', 'switch ci-runner to canary', 'bump ci-runner to X.Y.Z'.

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

It sits in DevOps & Cloud, covering Deployment. It works with Docker. The repository describes itself as: 🌀 Drupal project template. The licence is GPL-3.0.

When your agent uses it

  • Testing a canary build of drevops/ci-runner against a Vortex project before official release
  • Incrementing the pinned drevops/ci-runner version after a new release
  • Phrases like test ci-runner canary
  • Update ci-runner

Example prompts

  • “drevops/ci-runner”
  • “test ci-runner canary”
  • “update ci-runner”
  • “/update-vortex-ci-runner”

Requirements

  • Docker

Workflow steps

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

  1. Canary
  2. Release Pin

What it can do on your machine

Read from SKILL.md and the folder at commit 3b9ec25. 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:

    • git
    • gh
    • docker

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

  • Network

    No URLs in SKILL.md. Its commands use git, gh and docker, which can reach the network depending on how they are called.

    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

Update Vortex CI Runner loads about 1.6k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 778 words of instructions outside code blocks.

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

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 drevops/vortex at commit 3b9ec25, republished under its GPL-3.0 licence (© drevops). 778 words, ~1,595 tokens.

Download SKILL.mdSave it as .claude/skills/update-vortex-ci-runner/SKILL.md (or your agent's skills folder).
name
update-vortex-ci-runner
description
Use when testing a canary build of 'drevops/ci-runner' against a Vortex project before official release, or when incrementing the pinned 'drevops/ci-runner' version after a new release. Triggers on phrases like 'test ci-runner canary', 'update ci-runner', 'switch ci-runner to canary', 'bump ci-runner to X.Y.Z'.
user-invocable
true

Vortex Update CI Runner

Two-phase workflow for verifying a new drevops/ci-runner release on a Vortex-based Drupal project:

  • Phase 1 (Canary): Switch all drevops/ci-runner image references to :canary (no SHA pin), open a PR, monitor CI. If green, STOP and notify the user so they can cut the official release.
  • Phase 2 (Release): After the user confirms a release version, roll the same PR forward to pin :NEW_VERSION@sha256:NEW_SHA, push, monitor CI. On green, notify the user the PR is ready to merge.

When to Use

  • User says 'test ci-runner canary' / 'switch ci-runner to canary' / 'try the new ci-runner'.
  • User says 'update ci-runner to X.Y.Z' (skip to Phase 2 if no canary needed).
  • Vortex release prep needs a ci-runner verification.

Do NOT use for uselagoon/* images (Renovate handles those) or ci-builder (different image).

Prerequisites

  • Working in a Vortex-based project (look for .vortex/ directory or drevops/ci-runner references).
  • gh CLI authenticated.
  • Docker available (only needed for the Phase 2 SHA lookup).
  • Clean working tree.

Phase 1: Canary

1. Discover references

The file list is not fixed: older or downstream projects may have it in more places. Always rediscover.

bash
grep -rln "drevops/ci-runner" --include="*.yml" .

Repeat for *.yaml and Dockerfile*. Exclude */tests/Fixtures/* and */test/Fixtures/* paths since those are snapshots used by installer tests, not live CI configs.

Record the current version and SHA before changing anything: you need to know what you are rolling forward from in case of rollback.

2. Branch
bash
git checkout -b feature/update-ci-runner

This branch is reused for Phase 2; do not create a new branch when the release version is provided.

3. Replace image references

For every non-fixture file from Step 1, replace:

text
drevops/ci-runner:<VERSION>@sha256:<HASH>

with:

text
drevops/ci-runner:canary

Drop the SHA pin in canary mode. Pinning a SHA defeats the canary: CI re-runs would test the same frozen build, not whatever the canary tag currently points to. The whole point of the canary phase is to track a moving target.

Use the Edit tool with replace_all: true per file. Verify with grep afterwards: the only remaining hits should be in fixture paths.

4. Commit and push

Stage specific files (never git add .):

bash
git add .github/workflows/build-test-deploy.yml
bash
git commit -m "Switched 'drevops/ci-runner' to 'canary' for verification."
bash
git push -u origin feature/update-ci-runner
5. Open PR

Invoke the /open-pr skill. PR title:

text
Tested 'drevops/ci-runner' canary build.

PR body should note: this is a canary test (NOT for merge yet), the previous pinned version, files changed, and that the next step is for the user to release a new drevops/ci-runner once CI passes.

6. Monitor CI

Watch GitHub Actions via gh pr checks <PR> and CircleCI via the PR link.

On failure: Diagnose before reporting. Common causes:

  • Tool version drift in canary (PHP, Node, Composer bumped in the ci-runner image but pinned in project configs: composer.json config.platform.php, phpstan.neon phpVersion, phpcs.xml testVersion).
  • A tool removed from the canary image.
  • Cache key issues (rare: cache keys are tied to Lagoon versions, not ci-runner).
  • Image pull / registry timeout.

Report with: failing job name, failing step, ~30 lines of the most relevant log, and your hypothesis. Do not paste raw logs without a hypothesis.

On success: STOP. Do not merge. Tell the user:

Canary verification passed: CI is green on <PR URL>. Ready for you to cut the new drevops/ci-runner release. Let me know the new version (e.g. 26.4.0) when ready.

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

Phase 2: Release Pin

Triggered when the user confirms a new released version (e.g. 'released as 26.4.0').

1. Get the SHA digest
bash
docker pull drevops/ci-runner:<NEW_VERSION>
bash
docker inspect --format="{{index .RepoDigests 0}}" drevops/ci-runner:<NEW_VERSION>

The output is drevops/ci-runner@sha256:<HASH>. Record <HASH>.

If docker is unavailable, use docker manifest inspect drevops/ci-runner:<NEW_VERSION> and read the linux/amd64 digest.

2. Replace canary references

Rediscover files (rerun the grep from Phase 1 Step 1). Replace:

text
drevops/ci-runner:canary

with:

text
drevops/ci-runner:<NEW_VERSION>@sha256:<NEW_HASH>
3. Commit and push on the same branch
bash
git commit -m "Updated 'drevops/ci-runner' to '<NEW_VERSION>'."
bash
git push
4. Update PR metadata
bash
gh pr edit <PR> --title "Updated 'drevops/ci-runner' to '<NEW_VERSION>'."

Add a comment summarising the canary -> release transition.

5. Monitor CI

Same as Phase 1 Step 6. On success:

CI green on pinned <NEW_VERSION>. PR <URL> ready to merge.

Do NOT merge: the user merges.

Red Flags

  • About to pin a SHA in Phase 1: don't. Canary needs the moving tag.
  • About to edit a file under tests/Fixtures/: don't. Those are test snapshots.
  • About to merge the PR: don't. User merges.
  • About to use gh pr create: don't. Use /open-pr.
  • About to start Phase 2 without Phase 1 CI green: confirm with user first.
  • Hardcoding the file list from this skill: don't. Always grep first.

Common Mistakes

MistakeFix
Hardcoded list of filesAlways grep: the list grows over time
Included fixture files in editsExclude fixture snapshot paths only (for example */tests/Fixtures/* and */test/Fixtures/*)
Kept SHA pin in canary phaseStrip SHA: canary tag must be unpinned to test moving target
Used git add .Stage specific files only
Reported CI failure rawRead failing step, form a hypothesis, then report
Created PR via gh pr createUse /open-pr skill
New branch for Phase 2Reuse the Phase 1 branch and PR

© drevops, GPL-3.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 .claude/skills/update-vortex-ci-runner of drevops/vortex.

Open the folder on GitHubat commit 3b9ec25

Compare with similar skills

Update Vortex CI Runner 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.

Update Vortex CI Runner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update Vortex CI Runner this skilldrevops/vortex133—~1.6kAutomated safety check: PassGPL-3.0
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Reflexo ReleaseMyriad-Dreamin/typst.ts1.2k—~1.5kAutomated safety check: PassApache-2.0
Aspiremicrosoft/aspire.dev1964 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes

  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Reflexo Release

    Myriad-Dreamin/typst.ts

    Guide Reflexo/typst.ts release preparation and operator handoffs.

    1.2k GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Aspire

    microsoft/aspire.dev

    Official

    Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.

    196 GitHub starsUsed in 4 repos~1.1k tokens
    DevOps & CloudAuto-check passed

  • Classical Poem Silk Video

    Mr-funny/hbg-classical-poem-silk-video

    Turn Chinese classical poems and ci into coherent vertical Chinese-art videos with poem-driven scene grouping, GPT ImageGen stills, Docker-only Gemini I2V, retained model-generated ambience, Gemini…

    361 GitHub stars~1.6k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

More from drevops/vortex

  • Create Vortex Tooling Release Notes

    drevops/vortex

    A skill your agent uses when preparing release notes for the 'drevops/vortex-tooling' Composer package, published as a read-only mirror of '.vortex/tooling/' from the Vortex monorepo.

    133 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Propagate Vortex Main To 2x

    drevops/vortex

    Forward-port commits that landed on 'main' into the deviated '2.x' development branch.

    133 GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • Update Vortex Dev Deps

    drevops/vortex

    A skill your agent uses when refreshing Composer and Yarn dev dependencies across the three '.vortex/' subsystems (docs, installer, tests).

    133 GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • Prepare Vortex Release

    drevops/vortex

    Prepare the Vortex codebase for a release - run checklist operations (deps, container images, PHP version, cache bumps, docs) and generate release notes at .artifacts/release-VERSION/release-notes.md.

    133 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Update Vortex CI Runner

What does Update Vortex CI Runner do?

A skill your agent uses when testing a canary build of 'drevops/ci-runner' against a Vortex project before official release, or when incrementing the pinned 'drevops/ci-runner' version after a new…. Update Vortex CI Runner is an agent skill from drevops/vortex. Use when testing a canary build of 'drevops/ci-runner' against a Vortex project before official release, or when incrementing the pinned 'drevops/ci-runner' version after a new release.

When should I use Update Vortex CI Runner?

Update Vortex CI Runner fits situations like: testing a canary build of drevops/ci-runner against a Vortex project before official release; incrementing the pinned drevops/ci-runner version after a new release; phrases like test ci-runner canary; update ci-runner.

How do I install Update Vortex CI Runner in Claude Code?

Run `npx skills add drevops/vortex --skill update-vortex-ci-runner -a claude-code`. Or copy the skill folder (.claude/skills/update-vortex-ci-runner in drevops/vortex) into .claude/skills/update-vortex-ci-runner in your project. Claude Code loads it when a task matches its description.

How do I install Update Vortex CI Runner in Codex?

Run `npx skills add drevops/vortex --skill update-vortex-ci-runner -a codex`. Or copy the skill folder (.claude/skills/update-vortex-ci-runner in drevops/vortex) into .agents/skills/update-vortex-ci-runner in your project. Codex loads it when a task matches its description.

Can I use Update Vortex CI Runner 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 drevops/vortex --skill update-vortex-ci-runner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-vortex-ci-runner, .gemini/skills/update-vortex-ci-runner, .github/skills/update-vortex-ci-runner and .opencode/skills/update-vortex-ci-runner in your project.

What does Update Vortex CI Runner need to run?

Going by SKILL.md and its folder, Update Vortex CI Runner needs the command-line tools its instructions call (git, gh and docker). Our summary lists: Docker.

Does Update Vortex CI Runner access the network?

SKILL.md contains no URLs. Its commands use git, gh and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Update Vortex CI Runner 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 Update Vortex CI Runner use?

Update Vortex CI Runner is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Update Vortex CI Runner use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 Update Vortex CI Runner?

Skills that share tags, products or a category with Update Vortex CI Runner: GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars) and Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Update Vortex CI Runner?

drevops (a GitHub organization) maintains it in drevops/vortex, which has 133 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: drevops/vortex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.