Agent skill

Troubleshooting

by projectbluefin in projectbluefin/finpilot

Symptom to cause to fix for build, CI, and runtime failures, plus the pre-commit checklist.

Apache-2.0Auto-check passedDevelopment

Install Troubleshooting

skills CLI
$ npx skills add projectbluefin/finpilot --skill troubleshooting -a claude-code

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

GitHub CLI
$ gh skill install projectbluefin/finpilot troubleshooting --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/projectbluefin/finpilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/troubleshooting .claude/skills/troubleshooting && 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
troubleshooting
GitHub stars
126
Token cost
~605 tokens
SKILL.md length
309 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

Symptom to cause to fix for build, CI, and runtime failures, plus the pre-commit checklist.

  • Something is broken
  • SKILL.md covers Before a pull request, Build, CI and Runtime, plus 1 more section
  • Calls just; needs RENOVATE_TOKEN
  • Before opening a pull request

What it does

Troubleshooting is an agent skill from projectbluefin/finpilot. Symptom to cause to fix for build, CI, and runtime failures, plus the pre-commit checklist. Use when something is broken or before opening a pull request.

Its SKILL.md is about 610 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 Development, covering Pull requests. The repository describes itself as: Build your own custom Bluefin. The licence is Apache-2.0.

When your agent uses it

  • Something is broken
  • Before opening a pull request

Example prompts

  • “/troubleshooting”

Requirements

  • A credential in RENOVATE_TOKEN

What it can do on your machine

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

    • just

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

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • RENOVATE_TOKEN

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

Context cost

Troubleshooting loads about 605 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 309 words of instructions outside code blocks.

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

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 projectbluefin/finpilot at commit 8e0eb5d, republished under its Apache-2.0 licence (© projectbluefin). 309 words, ~605 tokens.

Download SKILL.mdSave it as .claude/skills/troubleshooting/SKILL.md (or your agent's skills folder).
name
troubleshooting
description
Symptom to cause to fix for build, CI, and runtime failures, plus the pre-commit checklist. Use when something is broken or before opening a pull request.

Troubleshooting

Before a pull request

  • Conventional Commit message.
  • just lint — shellcheck on every tracked script.
  • just check — Justfile syntax.
  • just test-unit — the suite.
  • just validate-brewfiles / just validate-flatpaks if those changed.
  • just build if the image changed.

CI runs the same checks; running them locally only makes the pull request quiet.

Build

SymptomCauseFix
bootc container lint fails on a nonempty /runa script wrote to /run into an image layerremove it in 90-cleanup.sh; that phase deliberately does not mount /run as tmpfs
a third-party repository is live in the final imagea script enabled it and did not disable ituse copr_install_isolated, or disable it explicitly
the package layer rebuilds on every overlay editpackages drifted into the overlay phasekeep packages in 20-packages-and-services.sh
hadolint flags the Containerfilea rule in .github/hadolint.yamlfix it, or add a suppression with a reason

CI

SymptomCauseFix
validate never runsbranch protection names a check no workflow producesthe context must be exactly validate
Renovate logs a skip and opens nothingRENOVATE_TOKEN is not setexpected; set the secret to turn Renovate on
Renovate fails on Validate RENOVATE_TOKENthe token is expired or lacks the workflow scoperecreate the token
the promotion PR never opensstable does not existcreate the branch
the promotion PR will not mergestable requires an approvalset required approvals to 0
a Renovate PR waits foreverauto-merge is offenable it in Settings

Runtime

The two most common first-boot surprises — no Flatpaks, and no brew — are in the README's Troubleshooting section.

SymptomCauseFix
ujust shows no custom commands60-custom.just was not written or importedcheck that 10-overlay.sh copied the recipes

Capturing what you learned

When a fix here was non-obvious, put it in the skill that owns the area, in the same pull request. That is the only home for durable learning.

© projectbluefin, 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 .agents/skills/troubleshooting of projectbluefin/finpilot.

Open the folder on GitHubat commit 8e0eb5d

Compare with similar skills

Troubleshooting 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.

Troubleshooting compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Troubleshooting this skillprojectbluefin/finpilot126—~605Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from projectbluefin/finpilot

  • Customize

    projectbluefin/finpilot

    Decide where a package, app, or command belongs — dnf5 at build time, Homebrew, Flatpak, or ujust — and how each is validated.

    126 GitHub stars~625 tokensUpdated today
    Auto-check passed
  • Onboarding

    projectbluefin/finpilot

    Bootstrap a new image from this template: rename the project, enable Actions and Renovate, protect the branch, and reach a first green build.

    126 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • CI

    projectbluefin/finpilot

    GitHub Actions, Renovate, the two-branch release model, signing, and promotion.

    126 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Overview

    projectbluefin/finpilot

    Architecture, repository layout, and file map for this template.

    126 GitHub stars~740 tokensUpdated today
    Auto-check passed

Categories

Questions about Troubleshooting

What does Troubleshooting do?

Symptom to cause to fix for build, CI, and runtime failures, plus the pre-commit checklist. Troubleshooting is an agent skill from projectbluefin/finpilot. Symptom to cause to fix for build, CI, and runtime failures, plus the pre-commit checklist.

When should I use Troubleshooting?

Troubleshooting fits situations like: something is broken; before opening a pull request.

How do I install Troubleshooting in Claude Code?

Run `npx skills add projectbluefin/finpilot --skill troubleshooting -a claude-code`. Or copy the skill folder (.agents/skills/troubleshooting in projectbluefin/finpilot) into .claude/skills/troubleshooting in your project. Claude Code loads it when a task matches its description.

How do I install Troubleshooting in Codex?

Run `npx skills add projectbluefin/finpilot --skill troubleshooting -a codex`. Or copy the skill folder (.agents/skills/troubleshooting in projectbluefin/finpilot) into .agents/skills/troubleshooting in your project. Codex loads it when a task matches its description.

Can I use Troubleshooting 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 projectbluefin/finpilot --skill troubleshooting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/troubleshooting, .gemini/skills/troubleshooting, .github/skills/troubleshooting and .opencode/skills/troubleshooting in your project.

What does Troubleshooting need to run?

Going by SKILL.md and its folder, Troubleshooting needs the command-line tools its instructions call (just) and credentials named RENOVATE_TOKEN. Our summary lists: A credential in RENOVATE_TOKEN.

Does Troubleshooting access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Troubleshooting 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 Troubleshooting use?

Troubleshooting 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 Troubleshooting use?

About 605 tokens (SKILL.md is roughly 2.4k 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 Troubleshooting?

Skills that share tags, products or a category with Troubleshooting: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Troubleshooting?

projectbluefin (a GitHub organization) maintains it in projectbluefin/finpilot, which has 126 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

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