Skip to content
TrustedSkillsbeta
Back to all skills

Starwards Ci Debugging

Listed
starwards·vlatest·testing

Automatically identifies and suggests fixes for CI/CD pipeline failures using Starwards' advanced AI analysis.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add starwards/starwards --skill starwards-ci-debugging -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

starwards

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: mcr.microsoft.com.

    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.

    Hosts contacted

    mcr.microsoft.comundeclared

    What it found

    • .agents/skills/starwards-ci-debugging/SKILL.md:214contacts mcr.microsoft.com
      curl -s https://mcr.microsoft.com/v2/playwright/tags/list | jq -r '.tags[] | select(startswith("v1.5"))' | sort -V | tail -10
    • .claude/skills/starwards-ci-debugging/SKILL.md:214contacts mcr.microsoft.com
      curl -s https://mcr.microsoft.com/v2/playwright/tags/list | jq -r '.tags[] | select(startswith("v1.5"))' | sort -V | tail -10

  • 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 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 starwards/starwards at f7dc1575ae.

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

Commit
f7dc1575ae
Manifest
.agents/skills/starwards-ci-debugging/SKILL.md
Scanned
2 files, 938 lines
Copies in repo
2 — all of them scanned
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

This skill allows AI agents to debug continuous integration (CI) pipelines. It can analyze CI logs, identify error patterns, and suggest potential fixes for build failures. The tool helps streamline troubleshooting workflows and reduce time spent diagnosing pipeline issues.

When to use it

  • Build failures: Use when a CI/CD pipeline consistently fails, and manual log analysis is proving difficult or time-consuming.
  • Recurring errors: Employ this skill when specific error messages or patterns appear repeatedly in build logs.
  • Complex pipelines: Leverage the debugging capabilities for intricate CI pipelines with multiple stages and dependencies.
  • Performance bottlenecks: Identify slowdowns within a CI pipeline by analyzing execution times of different steps.

Key capabilities

  • CI log analysis
  • Error pattern identification
  • Suggestion of potential fixes
  • Pipeline performance analysis

Example prompts

  • "Analyze the latest build logs for repository X and identify the root cause of the failure."
  • "What are the most common error patterns in our CI pipeline?"
  • "Suggest a fix for this specific error message found in the build log: [error message]."

Tips & gotchas

The skill's effectiveness depends on the quality and completeness of the CI logs. Ensure that your CI system is configured to provide detailed, verbose logging for accurate debugging.