New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

CI Diagnostics

by timeplus-io in timeplus-io/proton

Diagnose Proton CI failures and performance comparison results from GitHub checks and uploaded reports.

Apache-2.0Auto-check passedTesting & QA

Install CI Diagnostics

skills CLI
$ npx skills add timeplus-io/proton --skill ci-diagnostics -a claude-code

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

GitHub CLI
$ gh skill install timeplus-io/proton ci-diagnostics --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/timeplus-io/proton.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ci-diagnostics .claude/skills/ci-diagnostics && 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/

Facts

Skill name
ci-diagnostics
GitHub stars
2.3k
Token cost
~685 tokens
SKILL.md length
260 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Diagnose Proton CI failures and performance comparison results from GitHub checks and uploaded reports.

  • Works in 5 steps: List failing contexts from gh pr checks… → Open each target_url report first. → If the report is sparse, inspect the… → …
  • CI checks are mentioned
  • SKILL.md covers Inputs, First step: collect check status, Proton report layout and Failure triage workflow, plus 2 more sections
  • Calls gh

What it does

CI Diagnostics is an agent skill from timeplus-io/proton. Diagnose Proton CI failures and performance comparison results from GitHub checks and uploaded reports. Make sure to use this skill whenever CI checks are mentioned, a PR has red or failing checks, the user pastes a CI URL, or asks about test failures in the pipeline, even if they just ask 'why is CI failing'.

Its SKILL.md is about 690 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 Testing & QA, covering Failing and flaky tests. It works with GitHub. The repository describes itself as: The Fastest Unified Streaming SQL Engine in a Single C++ Binary. ⚡ Millisecond latency. 100+ GB/s throughput. Continuously compute real-time context from streams, logs, metrics… The licence is Apache-2.0.

When your agent uses it

  • CI checks are mentioned
  • The user pastes a CI URL
  • Asks about test failures in the pipeline
  • Even if they just ask why is CI failing

Example prompts

  • “why is CI failing”
  • “/ci-diagnostics”

Workflow steps

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

  1. List failing contexts from gh pr checks or commit statuses.
  2. Open each target_url report first.
  3. If the report is sparse, inspect the linked raw log.
  4. For test reports, summarize
  5. Map failures back to touched areas in the diff.

What it can do on your machine

Read from SKILL.md and the folder at commit 1c47e60. 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:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, 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 no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CI Diagnostics loads about 685 tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 260 words of instructions outside code blocks.

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

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 timeplus-io/proton at commit 1c47e60, republished under its Apache-2.0 licence (© timeplus-io). 260 words, ~685 tokens.

Download SKILL.mdSave it as .claude/skills/ci-diagnostics/SKILL.md (or your agent's skills folder).
name
ci-diagnostics
description
Diagnose Proton CI failures and performance comparison results from GitHub checks and uploaded reports. Make sure to use this skill whenever CI checks are mentioned, a PR has red or failing checks, the user pastes a CI URL, or asks about test failures in the pipeline, even if they just ask 'why is CI failing'.

CI Diagnostics

Inputs

  • PR number or URL
  • optional check name substring
  • optional direct report URL

First step: collect check status

For a PR:

bash
gh pr view "$PR" --json title,body,url
gh pr checks "$PR"
REPO=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
SHA=$(gh pr view "$PR" --json commits --jq '.commits[-1].oid')
gh api "repos/$REPO/commits/$SHA/status"

Use the commit status payload to find:

  • failing or pending contexts
  • target_url links for uploaded HTML reports, raw logs, or performance artifacts

Proton report layout

CI uploads reports under:

text
<pr-number>/<commit-sha>/<normalized-check-name>...

The normalization logic is defined in:

Normalize a check name with lowercase and replacements for spaces, (, ), and ,.

Failure triage workflow

  1. List failing contexts from gh pr checks or commit statuses.
  2. Open each target_url report first.
  3. If the report is sparse, inspect the linked raw log.
  4. For test reports, summarize:
    • failing test names
    • first common error signature
    • whether the failure looks deterministic, flaky, infra, or environment-specific
  5. Map failures back to touched areas in the diff.

Performance comparison workflow

Performance comparison artifacts upload:

  • report.html
  • all-queries.html
  • all-query-metrics.tsv
  • queries.rep
  • images/flamegraphs

If you have a report.html URL, inspect sibling artifacts by replacing the filename in the same prefix.

When reviewing perf results:

  • start from the summary in report.html
  • inspect all-query-metrics.tsv for the biggest client_time regressions
  • distinguish broad regressions from a few outlier queries
  • correlate with touched execution paths, joins, windows, aggregations, or storage reads

Output expectations

Always report:

  1. failing checks
  2. best report/log URL for each failing check
  3. likely failure class: code bug, flaky test, infra, dependency, or timeout/resource limit
  4. smallest next debugging action

For performance changes also report:

  1. whether the regression is broad or narrow
  2. the most affected workload family
  3. whether more local benchmarking is needed before code changes

© timeplus-io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/ci-diagnostics of timeplus-io/proton.

Open the folder on GitHubat commit 1c47e60

Compare with similar skills

CI Diagnostics 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 Diagnostics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
CI Diagnostics this skilltimeplus-io/proton2.3k—~685Automated safety check: PassApache-2.0
Triage CI Flakepayloadcms/payload45k—~4.4kAutomated safety check: PassMIT
GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb6.7k—~4.4kAutomated safety check: PassApache-2.0
Fix Issueremix-run/remix33k—~1.8kAutomated safety check: PassMIT
Issue To Regression Testbrunosabot/streamline-card269—~529Automated safety check: PassMIT
Detect Flaky Testsagent-substrate/substrate4.5k—~3kAutomated safety check: PassApache-2.0

Similar skills

  • Triage CI Flake

    payloadcms/payload

    A skill your agent uses when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests

    45k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed

  • GreptimeDB Fuzz CI Failure Investigation

    GreptimeTeam/greptimedb

    Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.

    6.7k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Fix Issue

    remix-run/remix

    Fix a reported issue in Remix from a GitHub issue. An agent skill from remix-run/remix.

    33k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

  • Issue To Regression Test

    brunosabot/streamline-card

    A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.

    269 GitHub stars~529 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

  • Detect Flaky Tests

    agent-substrate/substrate

    Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM…

    4.5k GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed

  • Fix Random CI Test Failure

    dotnet/macios

    Official

    Investigate and fix flaky/random CI test failures in dotnet/macios.

    2.9k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

More from timeplus-io/proton

  • Alloc Profile

    timeplus-io/proton

    Analyze jemalloc or async-profiler allocation profiles in collapsed stack format.

    2.3k GitHub stars~489 tokensUpdated 17 days ago
    Auto-check passed

  • Create Worktree

    timeplus-io/proton

    Create a Proton git worktree with local submodule reuse. An agent skill from timeplus-io/proton.

    2.3k GitHub stars~812 tokensUpdated 17 days ago
    Auto-check passed

  • Build And Verify

    timeplus-io/proton

    Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures.

    2.3k GitHub stars~1.3k tokensUpdated 17 days ago
    Auto-check passed

  • SQL Usage

    timeplus-io/proton

    Timeplus streaming SQL covering stream types, EMIT policies, window functions, JOINs, materialized views, external streams, and UDFs.

    2.3k GitHub stars~1.7k tokensUpdated 17 days ago
    Auto-check passed

  • Cpp Coding

    timeplus-io/proton

    Write or review Timeplus/Proton C++20 code covering naming conventions, Proton fences, clang-format, IProcessor patterns, and checkpointing.

    2.3k GitHub stars~582 tokensUpdated 17 days ago
    Auto-check passed

  • Review

    timeplus-io/proton

    Review a Proton pull request or diff for correctness, streaming semantics, checkpointing, compatibility, and performance.

    2.3k GitHub stars~1.1k tokensUpdated 17 days ago
    Auto-check passed

Works with

Categories

Questions about CI Diagnostics

What does CI Diagnostics do?

Diagnose Proton CI failures and performance comparison results from GitHub checks and uploaded reports. CI Diagnostics is an agent skill from timeplus-io/proton. Diagnose Proton CI failures and performance comparison results from GitHub checks and uploaded reports.

When should I use CI Diagnostics?

CI Diagnostics fits situations like: CI checks are mentioned; the user pastes a CI URL; asks about test failures in the pipeline; even if they just ask why is CI failing.

How do I install CI Diagnostics in Claude Code?

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

How do I install CI Diagnostics in Codex?

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

Can I use CI Diagnostics 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 timeplus-io/proton --skill ci-diagnostics -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-diagnostics, .gemini/skills/ci-diagnostics, .github/skills/ci-diagnostics and .opencode/skills/ci-diagnostics in your project.

What does CI Diagnostics need to run?

Going by SKILL.md and its folder, CI Diagnostics needs the command-line tools its instructions call (gh).

Does CI Diagnostics access the network?

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

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

CI Diagnostics is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CI Diagnostics use?

About 685 tokens (SKILL.md is roughly 2.7k 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 Diagnostics?

Skills that share tags, products or a category with CI Diagnostics: Triage CI Flake (payloadcms/payload, 45k stars), GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars), Fix Issue (remix-run/remix, 33k stars) and Issue To Regression Test (brunosabot/streamline-card, 269 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CI Diagnostics?

timeplus-io (a GitHub organization) maintains it in timeplus-io/proton, which has 2,265 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 20, 2026.

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