How do I install the CI skill?

Run npx skillmds@latest add tomevault-io/ci-7 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI by tomevault-io — Agent Skill

Name: CI
Author: tomevault-io

File contents

CI Feature

Intent

Provide a practical, repo-embedded CI baseline:

deterministic test/build commands (by convention)
consistent artifacts upload and retention defaults
provider templates for GitHub Actions and GitLab CI

Delivery (release/packaging/deploy automation) is opt-in and is not installed by default.

What gets enabled

When enabled, this feature materializes:

CI metadata directory:
- ci/AGENTS.md
- ci/config.json
- ci/handbook/
Provider workflow file (copy-if-missing):
- GitHub Actions: .github/workflows/ci.yml
- GitLab CI: .gitlab-ci.yml

Provider skills (for workflow customization and troubleshooting):

.ai/skills/features/ci/github-actions-ci/
.ai/skills/features/ci/gitlab-ci/

Controller script (feature-local):

node .ai/skills/features/ci/scripts/ctl-ci.mjs
node .githooks/ci-verify.mjs (shared CI verification entrypoint used by provider templates)

How to enable

In an existing repo

Run:

node .ai/skills/features/ci/scripts/ctl-ci.mjs init --provider github --repo-root .
node .ai/skills/features/ci/scripts/ctl-ci.mjs init --provider gitlab --repo-root .

Delivery explicit enable (opt-in)

Delivery is enabled explicitly (method A) via:

node .ai/skills/features/ci/scripts/ctl-ci.mjs add-delivery --provider github --repo-root .
node .ai/skills/features/ci/scripts/ctl-ci.mjs add-delivery --provider gitlab --repo-root .

Boundaries

Do not store secrets in repo; CI secrets must come from the CI platform secret store.
Keep CI PR/MR gating fast; move flaky/heavy suites to scheduled/manual triggers.
Do not make deploy/release actions automatic unless the repo explicitly opts in and documents credentials, approvals, and rollback.

Verification

node .ai/skills/features/ci/scripts/ctl-ci.mjs --help
node .githooks/ci-verify.mjs

# Dry-run install (no writes)
node .ai/skills/features/ci/scripts/ctl-ci.mjs init --provider github --repo-root . --dry-run
node .ai/skills/features/ci/scripts/ctl-ci.mjs init --provider gitlab --repo-root . --dry-run

# Dry-run delivery opt-in (no writes)
node .ai/skills/features/ci/scripts/ctl-ci.mjs add-delivery --provider github --repo-root . --dry-run
node .ai/skills/features/ci/scripts/ctl-ci.mjs add-delivery --provider gitlab --repo-root . --dry-run

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: ci-7description: Enable and operate the CI feature (GitHub Actions / GitLab CI) with repeatable templates, artifact conventions, and opt-in delivery enablement. Use when this capability is needed.---# CI Feature## IntentProvide a practical, repo-embedded CI baseline:- deterministic test/build commands (by convention)- consistent artifacts upload and retention defaults- provider templates for GitHub Actions and GitLab CIDelivery (release/packaging/deploy automation) is **opt-in** and is not installed by default.## What gets enabledWhen enabled, this feature materializes:- CI metadata directory: - `ci/AGENTS.md` - `ci/config.json` - `ci/handbook/`- Provider workflow file (copy-if-missing): - GitHub Actions: `.github/workflows/ci.yml` - GitLab CI: `.gitlab-ci.yml`Provider skills (for workflow customization and troubleshooting):- `.ai/skills/features/ci/github-actions-ci/`- `.ai/skills/features/ci/gitlab-ci/`Controller script (feature-local):- `node .ai/skills/features/ci/scripts/ctl-ci.mjs`- `node .githooks/ci-verify.mjs` (shared CI verification entrypoint used by provider templates)## How to enable### In an existing repoRun:```bashnode .ai/skills/features/ci/scripts/ctl-ci.mjs init --provider github --repo-root .node .ai/skills/features/ci/scripts/ctl-ci.mjs init --provider gitlab --repo-root .```## Delivery explicit enable (opt-in)Delivery is enabled explicitly (method A) via:```bashnode .ai/skills/features/ci/scripts/ctl-ci.mjs add-delivery --provider github --repo-root .node .ai/skills/features/ci/scripts/ctl-ci.mjs add-delivery --provider gitlab --repo-root .```## Boundaries- Do not store secrets in repo; CI secrets must come from the CI platform secret store.- Keep CI PR/MR gating fast; move flaky/heavy suites to scheduled/manual triggers.- Do not make deploy/release actions automatic unless the repo explicitly opts in and documents credentials, approvals, and rollback.## Verification```bashnode .ai/skills/features/ci/scripts/ctl-ci.mjs --helpnode .githooks/ci-verify.mjs# Dry-run install (no writes)node .ai/skills/features/ci/scripts/ctl-ci.mjs init --provider github --repo-root . --dry-runnode .ai/skills/features/ci/scripts/ctl-ci.mjs init --provider gitlab --repo-root . --dry-run# Dry-run delivery opt-in (no writes)node .ai/skills/features/ci/scripts/ctl-ci.mjs add-delivery --provider github --repo-root . --dry-runnode .ai/skills/features/ci/scripts/ctl-ci.mjs add-delivery --provider gitlab --repo-root . --dry-run```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/willyu1007) — claim your Tome and manage your conversions.

Frequently asked questions

CI