AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Circleci Status

skill-flurdy-agent-skills-circleci-status · by flurdy

Check CircleCI build status and failed job logs for the current GitHub repository. Use when asked whether CircleCI is green, failing, pending, or when needing CircleCI job logs.

No reviews yet
0 installs
35 views
0.0% view→install

Install

$ agentstack add skill-flurdy-agent-skills-circleci-status

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-flurdy-agent-skills-circleci-status)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Circleci Status? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

CircleCI Status

Check the latest CircleCI pipeline/workflow status for the current GitHub repository, with optional failed job logs.

Authentication

  • Basic GitHub commit status/check-run summaries use gh when authenticated.
  • CircleCI pipeline/workflow/job details require CIRCLECI_TOKEN in the local environment.
  • CircleCI project slug is derived from origin: gh/{owner}/{repo}.

Set up once locally if detailed CircleCI API access is needed:

export CIRCLECI_TOKEN=...

or configure the CircleCI CLI/token storage separately and export the token before invoking the skill.

Usage

/circleci-status          # Summarise latest status for current branch/HEAD
/circleci-status logs     # Show latest failed job logs for current branch
/circleci-status main     # Summarise latest CircleCI pipeline for branch main
/circleci-status logs main

Instructions

Always run the helper scripts fresh; never reuse prior status output.

Status mode

For no argument, or an argument other than logs, run:

~/.claude/skills/circleci-status/scripts/status.sh {optional-branch-or-ref}

Render:

## CircleCI status — {repo} `{branch}`

- GitHub commit status: {state}
- GitHub check runs: {counts by conclusion/status}
- CircleCI: {workflow statuses or token-missing note}

If ---CIRCLECI-STATUS--- is NO_TOKEN, say:

> CircleCI API details unavailable: set CIRCLECI_TOKEN locally. GitHub commit/check status above may still show CircleCI's reported state.

If GitHub status includes CircleCI contexts with target_url, include links for failing/pending contexts.

Logs mode

For logs as the first argument, run:

~/.claude/skills/circleci-status/scripts/logs.sh {optional-branch}

Render:

## CircleCI logs — {repo} `{branch}`

| Job | Status | Number |
|-----|--------|--------|

Then include the tail or relevant failure portion of ---LOGS---. Keep output concise; prefer the final failing command/error block over dumping thousands of lines. If no token is configured, explain that logs require CIRCLECI_TOKEN.

Failure handling

  • NO_GIT_REPO: say this must be run inside a GitHub-backed git repo.
  • NO_TOKEN: show GitHub status if available, and explain how to set CIRCLECI_TOKEN.
  • CircleCI API errors: report the error and fall back to GitHub commit/check status when present.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.