flisk: Skill for Claude Code

.claude/skills/flisk-troubleshoot/SKILL.md

flisk-troubleshoot is a skill for Claude Code from flisk-sh/flisk. It costs 139 tokens per session (1,699 once invoked), scanned A, original, MIT.

A diagnostic procedure for Flisk stacks that fail to start or never become healthy.

In plain words
What is it for?
Use it to investigate failed images, database crash loops, missing files, unhealthy services, Docker problems, and startup errors.
Why use it?
It turns service, Tilt, Docker, and machine reports into an evidence-based diagnosis instead of relying on guesses or stopping unrelated containers.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

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

Reuse

Borrowing it

Nothing to install: this file belongs to flisk-sh/flisk. 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/flisk-sh/flisk/main/.claude/skills/flisk-troubleshoot/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/flisk-sh/flisk

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 flisk-troubleshoot

README.md
[![agentmods](https://agentmods.dev/badge/skills/flisk-sh/flisk/flisk-troubleshoot/github.svg)](https://agentmods.dev/skills/flisk-sh/flisk/flisk-troubleshoot)
Your own site
<a href="https://agentmods.dev/skills/flisk-sh/flisk/flisk-troubleshoot"><img src="https://agentmods.dev/badge/skills/flisk-sh/flisk/flisk-troubleshoot/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 flisk-troubleshoot

Your own site · 80×15
<a href="https://agentmods.dev/skills/flisk-sh/flisk/flisk-troubleshoot"><img src="https://agentmods.dev/badge/skills/flisk-sh/flisk/flisk-troubleshoot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,699 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.
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.00139 $0.01699
Opus 5.5 $0.00056 $0.00680
Sonnet 5.5 $0.00028 $0.00340
Haiku 4.5 $0.00014 $0.00170

Measured 5d ago against content hash 110e232b67d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flisk-troubleshoot 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 5d ago.

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/flisk-troubleshoot/SKILL.md · 102 lines

How it starts

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

Flisk troubleshooting

Work from evidence: what the CLI, Tilt and Docker report. Say what you measured, what you estimated and what you do not know, in that order. The full message-by-message guide is docs/troubleshooting.md.

First minute: triage

flisk status --unhealthy --json      # which services are failing or still starting
flisk logs --unhealthy --tail 100    # their recent logs
flisk doctor --json                  # machine and project checks
time docker ps -q | wc -l            # how many containers, and how slow Docker is
  • docker ps taking more than about 5 s means the machine is overloaded, not broken. flisk doctor and flisk down give up after their own 10 s Docker check in that state. Check load (uptime) and free memory before blaming Docker, Tilt or the code.
  • A running tilt up recreates any container you docker stop within seconds. Run flisk down (it stops this project's Tilt too) instead of stopping containers one by one.
  • Several Flisk projects can share one Docker daemon. Containers are named <project>-<stack>-autogenerated-<service>-1; filter by project before stopping anything.
  • Before anything that runs longer than about 5 minutes or starts dozens of containers, tell the user and give an estimate. Start only the stack you need: flisk up <stack>, or flisk up <stack> --only <service>.

Symptoms, causes and fixes

"Docker daemon is not responding (docker ps hung for 10s)"

Cause: usually overload, as above. Fix: flisk down, wait for the load to drop, then start one stack instead of all of them.

flisk up keeps waiting, or init-networks is red

Cause: Docker has no free address pools (all predefined address pools have been fully subnetted). Every Flisk project creates several networks and flisk down keeps them. Fix: flisk doctor --fix --scope=machine removes unused networks of every Flisk project. For throwaway projects, stop them with flisk down --prune-networks.

Read the full file on GitHub · 102 lines

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. 5d ago First seen · 102 lines · 139 tokens per session scan A 110e232b67d7

Subscribe to this mod's changes

flisk-troubleshoot is a skill published in the GitHub repository flisk-sh/flisk (54 stars, last pushed yesterday), licensed MIT. It adds 139 tokens to every session and 1,699 once invoked, about $0.0006 per session on Opus 5.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-11-15.

Related

flisk-troubleshoot compared with skills from other repositories

flisk-troubleshoot next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
flisk-troubleshootflisk-sh/fliskSkill54yesterdayMITA139Claude Code
docker-debugkurtosis-tech/kurtosisSkill559todayApache-2.0A45Claude Code, Codex
k8s-debug-podskurtosis-tech/kurtosisSkill559todayApache-2.0A62Claude Code, Codex
docker-docspledgeandgrow/pledge-skillsSkill114mo agoMITA93Claude Code, Codex
docker-managementfurkangonel/cowranglerSkill12mo agoMITC16Claude Code, Codex
gke-kueue-troubleshootinggoogle/skillsSkill24ktodayApache-2.0A253Claude Code, Codex
smoke-testgarrytan/gbrainSkill33ktodayMITA79Claude Code