Agent skill

CI Validation Gates

by FritzAndFriends in FritzAndFriends/SharpSite

Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22

Install CI Validation Gates

skills CLI

$ npx skills add FritzAndFriends/SharpSite --skill ci-validation-gates -a claude-code

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

GitHub CLI

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

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 FritzAndFriends/SharpSite --skill ci-validation-gates -a codex

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

GitHub CLI

$ gh skill install FritzAndFriends/SharpSite ci-validation-gates --agent codex

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

Manual copy

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

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

GitHub CLI

$ gh skill install FritzAndFriends/SharpSite ci-validation-gates --agent cursor

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

Manual copy

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

--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 FritzAndFriends/SharpSite --skill ci-validation-gates -a gemini-cli

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

GitHub CLI

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

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 FritzAndFriends/SharpSite --skill ci-validation-gates -a github-copilot

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

Manual copy

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

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

Manual copy

$ git clone --depth 1 https://github.com/FritzAndFriends/SharpSite.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.copilot/skills/ci-validation-gates .opencode/skills/ci-validation-gates && 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-validation-gates" agent skill from https://github.com/FritzAndFriends/SharpSite/tree/main/.copilot/skills/ci-validation-gates into .opencode/skills/ci-validation-gates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-validation-gates", 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-validation-gates
GitHub stars: 145
Used in: 1 other repo
Token cost: ~911 tokens
SKILL.md length: 329 words
Files: 1
Skills in repo: 18
Repo updated: Apr 30, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22

Tasks that involve Error handling
SKILL.md covers Context, Patterns, Known Failure Modes (v0.8.22… and Anti-Patterns
Calls npm and npx; needs NPM_TOKEN
Tasks that involve CI/CD

What it does

CI Validation Gates is an agent skill from FritzAndFriends/SharpSite. Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22

Its SKILL.md is about 910 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 Error handling and CI/CD. It works with npm. The repository describes itself as: A basic CMS built with .NET 9 and Blazor. The licence is MIT.

When your agent uses it

Tasks that involve Error handling
Tasks that involve CI/CD

Example prompts

“/ci-validation-gates”

Requirements

Node.js
A credential in NPM_TOKEN

What it can do on your machine

Read from SKILL.md and the folder at commit c35e5e0. 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
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and npx, 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 these keys or tokens, usually read from environment variables:
- NPM_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CI Validation Gates loads about 911 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 329 words of instructions outside code blocks.

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

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 FritzAndFriends/SharpSite at commit c35e5e0, republished under its MIT licence (© FritzAndFriends). 329 words, ~911 tokens.

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

name: ci-validation-gates
description: Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22
domain: ci-cd
confidence: high
source: extracted from Drucker and Trejo charters — earned knowledge from v0.8.22 release incident

Context

CI workflows must be defensive. These patterns were learned from the v0.8.22 release disaster where invalid semver, wrong token types, missing retry logic, and draft releases caused a multi-hour outage. Both Drucker (CI/CD) and Trejo (Release Manager) carried this knowledge in their charters — now centralized here.

Patterns

Semver Validation Gate

Every publish workflow MUST validate version format before npm publish. 4-part versions (e.g., 0.8.21.4) are NOT valid semver — npm mangles them.

yaml

- name: Validate semver
  run: |
    VERSION="${{ github.event.release.tag_name }}"
    VERSION="${VERSION#v}"
    if ! npx semver "$VERSION" > /dev/null 2>&1; then
      echo "❌ Invalid semver: $VERSION"
      echo "Only 3-part versions (X.Y.Z) or prerelease (X.Y.Z-tag.N) are valid."
      exit 1
    fi
    echo "✅ Valid semver: $VERSION"

NPM Token Type Verification

NPM_TOKEN MUST be an Automation token, not a User token with 2FA:

User tokens require OTP — CI can't provide it → EOTP error
Create Automation tokens at npmjs.com → Settings → Access Tokens → Automation
Verify before first publish in any workflow

Retry Logic for npm Registry Propagation

npm registry uses eventual consistency. After npm publish succeeds, the package may not be immediately queryable.

Propagation: typically 5-30s, up to 2min in rare cases
All verify steps: 5 attempts, 15-second intervals
Log each attempt: "Attempt 1/5: Checking package..."
Exit loop on success, fail after max attempts

yaml

- name: Verify package (with retry)
  run: |
    MAX_ATTEMPTS=5
    WAIT_SECONDS=15
    for attempt in $(seq 1 $MAX_ATTEMPTS); do
      echo "Attempt $attempt/$MAX_ATTEMPTS: Checking $PACKAGE@$VERSION..."
      if npm view "$PACKAGE@$VERSION" version > /dev/null 2>&1; then
        echo "✅ Package verified"
        exit 0
      fi
      [ $attempt -lt $MAX_ATTEMPTS ] && sleep $WAIT_SECONDS
    done
    echo "❌ Failed to verify after $MAX_ATTEMPTS attempts"
    exit 1

Draft Release Detection

Draft releases don't emit release: published event. Workflows MUST:

Trigger on release: published (NOT created)
If using workflow_dispatch: verify release is published via GitHub API before proceeding

Build Script Protection

Set SKIP_BUILD_BUMP=1 (or $env:SKIP_BUILD_BUMP = "1" on Windows) before ANY release build. bump-build.mjs is for dev builds ONLY — it silently mutates versions.

Known Failure Modes (v0.8.22 Incident)

#	What Happened	Root Cause	Prevention
1	4-part version published, npm mangled it	No semver validation gate	`npx semver` check before every publish
2	CI failed 5+ times with EOTP	User token with 2FA	Automation token only
3	Verify returned false 404	No retry logic for propagation	5 attempts, 15s intervals
4	Workflow never triggered	Draft release doesn't emit event	Never create draft releases
5	Version mutated during release	bump-build.mjs ran in release	SKIP_BUILD_BUMP=1

Anti-Patterns

❌ Publishing without semver validation gate
❌ Single-shot verification without retry
❌ Hard-coded secrets in workflows
❌ Silent CI failures — every error needs actionable output with remediation
❌ Assuming npm publish is instantly queryable

Files

Just SKILL.md in .copilot/skills/ci-validation-gates of FritzAndFriends/SharpSite.

Open the folder on GitHubat commit c35e5e0

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 FritzAndFriends/SharpSite, which our catalogue first saw on October 7, 2026.

olivomarco/github-copilot-token-optimization.copilot/skills/ci-validation-gates

Compare with similar skills

CI Validation Gates 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 Validation Gates compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
CI Validation Gates this skillFritzAndFriends/SharpSite	145	1 repos	~911	Automated safety check: Pass	MIT	5 mo ago
CI Validation Gatesbradygaster/squad	3.3k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Repo Hygiene Scan and FixQwenLM/qwen-code	28k	—	~1.7k	Automated safety check: Pass	Apache-2.0	today
Check Deps SyncHyk260/PureChat	546	—	~594	Automated safety check: Pass	MIT	23 days ago
npm Release Via GitHub Actionsjmfederico/pi-web	869	—	~2.9k	Automated safety check: Pass	MIT	today
Publishcode-yeongyu/oh-my-openagent	70k	—	~5.5k	Automated safety check: Warn	Custom licence	today

Similar skills

CI Validation Gates
bradygaster/squad
Defensive CI/CD patterns: semver validation, token checks, retry logic, and draft detection
3.3k GitHub stars~1.1k tokensUpdated yesterday
DevOps & CloudAuto-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
Check Deps Sync
Hyk260/PureChat
Check if package.json files are in sync with pnpm-lock.yaml.
546 GitHub stars~594 tokensUpdated 23 days ago
DevOps & CloudAuto-check passed
npm Release Via GitHub Actions
jmfederico/pi-web
A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…
869 GitHub stars~2.9k tokensUpdated today
DevOps & CloudAuto-check passed
Publish
code-yeongyu/oh-my-openagent
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts.
70k GitHub stars~5.5k tokensUpdated today
DevOps & CloudAuto-check: warnings
Release And CI
eser/stack
Releases and CI for eserstack: the shared version of all packages, the release command, the tag-driven build.yml run, JSR and npm publishing, changelog and breaking changes, release recovery, GitHub…
128 GitHub stars~665 tokensUpdated 6 days ago
DevOps & CloudAuto-check passed

Questions about CI Validation Gates

What does CI Validation Gates do?

Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22. CI Validation Gates is an agent skill from FritzAndFriends/SharpSite.

When should I use CI Validation Gates?

CI Validation Gates fits situations like: tasks that involve Error handling; tasks that involve CI/CD.

How do I install CI Validation Gates in Claude Code?

Run `npx skills add FritzAndFriends/SharpSite --skill ci-validation-gates -a claude-code`. Or copy the skill folder (.copilot/skills/ci-validation-gates in FritzAndFriends/SharpSite) into .claude/skills/ci-validation-gates in your project. Claude Code loads it when a task matches its description.

How do I install CI Validation Gates in Codex?

Run `npx skills add FritzAndFriends/SharpSite --skill ci-validation-gates -a codex`. Or copy the skill folder (.copilot/skills/ci-validation-gates in FritzAndFriends/SharpSite) into .agents/skills/ci-validation-gates in your project. Codex loads it when a task matches its description.

Can I use CI Validation Gates 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 FritzAndFriends/SharpSite --skill ci-validation-gates -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-validation-gates, .gemini/skills/ci-validation-gates, .github/skills/ci-validation-gates and .opencode/skills/ci-validation-gates in your project.

What does CI Validation Gates need to run?

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

Does CI Validation Gates access the network?

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

Is CI Validation Gates 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 Validation Gates use?

CI Validation Gates 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 Validation Gates use?

About 911 tokens (SKILL.md is roughly 3.6k 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 Validation Gates?

Skills that share tags, products or a category with CI Validation Gates: CI Validation Gates (bradygaster/squad, 3.3k stars), Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars), Check Deps Sync (Hyk260/PureChat, 546 stars) and npm Release Via GitHub Actions (jmfederico/pi-web, 869 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CI Validation Gates?

FritzAndFriends (a GitHub organization) maintains it in FritzAndFriends/SharpSite, which has 145 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on April 30, 2026.

Source: FritzAndFriends/SharpSite 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 Validation Gates

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Context

Patterns

Semver Validation Gate

NPM Token Type Verification

Retry Logic for npm Registry Propagation

Draft Release Detection

Build Script Protection

Known Failure Modes (v0.8.22 Incident)

Anti-Patterns

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from FritzAndFriends/SharpSite

Related

Questions about CI Validation Gates