Agent skill

CI Maintenance

by foldkit in foldkit/foldkit

GitHub Actions maintenance. An agent skill from foldkit/foldkit.

MITAuto-check passedDevOps & Cloud

Install CI Maintenance

skills CLI
$ npx skills add foldkit/foldkit --skill ci-maintenance -a claude-code

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

GitHub CLI
$ gh skill install foldkit/foldkit ci-maintenance --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/foldkit/foldkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/repos/effect/.agents/skills/ci-maintenance .claude/skills/ci-maintenance && 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
ci-maintenance
GitHub stars
918
Token cost
~678 tokens
SKILL.md length
314 words
Files
2
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

GitHub Actions maintenance. An agent skill from foldkit/foldkit.

  • Works in 7 steps: Decide whether this is a review or an… → Inspect every affected workflow,… → For each job, record the trigger,… → …
  • Reviewing workflows
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Composite actions

What it does

CI Maintenance is an agent skill from foldkit/foldkit. GitHub Actions maintenance. Use when authoring or reviewing workflows or composite actions, especially event, permission, action-reference, artifact, setup, or concurrency changes.

Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `privileged-workflows.md`).

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions. The licence is MIT.

When your agent uses it

  • Reviewing workflows
  • Composite actions
  • Especially event
  • Action-reference

Example prompts

  • “/ci-maintenance”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Decide whether this is a review or an implementation. Reviews produce
  2. Inspect every affected workflow, composite action, and caller. List all
  3. For each job, record the trigger, actor/fork status, workflow revision,
  4. Consult current GitHub documentation for every platform-sensitive decision.
  5. Apply every applicable rule
  6. For forks, privileged credentials, publication, or cross-run data, read
  7. Run the narrowest syntax and repository checks, inspect the complete diff,

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md.

    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 no API keys, tokens, secrets or passwords.

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

Context cost

CI Maintenance loads about 678 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 314 words of instructions outside code blocks.

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

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 foldkit/foldkit at commit d21db42, republished under its MIT licence (© foldkit). 314 words, ~678 tokens.

Download SKILL.mdSave it as .claude/skills/ci-maintenance/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ci-maintenance
description
GitHub Actions maintenance. Use when authoring or reviewing workflows or composite actions, especially event, permission, action-reference, artifact, setup, or concurrency changes.

Audit the trust boundary before editing. This skill owns Actions event semantics, workflow security, permissions, action pinning, setup reuse, untrusted inputs, timeouts, concurrency, and artifact trust boundaries.

Workflow

  1. Decide whether this is a review or an implementation. Reviews produce evidence-backed findings without editing; implementations continue through the smallest boundary-preserving change.
  2. Inspect every affected workflow, composite action, and caller. List all affected jobs and actions before proceeding.
  3. For each job, record the trigger, actor/fork status, workflow revision, checked-out revision, permissions, credentials, and every external input and consumer. Include artifacts, caches, outputs, PR fields, refs, dispatch inputs, generated files, and called actions.
  4. Consult current GitHub documentation for every platform-sensitive decision. Repository examples establish local convention, not platform semantics.
  5. Apply every applicable rule:
    • Default workflow permissions to empty and grant minimal job permissions.
    • Reuse the repository's shared setup action unless the environment must differ.
    • Give executable jobs intentional matrices and realistic timeouts.
    • Pin external actions and reusable workflows to full commit SHAs with readable release comments; verify each SHA belongs to that upstream release.
    • Analyze event choice, checkout revision, and credential persistence together.
    • Pass untrusted expressions through environment variables; validate and quote them before use.
    • Derive concurrency from interruption safety.
  6. For forks, privileged credentials, publication, or cross-run data, read privileged-workflows.md.
  7. Run the narrowest syntax and repository checks, inspect the complete diff, and identify behavior testable only on GitHub-hosted runners.

For local patterns, inspect the current shared setup action and the nearest workflow with the same trust boundary. Use ordinary check workflows for routine precedent and privileged publication workflows only for equivalent trust boundaries.

The task is complete when every affected job and caller has a recorded trust boundary, every applicable rule has evidence or a compensating control, local checks pass, and GitHub-only verification is identified. Reviews report every failure with evidence; implementations resolve every failure and contain only intended behavior.

© foldkit, 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 repos/effect/.agents/skills/ci-maintenance of foldkit/foldkit.

  • SKILL.md
  • privileged-workflows.md

Open the folder on GitHubat commit d21db42

Compare with similar skills

CI Maintenance 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.

CI Maintenance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
CI Maintenance this skillfoldkit/foldkit918—~678Automated safety check: PassMIT
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
GitHub Actions Templatesbartstc/vite-ts-react-template12214 repos~1.9kAutomated safety check: PassMIT
Nushellccusage/ccusage19k—~938Automated safety check: PassCustom licence
Repo Hygiene Scan and FixQwenLM/qwen-code28k—~1.7kAutomated safety check: PassApache-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence

Similar skills

  • 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
  • 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
  • Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.

    28k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • 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
  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

More from foldkit/foldkit

All 18 skills in this repo
  • Commit Changes

    foldkit/foldkit

    Create a git commit in the Foldkit monorepo with changeset enforcement and formatting.

    918 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Foldkit

    foldkit/foldkit

    A skill your agent uses whenever working with Foldkit. An agent skill from foldkit/foldkit.

    918 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Outline, draft, or revise a Foldkit version release blog post using the repository's announcement style and editorial preferences.

    918 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Audit Program

    foldkit/foldkit

    Audit an existing Foldkit program against the architecture, conventions, and quality bar.

    918 GitHub stars~7.2k tokensUpdated today
    Auto-check passed
  • Generate Program

    foldkit/foldkit

    Generate a complete, idiomatic Foldkit program from a natural language description.

    918 GitHub stars~20k tokensUpdated today
    Auto-check passed
  • Changesets

    foldkit/foldkit

    Concise PR finalization changesets. An agent skill from foldkit/foldkit.

    918 GitHub stars~923 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about CI Maintenance

What does CI Maintenance do?

GitHub Actions maintenance. An agent skill from foldkit/foldkit. CI Maintenance is an agent skill from foldkit/foldkit. GitHub Actions maintenance.

When should I use CI Maintenance?

CI Maintenance fits situations like: reviewing workflows; composite actions; especially event; action-reference.

How do I install CI Maintenance in Claude Code?

Run `npx skills add foldkit/foldkit --skill ci-maintenance -a claude-code`. Or copy the skill folder (repos/effect/.agents/skills/ci-maintenance in foldkit/foldkit) into .claude/skills/ci-maintenance in your project. Claude Code loads it when a task matches its description.

How do I install CI Maintenance in Codex?

Run `npx skills add foldkit/foldkit --skill ci-maintenance -a codex`. Or copy the skill folder (repos/effect/.agents/skills/ci-maintenance in foldkit/foldkit) into .agents/skills/ci-maintenance in your project. Codex loads it when a task matches its description.

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

What does CI Maintenance need to run?

SKILL.md names no scripts, command-line tools or credentials: CI Maintenance is instructions for the agent only.

Does CI Maintenance 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 CI Maintenance 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 CI Maintenance use?

CI Maintenance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CI Maintenance use?

About 678 tokens (SKILL.md is roughly 2.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 CI Maintenance?

Skills that share tags, products or a category with CI Maintenance: Analyze GitHub Action Logs (withastro/astro, 63k stars), GitHub Actions Templates (bartstc/vite-ts-react-template, 122 stars), Nushell (ccusage/ccusage, 19k stars) and Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CI Maintenance?

foldkit (a GitHub organization) maintains it in foldkit/foldkit, which has 918 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 8, 2026.

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