Agent skill

Setting Up CI

by spencerpauly in spencerpauly/awesome-cursor-skills

Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps.

CC0-1.0Auto-check passedDevOps & Cloud

Install Setting Up CI

skills CLI

$ npx skills add spencerpauly/awesome-cursor-skills --skill setting-up-ci -a claude-code

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

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills setting-up-ci --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/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/setting-up-ci .claude/skills/setting-up-ci && 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 "setting-up-ci" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/setting-up-ci into .claude/skills/setting-up-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-ci", 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/spencerpauly/awesome-cursor-skills/tree/main/resources/setting-up-ci

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 spencerpauly/awesome-cursor-skills --skill setting-up-ci -a codex

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

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills setting-up-ci --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/setting-up-ci .agents/skills/setting-up-ci && 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 "setting-up-ci" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/setting-up-ci into .agents/skills/setting-up-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-ci", 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 spencerpauly/awesome-cursor-skills --skill setting-up-ci -a cursor

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

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills setting-up-ci --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/setting-up-ci .cursor/skills/setting-up-ci && 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 "setting-up-ci" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/setting-up-ci into .cursor/skills/setting-up-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-ci", 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/spencerpauly/awesome-cursor-skills.git --path resources/setting-up-ci

--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 spencerpauly/awesome-cursor-skills --skill setting-up-ci -a gemini-cli

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

GitHub CLI

$ gh skill install spencerpauly/awesome-cursor-skills setting-up-ci --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/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/setting-up-ci .gemini/skills/setting-up-ci && 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 "setting-up-ci" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/setting-up-ci into .gemini/skills/setting-up-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-ci", 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 spencerpauly/awesome-cursor-skills setting-up-ci

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 spencerpauly/awesome-cursor-skills --skill setting-up-ci -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/setting-up-ci .github/skills/setting-up-ci && 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 "setting-up-ci" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/setting-up-ci into .github/skills/setting-up-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-ci", 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 spencerpauly/awesome-cursor-skills --skill setting-up-ci -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 spencerpauly/awesome-cursor-skills setting-up-ci --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/setting-up-ci .opencode/skills/setting-up-ci && 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 "setting-up-ci" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/setting-up-ci into .opencode/skills/setting-up-ci/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-ci", 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: setting-up-ci
GitHub stars: 844
Token cost: ~582 tokens
SKILL.md length: 178 words
Files: 1
Skills in repo: 60
Repo updated: Aug 2, 2026
First seen: Oct 7, 2026
Licence: CC0-1.0

At a glance

Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps.

Works in 7 steps: Detect the project structure — check for… → Create .github/workflows/ci.yml → Add type-checking — if typecheck script… → …
Tasks that involve CI/CD
SKILL.md covers Steps and Notes
Calls npm; reaches github.com; needs VERCEL_TOKEN

What it does

Setting Up CI is an agent skill from spencerpauly/awesome-cursor-skills. Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps.

Its SKILL.md is about 580 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 CI/CD, Type safety and Linting and formatting. It works with GitHub Actions and npm. The repository describes itself as: A curated list of awesome skills for Cursor. The licence is CC0-1.0.

When your agent uses it

Tasks that involve CI/CD
Tasks that involve Type safety
Tasks that involve Linting and formatting

Example prompts

“/setting-up-ci”

Requirements

Node.js
A credential in VERCEL_TOKEN

Workflow steps

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

Detect the project structure — check for package.json (Node.js), requirements.txt / pyproject.toml (Python), go.mod (Go), or monorepo…
Create .github/workflows/ci.yml
Add type-checking — if typecheck script doesn't exist in package.json, add "typecheck": "tsc --noEmit".
Add caching — the actions/setup-node cache option handles node_modules. For monorepos with Turborepo, add remote caching or actions/cache…
Add matrix testing (optional) — if the user needs to test across Node versions or OS
Add deployment step (optional) — if requested, add a deploy job that runs only on main pushes, gated by the build job succeeding
Add status badge — add the workflow status badge to the project README

What it can do on your machine

Read from SKILL.md and the folder at commit 99cd265. 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
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 these keys or tokens, usually read from environment variables:
- VERCEL_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Setting Up CI loads about 582 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 178 words of instructions outside code blocks.

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

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 spencerpauly/awesome-cursor-skills at commit 99cd265, republished under its CC0-1.0 licence (© spencerpauly). 178 words, ~582 tokens.

Download SKILL.mdSave it as .claude/skills/setting-up-ci/SKILL.md (or your agent's skills folder).

name: setting-up-ci
description: Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps.

Setup CI (GitHub Actions)

Use this skill when the user asks to set up CI, continuous integration, a build pipeline, or GitHub Actions.

Steps

Detect the project structure — check for package.json (Node.js), requirements.txt / pyproject.toml (Python), go.mod (Go), or monorepo tools like Turborepo.

Create .github/workflows/ci.yml

For a Node.js project:

yaml

name: CI

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

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - run: npm ci
      - run: npm run lint
      - run: npm run typecheck
      - run: npm test
      - run: npm run build

Add type-checking — if typecheck script doesn't exist in package.json, add "typecheck": "tsc --noEmit".
Add caching — the actions/setup-node cache option handles node_modules. For monorepos with Turborepo, add remote caching or actions/cache for .turbo.
Add matrix testing (optional) — if the user needs to test across Node versions or OS:
yaml
```
strategy:
  matrix:
    node-version: [18, 20, 22]
```

Add deployment step (optional) — if requested, add a deploy job that runs only on main pushes, gated by the build job succeeding:

yaml

deploy:
  needs: build
  if: github.ref == 'refs/heads/main'
  runs-on: ubuntu-latest
  steps:
    - uses: actions/checkout@v4
    - run: npm ci && npm run build
    - run: npx vercel deploy --prod --token=${{ secrets.VERCEL_TOKEN }}

Add status badge — add the workflow status badge to the project README:
markdown
```
![CI](https://github.com/OWNER/REPO/actions/workflows/ci.yml/badge.svg)
```

Notes

Keep CI fast — run lint and typecheck in parallel using separate jobs if the pipeline is slow.
Use npm ci (not npm install) for deterministic installs.
Store secrets (API keys, deploy tokens) in GitHub repository settings, never in the workflow file.

Files

Just SKILL.md in resources/setting-up-ci of spencerpauly/awesome-cursor-skills.

Open the folder on GitHubat commit 99cd265

Compare with similar skills

Setting Up CI 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.

Setting Up CI compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Setting Up CI this skillspencerpauly/awesome-cursor-skills	844	—	~582	Automated safety check: Pass	CC0-1.0	2 mo ago
Manor CI Triagemanor-os/manor-ai	162	—	~533	Automated safety check: Pass	Custom licence	1 mo ago
Configuration GeneratorArabelaTso/Skills-4-SE	253	—	~2.8k	Automated safety check: Notes	Apache-2.0	1 mo ago
Update Dependenciesalorence/django-modern-rpc	111	—	~1.3k	Automated safety check: Pass	MIT	2 days ago
Python Pypi Package Buildergithub/awesome-copilot	40k	1 repos	~4.6k	Automated safety check: Pass	MIT	yesterday
Obsidian Plugin Releasecrafter-station/skills	112	—	~1.8k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Manor CI Triage
manor-os/manor-ai
A skill your agent uses when Manor GitHub Actions, .github/workflows/ci.yml, OSS smoke/regression jobs, web source smoke, frontend build, lint, or public CI failure logs need diagnosis or repair.
162 GitHub stars~533 tokensUpdated 1 mo ago
DevOps & CloudAuto-check passed
Configuration Generator
ArabelaTso/Skills-4-SE
Generate configuration files for applications, services, and infrastructure.
253 GitHub stars~2.8k tokensUpdated 1 mo ago
DevOps & CloudAuto-check: notes
Update Dependencies
alorence/django-modern-rpc
Routine update of all project dependencies — uv itself, uv.lock (all groups), tool versions pinned in GitHub workflows and .pre-commit-config.yaml (uv, ruff, mypy...), and SHA-pinned GitHub Actions.
111 GitHub stars~1.3k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Python Pypi Package Builder
github/awesome-copilot
Official
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
40k GitHub starsUsed in 1 repo~4.6k tokens
DevelopmentAuto-check passed
Obsidian Plugin Release
crafter-station/skills
Release a new version of an Obsidian community plugin without forgetting steps.
112 GitHub stars~1.8k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Repo Hygiene Scan and Fix
QwenLM/qwen-code
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

Questions about Setting Up CI

What does Setting Up CI do?

Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps. Setting Up CI is an agent skill from spencerpauly/awesome-cursor-skills. Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps.

When should I use Setting Up CI?

Setting Up CI fits situations like: tasks that involve CI/CD; tasks that involve Type safety; tasks that involve Linting and formatting.

How do I install Setting Up CI in Claude Code?

Run `npx skills add spencerpauly/awesome-cursor-skills --skill setting-up-ci -a claude-code`. Or copy the skill folder (resources/setting-up-ci in spencerpauly/awesome-cursor-skills) into .claude/skills/setting-up-ci in your project. Claude Code loads it when a task matches its description.

How do I install Setting Up CI in Codex?

Run `npx skills add spencerpauly/awesome-cursor-skills --skill setting-up-ci -a codex`. Or copy the skill folder (resources/setting-up-ci in spencerpauly/awesome-cursor-skills) into .agents/skills/setting-up-ci in your project. Codex loads it when a task matches its description.

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

What does Setting Up CI need to run?

Going by SKILL.md and its folder, Setting Up CI needs the command-line tools its instructions call (npm) and credentials named VERCEL_TOKEN. Our summary lists: Node.js; A credential in VERCEL_TOKEN.

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

Setting Up CI is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Setting Up CI use?

About 582 tokens (SKILL.md is roughly 2.3k 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 Setting Up CI?

Skills that share tags, products or a category with Setting Up CI: Manor CI Triage (manor-os/manor-ai, 162 stars), Configuration Generator (ArabelaTso/Skills-4-SE, 253 stars), Update Dependencies (alorence/django-modern-rpc, 111 stars) and Python Pypi Package Builder (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Setting Up CI?

spencerpauly (a GitHub user) maintains it in spencerpauly/awesome-cursor-skills, which has 844 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on August 2, 2026.

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

Setting Up CI

Install Setting Up CI

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

Setup CI (GitHub Actions)

Steps

Notes

Files

Compare with similar skills

Similar skills

Manor CI Triage

Configuration Generator

Update Dependencies

Python Pypi Package Builder

Obsidian Plugin Release

Repo Hygiene Scan and Fix

More from spencerpauly/awesome-cursor-skills

Generating Images

Babysitting PR

Best Of N Solving

Grinding Until Pass

Parallel CI Triage

Parallel Exploring

Questions about Setting Up CI

Install Setting Up CI

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

Setup CI (GitHub Actions)

Steps

Notes

Files

Compare with similar skills

Similar skills

More from spencerpauly/awesome-cursor-skills

Related

Questions about Setting Up CI