Agent skill

CI Pipeline Synthesizer

Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.

MITAuto-check passedDevOps & Cloud

Install CI Pipeline Synthesizer

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill ci-pipeline-synthesizer -a claude-code

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

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill ci-pipeline-synthesizer --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/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ci-pipeline-synthesizer .claude/skills/ci-pipeline-synthesizer && 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/

Paste into Claude Code

Install the "ci-pipeline-synthesizer" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/ci-pipeline-synthesizer into .claude/skills/ci-pipeline-synthesizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-pipeline-synthesizer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/ci-pipeline-synthesizer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill ci-pipeline-synthesizer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill ci-pipeline-synthesizer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/ci-pipeline-synthesizer .agents/skills/ci-pipeline-synthesizer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ci-pipeline-synthesizer" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/ci-pipeline-synthesizer into .agents/skills/ci-pipeline-synthesizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-pipeline-synthesizer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill ci-pipeline-synthesizer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill ci-pipeline-synthesizer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/ci-pipeline-synthesizer .cursor/skills/ci-pipeline-synthesizer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ci-pipeline-synthesizer" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/ci-pipeline-synthesizer into .cursor/skills/ci-pipeline-synthesizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-pipeline-synthesizer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/kajisho5/ffmpeg-skill.git --path .claude/skills/ci-pipeline-synthesizer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill ci-pipeline-synthesizer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill ci-pipeline-synthesizer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/ci-pipeline-synthesizer .gemini/skills/ci-pipeline-synthesizer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ci-pipeline-synthesizer" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/ci-pipeline-synthesizer into .gemini/skills/ci-pipeline-synthesizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-pipeline-synthesizer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill ci-pipeline-synthesizer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill ci-pipeline-synthesizer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/ci-pipeline-synthesizer .github/skills/ci-pipeline-synthesizer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ci-pipeline-synthesizer" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/ci-pipeline-synthesizer into .github/skills/ci-pipeline-synthesizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-pipeline-synthesizer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add kajisho5/ffmpeg-skill --skill ci-pipeline-synthesizer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install kajisho5/ffmpeg-skill ci-pipeline-synthesizer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kajisho5/ffmpeg-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/ci-pipeline-synthesizer .opencode/skills/ci-pipeline-synthesizer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ci-pipeline-synthesizer" agent skill from https://github.com/kajisho5/ffmpeg-skill/tree/main/.claude/skills/ci-pipeline-synthesizer into .opencode/skills/ci-pipeline-synthesizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-pipeline-synthesizer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ci-pipeline-synthesizer
GitHub stars: 1.9k
Used in: 1 other repo
Token cost: ~1.1k tokens
SKILL.md length: 438 words
Files: 5 (incl. assets)
Skills in repo: 14
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.

Works in 5 steps: Identify Project Type → Select Template → Customize Configuration → …
Updating CI workflows for npm packages
SKILL.md covers Overview, Workflow, Template Features and Customization Examples, plus 2 more sections
Calls npm, python and go; reaches github.com

What it does

CI Pipeline Synthesizer is an agent skill from kajisho5/ffmpeg-skill. Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects. Use when creating or updating CI workflows for npm packages, Python packages, Go modules, Rust crates, or other library projects that need automated build and test pipelines. Includes templates for common package ecosystems with best practices for dependency caching, matrix testing, and artifact publishing.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including assets (for example `assets/github-actions-go.yml`, `assets/github-actions-nodejs.yml` and `assets/github-actions-python.yml`).

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

When your agent uses it

Updating CI workflows for npm packages
Python packages
Other library projects that need automated build and test pipelines

Example prompts

“/ci-pipeline-synthesizer”

Requirements

Python 3
Node.js

Workflow steps

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

Identify Project Type
Select Template
Customize Configuration
Place Workflow File
Verify Configuration

What it can do on your machine

Read from SKILL.md and the folder at commit 1f7e7e3. 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:
- npm
- python
- go
- cargo
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

CI Pipeline Synthesizer loads about 1.1k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 438 words of instructions outside code blocks.

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

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 kajisho5/ffmpeg-skill at commit 1f7e7e3, republished under its MIT licence (© kajisho5). 438 words, ~1,133 tokens.

Download SKILL.mdSave it as .claude/skills/ci-pipeline-synthesizer/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: ci-pipeline-synthesizer
description: Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects. Use when creating or updating CI workflows for npm packages, Python packages, Go modules, Rust crates, or other library projects that need automated build and test pipelines. Includes templates for common package ecosystems with best practices for dependency caching, matrix testing, and artifact publishing.

CI Pipeline Synthesizer

Overview

Generate production-ready GitHub Actions workflow files for library and package projects with automated build and test stages, dependency caching, and multi-version testing matrices.

Workflow

1. Identify Project Type

Determine the package ecosystem by examining project files:

Node.js/npm: package.json present
Python: setup.py, pyproject.toml, or requirements.txt present
Go: go.mod present
Rust: Cargo.toml present

2. Select Template

Use the appropriate template from assets/ based on project type:

github-actions-nodejs.yml - Node.js/npm packages
github-actions-python.yml - Python packages
github-actions-go.yml - Go modules
github-actions-rust.yml - Rust crates

3. Customize Configuration

Adapt the template to project-specific needs:

Test commands: Update test scripts to match project conventions

Node.js: npm test, npm run test:coverage
Python: pytest, python -m unittest
Go: go test ./...
Rust: cargo test

Build commands: Adjust build steps if needed

Node.js: npm run build (if build step exists)
Python: python -m build
Go: go build
Rust: cargo build --release

Version matrix: Modify tested versions based on support policy

Node.js: LTS versions (16.x, 18.x, 20.x)
Python: Active versions (3.9, 3.10, 3.11, 3.12)
Go: Recent versions (1.21, 1.22)
Rust: stable, beta (optional)

Trigger conditions: Adjust when pipeline runs

Default: Push to main/master, all pull requests
Custom: Specific branches, paths, or schedules

4. Place Workflow File

Create the workflow file at .github/workflows/ci.yml in the project root. If .github/workflows/ doesn't exist, create the directory structure first.

5. Verify Configuration

Check that the generated workflow:

Uses appropriate actions versions (e.g., actions/checkout@v4, actions/setup-node@v4)
Includes dependency caching for faster builds
Runs on appropriate triggers (push, pull_request)
Tests against relevant version matrices
Has clear job and step names

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

Template Features

All templates include:

Dependency caching: Speeds up builds by caching package managers
Matrix testing: Tests across multiple language/runtime versions
Parallel execution: Runs tests for different versions concurrently
Clear naming: Descriptive job and step names for easy debugging
Best practices: Uses recommended actions and configurations

Customization Examples

Add code coverage reporting:

yaml

- name: Upload coverage to Codecov
  uses: codecov/codecov-action@v3
  with:
    file: ./coverage.xml

Add linting step:

yaml

- name: Run linter
  run: npm run lint  # or: pylint, golangci-lint, cargo clippy

Restrict to specific branches:

yaml

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

Add scheduled runs:

yaml

on:
  schedule:
    - cron: '0 0 * * 0'  # Weekly on Sunday

Tips

Start with the template and customize incrementally
Test the workflow by creating a pull request or pushing to a test branch
Use actions/cache for dependencies to reduce build times
Keep matrix versions current with language support policies
Add status badges to README.md: ![CI](https://github.com/user/repo/workflows/CI/badge.svg)

Note for this repository (ffmpeg-skill)

This skill's generic templates assume ordinary language-toolchain dependencies (pip/npm/go/cargo). They do NOT model this repo's actual CI needs — installing a real ffmpeg binary per OS (apt/brew ffmpeg-full/choco), capturing its -filters/-encoders/-bsfs listings as an artifact, or the skipIf-based Windows test coverage in tests/test_contract.py — all of which .github/workflows/ci.yml already handles and this skill's templates would not reproduce. Treat this as reference/scaffolding for a plain Python/Node/Go/ Rust package elsewhere, not a drop-in replacement for this repo's own workflow.

Files

SKILL.md and 4 other files (assets) in .claude/skills/ci-pipeline-synthesizer of kajisho5/ffmpeg-skill.

SKILL.md
assets/github-actions-go.yml
assets/github-actions-nodejs.yml
assets/github-actions-python.yml
assets/github-actions-rust.yml

Open the folder on GitHubat commit 1f7e7e3

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in kajisho5/ffmpeg-skill, which our catalogue first saw on October 7, 2026.

ArabelaTso/Skills-4-SEskills/ci-pipeline-synthesizer

Compare with similar skills

CI Pipeline Synthesizer 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 Pipeline Synthesizer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
CI Pipeline Synthesizer this skillkajisho5/ffmpeg-skill	1.9k	1 repos	~1.1k	Automated safety check: Pass	MIT	yesterday
GitHub Actions CreatorFNOSP/FlyNarwhal	509	1 repos	~2.4k	Automated safety check: Pass	AGPL-3.0	2 days ago
GitHub Actions Supply Chain Pinningasyncapi/generator	1.1k	—	~1.9k	Automated safety check: Pass	Apache-2.0	yesterday
Dep Auditorlaolaoshiren/claude-code-skills-zh	880	—	~895	Automated safety check: Pass	MIT	6 days ago
Code Reviewoaslananka/kicad-mcp-pro	122	—	~3.9k	Automated safety check: Pass	MIT	today
Deployment and CI/CD Patternsaffaan-m/ECC	277k	6 repos	~2.8k	Automated safety check: Pass	MIT	today

Similar skills

GitHub Actions Creator
FNOSP/FlyNarwhal
A skill your agent uses when the user wants to create, generate, or set up a GitHub Actions workflow.
509 GitHub starsUsed in 1 repo~2.4k tokens
DevOps & CloudAuto-check passed
GitHub Actions Supply Chain Pinning
asyncapi/generator
A skill your agent uses when editing, adding, or reviewing any file under .github/workflows/, or when a CI step installs a CLI tool (npm i -g, npx, pipx, uses: /setup-).
1.1k GitHub stars~1.9k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Dep Auditor
laolaoshiren/claude-code-skills-zh
审计 Node.js、Python、Go、Rust、JVM、Ruby 项目的依赖漏洞、版本健康度与许可证事实；当用户要求检查 package.json、lockfile、requirements、go.mod、Cargo.toml、pom.xml、Gemfile.lock，或生成不改依赖的中文审计报告时使用
880 GitHub stars~895 tokensUpdated 6 days ago
DevelopmentAuto-check passed
Code Review
oaslananka/kicad-mcp-pro
A skill your agent uses for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro.
122 GitHub stars~3.9k tokensUpdated today
DevelopmentAuto-check passed
Deployment and CI/CD Patterns
affaan-m/ECC
Covers rolling, blue-green and canary deployments, multi-stage Dockerfiles, a GitHub Actions pipeline, health checks and production readiness for web apps.
277k GitHub starsUsed in 6 repos~2.8k tokens
DevOps & CloudAuto-check passed
Deploy To Temps
gotempsh/temps
Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration.
833 GitHub stars~1.3k tokensUpdated today
DevOps & CloudAuto-check: notes

More from kajisho5/ffmpeg-skill

All 14 skills in this repo

Ffmpeg Skill
kajisho5/ffmpeg-skill
Edit video and audio with local FFmpeg from natural-language requests: cut, trim, join, resize/reframe (9:16, 1:1), speed change, captions and subtitles (SRT/ASS, animated, karaoke), logos and text…
1.9k GitHub stars~7.4k tokensUpdated yesterday
Auto-check passed
Reviewing Ffmpeg Skill Changes
kajisho5/ffmpeg-skill
Review a change to the ffmpeg-skill repository for the failures its own contract makes possible — a claim in a result document that is true at one layer and false at the layer a caller reads, a new…
1.9k GitHub stars~2.3k tokensUpdated yesterday
Auto-check passed
Building Python MCP Servers
kajisho5/ffmpeg-skill
Builds robust Python MCP (Model Context Protocol) servers with FastMCP — tool design, error contracts, event-loop-safe blocking work, subprocess/CLI wrapping, single-file vs packaged distribution…
1.9k GitHub stars~3.2k tokensUpdated yesterday
Auto-check passed
Concurrent Branches
kajisho5/ffmpeg-skill
Resolve conflicts and merges when several branches are open against one repo at the same time — the hotspot files every change must touch (registry manifests, a single version field, shared tool…
1.9k GitHub stars~2.8k tokensUpdated yesterday
Auto-check passed
Guarding Destructive Operations
kajisho5/ffmpeg-skill
Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of…
1.9k GitHub stars~2.6k tokensUpdated yesterday
Auto-check passed
Keeping Git Repos Clean
kajisho5/ffmpeg-skill
Prevents, detects, and remediates files that should never be committed — secrets (.env, API tokens, hardcoded credentials) and dev artifacts (build output, scratch databases, editor/OS files).
1.9k GitHub stars~2.1k tokensUpdated yesterday
Auto-check: notes

Works with

Questions about CI Pipeline Synthesizer

What does CI Pipeline Synthesizer do?

Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects. CI Pipeline Synthesizer is an agent skill from kajisho5/ffmpeg-skill. Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.

When should I use CI Pipeline Synthesizer?

CI Pipeline Synthesizer fits situations like: updating CI workflows for npm packages; Python packages; other library projects that need automated build and test pipelines.

How do I install CI Pipeline Synthesizer in Claude Code?

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

How do I install CI Pipeline Synthesizer in Codex?

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

Can I use CI Pipeline Synthesizer 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 kajisho5/ffmpeg-skill --skill ci-pipeline-synthesizer -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-pipeline-synthesizer, .gemini/skills/ci-pipeline-synthesizer, .github/skills/ci-pipeline-synthesizer and .opencode/skills/ci-pipeline-synthesizer in your project.

What does CI Pipeline Synthesizer need to run?

Going by SKILL.md and its folder, CI Pipeline Synthesizer needs the command-line tools its instructions call (npm, python, go and cargo). Our summary lists: Python 3; Node.js.

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

CI Pipeline Synthesizer 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 Pipeline Synthesizer use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Pipeline Synthesizer?

Skills that share tags, products or a category with CI Pipeline Synthesizer: GitHub Actions Creator (FNOSP/FlyNarwhal, 509 stars), GitHub Actions Supply Chain Pinning (asyncapi/generator, 1.1k stars), Dep Auditor (laolaoshiren/claude-code-skills-zh, 880 stars) and Code Review (oaslananka/kicad-mcp-pro, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CI Pipeline Synthesizer?

kajisho5 (a GitHub user) maintains it in kajisho5/ffmpeg-skill, which has 1,909 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 10, 2026.

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

Install CI Pipeline Synthesizer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CI Pipeline Synthesizer

Overview

Workflow

1. Identify Project Type

2. Select Template

3. Customize Configuration

4. Place Workflow File

5. Verify Configuration

Template Features

Customization Examples

Tips

Note for this repository (ffmpeg-skill)

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from kajisho5/ffmpeg-skill

Related

Questions about CI Pipeline Synthesizer