solo: Skill for Claude Code

.claude/skills/solo-log-ci-failure/SKILL.md

solo-log-ci-failure is a skill for Claude Code from hiero-ledger/solo. It costs 75 tokens per session (1,859 once invoked), scanned A, original, Apache-2.0.

A procedure for creating a fully documented GitHub bug issue when a Solo project's CI workflow fails. CI, or continuous integration, automatically runs checks on code changes; the procedure preserves logs and diagnostic files in a secret GitHub gist.

In plain words
What is it for?
Use it with GitHub Actions workflow URLs to download failure details, extract the error context, preserve the files, and create an issue in hiero-ledger/solo.
Why use it?
GitHub Actions logs and artifacts can expire, so it keeps the failure evidence available and links it to a tagged priority bug.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is hiero-ledger/solo's own configuration. It tells Claude Code how to work on solo 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 solo configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hiero-ledger/solo. 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/hiero-ledger/solo/main/.claude/skills/solo-log-ci-failure/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/hiero-ledger/solo

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 solo-log-ci-failure

README.md
[![agentmods](https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-log-ci-failure/github.svg)](https://agentmods.dev/skills/hiero-ledger/solo/solo-log-ci-failure)
Your own site
<a href="https://agentmods.dev/skills/hiero-ledger/solo/solo-log-ci-failure"><img src="https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-log-ci-failure/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 solo-log-ci-failure

Your own site · 80×15
<a href="https://agentmods.dev/skills/hiero-ledger/solo/solo-log-ci-failure"><img src="https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-log-ci-failure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,859 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00075 $0.01859
Opus 5 $0.00037 $0.00929
Sonnet 5 $0.00015 $0.00372
Haiku 4.5 $0.00007 $0.00186

Measured 10d ago against content hash 590e432895c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

solo-log-ci-failure 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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (log-ci-failure.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/solo-log-ci-failure/SKILL.md · 150 lines

How it starts

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

Solo Log CI Failure

Given one or more GitHub Actions workflow URLs (run, run+job, or suite/logs), create fully-configured P0 bug issues in hiero-ledger/solo with permanently preserved log files and complete project metadata — in exactly one Bash call per URL, run in parallel when multiple URLs are provided.

All executable logic lives in a single reviewable shell script in this skill directory:

Script Purpose
log-ci-failure.sh Fetch metadata, download job log + artifact, extract errors, create gist + issue

GitHub artifacts auto-purge after 7 days. The script downloads key log files and uploads them as a secret gist (never expires, not publicly listed). The issue body links directly to the gist.

Prerequisite: the gh token must have the gist scope (for log preservation) and the project scope (for the board additions in step 7). Verify with gh auth status. If missing, run: gh auth refresh -h github.com -s gist -s project


Reducing permission prompts

The script is the single point of review. Once you have read and approved its content, you can allowlist it by exact path so Claude can run it without per-call prompts:

/update-config add to project allowlist:
  Bash(bash *solo-log-ci-failure/log-ci-failure.sh *)

This allowlists only that specific named script — not gh broadly — so the scope of trust matches exactly what was reviewed.


Supported URL formats

Format Example
Run + job https://github.com/hiero-ledger/solo/actions/runs/30336845771/job/90203561367
Run only https://github.com/hiero-ledger/solo/actions/runs/30336845771
Suite/logs https://github.com/hiero-ledger/solo/suites/82215623504/logs?attempt=1

Usage (one Bash call per URL)

When multiple URLs are given, launch all calls in parallel in a single message.

bash ~/.claude/skills/solo-log-ci-failure/log-ci-failure.sh "<workflow-url>" [<parent-issue-id>]

Read the full file on GitHub · 150 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 150 lines · 75 tokens per session scan A 590e432895c2

Subscribe to this mod's changes

solo-log-ci-failure is a skill published in the GitHub repository hiero-ledger/solo (43 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 1,859 once invoked, about $0.0004 per session on Opus 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-09-01.

Related

Other skills, from other repositories

agent-merge-conflict-arbiter

Neutral arbiter for merge conflicts between two agents.

NousResearch/hermes-agent · 19 tokens

git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

wshobson/agents · 54 tokens

conventional-commit

Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.

JanDeDobbeleer/oh-my-posh · 47 tokens

oh-my-posh

Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.

JanDeDobbeleer/oh-my-posh · 47 tokens

comet-github-issue-fix

A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.

rpamis/comet · 71 tokens

triaging-merge-queue-failures

Decision procedure for a PR that failed or was removed from the Trunk merge queue: classify the kick (superseded by a newer commit, not mergeable, a gate that failed on a cancelled run, real failure, one-off flake, or repo-wide flaky/infra issue) and take the matching action (wait, hold and fix, requeue once, or…

PostHog/posthog-foss · 180 tokens