New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Runtime Process Debugging

by caarlos0 in caarlos0/dotfiles

Debug cross-platform process, shell, sandbox, pipe, handle, startup, and shutdown behavior.

MITAuto-check passedDevelopment

Install Runtime Process Debugging

skills CLI
$ npx skills add caarlos0/dotfiles --skill runtime-process-debugging -a claude-code

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

GitHub CLI
$ gh skill install caarlos0/dotfiles runtime-process-debugging --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/caarlos0/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/runtime-process-debugging .claude/skills/runtime-process-debugging && 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
runtime-process-debugging
GitHub stars
220
Token cost
~362 tokens
SKILL.md length
156 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Debug cross-platform process, shell, sandbox, pipe, handle, startup, and shutdown behavior.

  • Works in 6 steps: Map process ownership, parent/child… → Trace macOS, Linux, and Windows… → Instrument the narrow boundary where… → …
  • Lifecycle races
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Platform-specific runtime failures

What it does

Runtime Process Debugging is an agent skill from caarlos0/dotfiles. Debug cross-platform process, shell, sandbox, pipe, handle, startup, and shutdown behavior. Use for hangs, output loss, focus changes, lifecycle races, or platform-specific runtime failures.

Its SKILL.md is about 360 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 Debugging. The licence is MIT.

When your agent uses it

  • Lifecycle races
  • Platform-specific runtime failures

Example prompts

  • “/runtime-process-debugging”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Map process ownership, parent/child relationships, pipe and handle owners,
  2. Trace macOS, Linux, and Windows separately; do not assume their process or
  3. Instrument the narrow boundary where data, focus, or completion is lost.
  4. Reproduce under the relevant scheduler, load, descendant-process, and EOF
  5. Fix the owning runtime layer, preserving intentional bounds such as avoiding
  6. Add a deterministic regression test that controls ordering explicitly; use

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md.

    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 no API keys, tokens, secrets or passwords.

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

Context cost

Runtime Process Debugging loads about 362 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 156 words of instructions outside code blocks.

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

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 caarlos0/dotfiles at commit b144097, republished under its MIT licence (© caarlos0). 156 words, ~362 tokens.

Download SKILL.mdSave it as .claude/skills/runtime-process-debugging/SKILL.md (or your agent's skills folder).
name
runtime-process-debugging
description
Debug cross-platform process, shell, sandbox, pipe, handle, startup, and shutdown behavior. Use for hangs, output loss, focus changes, lifecycle races, or platform-specific runtime failures.

Runtime Process Debugging

Prove where lifecycle behavior diverges before changing it.

  1. Map process ownership, parent/child relationships, pipe and handle owners, cancellation, completion, and teardown.
  2. Trace macOS, Linux, and Windows separately; do not assume their process or pipe semantics match.
  3. Instrument the narrow boundary where data, focus, or completion is lost.
  4. Reproduce under the relevant scheduler, load, descendant-process, and EOF conditions.
  5. Fix the owning runtime layer, preserving intentional bounds such as avoiding hangs from inherited handles.
  6. Add a deterministic regression test that controls ordering explicitly; use writing-tests for synchronization, pipe-drain, EOF, and assertion patterns.

Do not fix races with sleeps, retries, looser assertions, or larger timeouts unless evidence shows elapsed time is the intended contract. Prefer observable state—EOF, process exit, handle ownership, channel closure—over timing.

  • writing-tests: deterministic lifecycle regression tests. When invoked from writing-tests, do not invoke it again.
  • code-review: review a completed lifecycle fix and its regression test.

© caarlos0, MIT. 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 skills/runtime-process-debugging of caarlos0/dotfiles.

Open the folder on GitHubat commit b144097

Compare with similar skills

Runtime Process Debugging 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.

Runtime Process Debugging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Runtime Process Debugging this skillcaarlos0/dotfiles220—~362Automated safety check: PassMIT
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence
Herdr Throwaway Reproductionherdrdev/herdr43k—~2.4kAutomated safety check: PassApache-2.0

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes

  • Debugging Executions

    n8n-io/n8n

    Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed

  • Herdr Throwaway Reproduction

    herdrdev/herdr

    Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.

    43k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Systematic Debugging

    ultralisp/ultralisp

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    258 GitHub starsUsed in 51 repos~2.4k tokens
    DevelopmentAuto-check passed

More from caarlos0/dotfiles

All 20 skills in this repo

  • CLI Design

    caarlos0/dotfiles

    Design and review command-line interfaces for usability, automation, safety, accessibility, and long-term compatibility.

    220 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Dependabot Merge

    caarlos0/dotfiles

    Review and merge open dependency pull requests from Dependabot, Renovate and similar bots across the goreleaser organization and the caarlos0 user.

    220 GitHub stars~5k tokensUpdated today
    Auto-check passed

  • Gh CLI

    caarlos0/dotfiles

    Use GitHub CLI efficiently for pull requests, CI checks, workflow runs, logs, and merge status.

    220 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Tui Design

    caarlos0/dotfiles

    Design terminal user interfaces and interactive CLIs that stay usable, accessible, and scriptable.

    220 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Dashboard

    caarlos0/dotfiles

    Design and review dashboards that are informative, honest, accessible, and visually polished, independent of any tool.

    220 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • Gh Doc Author

    caarlos0/dotfiles

    Author and revise clear GitHub internal documentation, including design docs, proposals, decision records, runbooks, status updates, and handoffs.

    220 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Runtime Process Debugging

What does Runtime Process Debugging do?

Debug cross-platform process, shell, sandbox, pipe, handle, startup, and shutdown behavior. Runtime Process Debugging is an agent skill from caarlos0/dotfiles. Debug cross-platform process, shell, sandbox, pipe, handle, startup, and shutdown behavior.

When should I use Runtime Process Debugging?

Runtime Process Debugging fits situations like: lifecycle races; platform-specific runtime failures.

How do I install Runtime Process Debugging in Claude Code?

Run `npx skills add caarlos0/dotfiles --skill runtime-process-debugging -a claude-code`. Or copy the skill folder (skills/runtime-process-debugging in caarlos0/dotfiles) into .claude/skills/runtime-process-debugging in your project. Claude Code loads it when a task matches its description.

How do I install Runtime Process Debugging in Codex?

Run `npx skills add caarlos0/dotfiles --skill runtime-process-debugging -a codex`. Or copy the skill folder (skills/runtime-process-debugging in caarlos0/dotfiles) into .agents/skills/runtime-process-debugging in your project. Codex loads it when a task matches its description.

Can I use Runtime Process Debugging 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 caarlos0/dotfiles --skill runtime-process-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/runtime-process-debugging, .gemini/skills/runtime-process-debugging, .github/skills/runtime-process-debugging and .opencode/skills/runtime-process-debugging in your project.

What does Runtime Process Debugging need to run?

SKILL.md names no scripts, command-line tools or credentials: Runtime Process Debugging is instructions for the agent only.

Does Runtime Process Debugging 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 Runtime Process Debugging 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 Runtime Process Debugging use?

Runtime Process Debugging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Runtime Process Debugging use?

About 362 tokens (SKILL.md is roughly 1.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 Runtime Process Debugging?

Skills that share tags, products or a category with Runtime Process Debugging: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Runtime Process Debugging?

caarlos0 (a GitHub user) maintains it in caarlos0/dotfiles, which has 220 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.

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