stoa: Skill for Claude Code

.claude/skills/ci-debug/SKILL.md

ci-debug is a skill for Claude Code from stoa-platform/stoa. It costs 28 tokens per session (881 once invoked), scanned A, original, Apache-2.0.

A helper for finding why GitHub Actions, GitHub's automated build and test service, has reported a failed workflow.

In plain words
What is it for?
Use it to inspect a pull request or workflow run, identify likely root causes, and suggest fixes for common Python and Node.js CI errors.
Why use it?
It brings together failed checks and error logs so you do not have to search through CI output manually.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter; positional $N argument.

This is stoa-platform/stoa's own configuration. It tells Claude Code how to work on stoa itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything stoa configures →

Reuse

Borrowing it

Nothing to install: this file belongs to stoa-platform/stoa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/stoa-platform/stoa/main/.claude/skills/ci-debug/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/stoa-platform/stoa

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ci-debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/stoa-platform/stoa/ci-debug/github.svg)](https://agentmods.dev/skills/stoa-platform/stoa/ci-debug)
Your own site
<a href="https://agentmods.dev/skills/stoa-platform/stoa/ci-debug"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/ci-debug/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ci-debug

Your own site · 80×15
<a href="https://agentmods.dev/skills/stoa-platform/stoa/ci-debug"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/ci-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 881 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00881
Opus 5.5 $0.00011 $0.00352
Sonnet 5.5 $0.00006 $0.00176
Haiku 4.5 $0.00003 $0.00088

Measured 2mo ago against content hash 76496348541e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ci-debug scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/ci-debug/SKILL.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI Debug — Analyse des echecs CI

Contexte dynamique

  • Checks PR en cours: !gh pr checks 2>/dev/null | head -20
  • Workflows recents: !gh run list --limit 5 --json name,status,conclusion,headBranch --template '{{range .}}{{.name}} | {{.status}} | {{.conclusion}} | {{.headBranch}}{{"\n"}}{{end}}' 2>/dev/null

Instructions

Analyser l'echec CI pour: $ARGUMENTS

Step 1: Identifier le workflow en echec

Si c'est un numero de PR:

gh pr checks $0
gh run list --branch $(gh pr view $0 --json headRefName -q .headRefName) --limit 3

Si c'est une URL de workflow run:

gh run view $0 --log-failed

Step 2: Extraire les logs d'erreur

gh run view <run-id> --log-failed 2>&1 | head -100

Chercher les patterns:

  • error, Error, ERROR
  • FAIL, FAILED
  • exit code 1, exit code 2
  • denied, forbidden, unauthorized

Step 3: Diagnostiquer

Causes frequentes dans STOA CI:

Pipeline Erreur frequente Cause Fix
Python CI I001 import order isort non respecte ruff check --fix
Python CI mypy type error Type hints manquants Ajouter les annotations
Node CI vitest fail Mock MSW manquant Ajouter handler MSW
Node CI eslint warnings Max warnings depassé (0 pour UI, 20 pour portal) Fixer les warnings
Docker buildx fail Cache layer miss ou multi-arch Verifier --platform linux/amd64,linux/arm64
Helm helm lint fail Values manquantes, indentation Verifier values.yaml
Security dependency-review GitHub Advanced Security non active Connu, non-bloquant
K8s deploy kubectl apply fail Selector immutable, Kyverno block Voir .claude/docs/k8s-deploy.md
K8s deploy rollout timeout maxSurge/maxUnavailable deadlock maxUnavailable: 1, maxSurge: 0

Step 4: Proposer le fix

Pour chaque erreur identifiee:

  1. Fichier exact a modifier (chemin complet)
  2. Diff propose (old → new)
  3. Commande de verification locale
  4. Impact sur les autres workflows

Read the full file on GitHub · 101 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 101 lines · 28 tokens per session scan A 76496348541e

Subscribe to this mod's changes

ci-debug is a skill published in the GitHub repository stoa-platform/stoa (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 881 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

ci-debug compared with skills from other repositories

ci-debug next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ci-debugstoa-platform/stoaSkill9yesterdayApache-2.0A28Claude Code
meta-long-running-build-watchdogopensquilla/opensquillaSkill7.1k6d agoApache-2.0A131Claude Code
ci-debugyonatangross/orchestkitSkill299yesterdayMITA55Claude Code
lyrikgebruder/wirkenSkill1942d agoMITA15Claude Code
librariangebruder/wirkenSkill1942d agoMITA34Claude Code
notesgebruder/wirkenSkill1942d agoMITA10Claude Code
tdx-assetsgebruder/wirkenSkill1942d agoMITA58Claude Code