Skip to content
TrustedSkillsbeta
Back to all skills

Analyze Ci

Checked
eyh0602·vlatest·devops

Examines CI/CD pipeline logs to identify errors, bottlenecks, and potential deployment risks quickly.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it using-skillshub, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add eyh0602/skillshub --skill using-skillshub -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

eyh0602

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned eyh0602/skillshub at 02bc988c53.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
02bc988c53
Manifest
skills/using-skillshub/SKILL.md
Scanned
3 files, 382 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The analyze-ci skill allows you to parse and summarize Continuous Integration (CI) logs. It can extract key information like test results, build status, and error messages from CI output. This enables quick identification of failures and insights into the health of a software project's integration process.

When to use it

  • Troubleshooting Build Failures: Quickly understand why a recent CI run failed by summarizing the logs.
  • Monitoring Project Health: Get an overview of test pass rates and build stability over time.
  • Identifying Regression Issues: Pinpoint changes that introduced new errors or broken tests in your codebase.
  • Automated Reporting: Generate concise reports on CI performance for stakeholders.

Key capabilities

  • Parses CI logs
  • Summarizes test results
  • Extracts build status information
  • Identifies error messages

Example prompts

  • "Analyze the attached GitLab CI log and tell me if any tests failed."
  • "Can you summarize the key errors from this Jenkins build?"
  • "What's the overall pass rate for the tests in this CircleCI run?"

Tips & gotchas

The skill requires access to the CI logs, which may necessitate providing credentials or API keys depending on your CI system. Ensure the provided log format is compatible with the skill’s parsing capabilities.