Agent skill

Keen Pbr Symbolize Crash

by maksimkurb in maksimkurb/keen-pbr

Diagnose Keen PBR native crashes from KPBR-CRASH v1 or legacy raw logs.

GPL-3.0Auto-check passedDevelopment

Install Keen Pbr Symbolize Crash

skills CLI
$ npx skills add maksimkurb/keen-pbr --skill keen-pbr-symbolize-crash -a claude-code

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

GitHub CLI
$ gh skill install maksimkurb/keen-pbr keen-pbr-symbolize-crash --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/maksimkurb/keen-pbr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/keen-pbr-symbolize-crash .claude/skills/keen-pbr-symbolize-crash && 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
keen-pbr-symbolize-crash
GitHub stars
141
Token cost
~1.4k tokens
SKILL.md length
608 words
Files
4 (incl. scripts)
Skills in repo
2
Repo updated
First seen
Licence
GPL-3.0

At a glance

Diagnose Keen PBR native crashes from KPBR-CRASH v1 or legacy raw logs.

  • Works in 6 steps: exact commit SHA, commit time, subject,… → temporary worktree and debug artifact… → artifact URL and ELF type/load ranges; → …
  • A user has a Keen PBR SIGSEGV
  • SKILL.md covers Prefer KPBR-CRASH v1, Collect legacy inputs, Run legacy deterministic… and Interpret addresses…, plus 2 more sections
  • Runs Python scripts from its folder; calls python3 and git; reaches raw.githubusercontent.com

What it does

Keen Pbr Symbolize Crash is an agent skill from maksimkurb/keen-pbr. Diagnose Keen PBR native crashes from KPBR-CRASH v1 or legacy raw logs. Use when a user has a Keen PBR SIGSEGV, SIGABRT, SIGBUS, SIGFPE, SIGILL, or terminate report and wants the exact historical commit, temporary worktree, matching OpenWrt or Keenetic GitHub debug artifact, readable stack trace, symbol/function, source file, source line, or an evidence-backed explanation of an unresolved address.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `agents/openai.yaml`, `scripts/analyze_crash.py` and `scripts/test_analyze_crash.py`).

It sits in Development, covering Debugging and Git worktrees. It works with GitHub. The repository describes itself as: keen-pbr is a Policy Based Routing toolkit for Keenetic and OpenWRT routers / Инструменты для выборочной маршрутизации на роутерах Keenetic и OpenWRT. The licence is GPL-3.0.

When your agent uses it

  • A user has a Keen PBR SIGSEGV
  • Terminate report and wants the exact historical commit
  • Temporary worktree
  • Matching OpenWrt

Example prompts

  • “/keen-pbr-symbolize-crash”

Requirements

  • Python 3

Workflow steps

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

  1. exact commit SHA, commit time, subject, and requested branch;
  2. temporary worktree and debug artifact paths;
  3. artifact URL and ELF type/load ranges;
  4. a numbered stack trace plus each raw address, mapping, proven normalization, function, file, and line;
  5. the exact historical source statement and a short causal explanation when resolved;
  6. confidence and missing evidence when unresolved.

What it can do on your machine

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

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • git

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • raw.githubusercontent.com

    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

Keen Pbr Symbolize Crash loads about 1.4k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 608 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from maksimkurb/keen-pbr at commit 4b0a09b, republished under its GPL-3.0 licence (© maksimkurb). 608 words, ~1,377 tokens.

Download SKILL.mdSave it as .claude/skills/keen-pbr-symbolize-crash/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
keen-pbr-symbolize-crash
description
Diagnose Keen PBR native crashes from KPBR-CRASH v1 or legacy raw logs. Use when a user has a Keen PBR SIGSEGV, SIGABRT, SIGBUS, SIGFPE, SIGILL, or terminate report and wants the exact historical commit, temporary worktree, matching OpenWrt or Keenetic GitHub debug artifact, readable stack trace, symbol/function, source file, source line, or an evidence-backed explanation of an unresolved address.

Keen PBR Crash Symbolization

Resolve historical crash addresses without modifying the user's current worktree and without guessing ASLR bases.

Prefer KPBR-CRASH v1

For a complete KPBR-CRASH v1 report, require only the log. Read version, 14-digit build ID, commit, branch, platform, firmware version, architecture, and variant from its meta line. Run:

bash
python3 .agents/skills/keen-pbr-symbolize-crash/scripts/analyze_crash.py \
  --repo . \
  --log-file /path/to/keen-pbr-crash.log

Use explicit CLI metadata only to analyze a legacy report or override a known incorrect field. Never override embedded metadata silently.

Collect legacy inputs

Require or infer these values:

  • version, for example 3.0.7
  • build ID in YYYYmmddHHMMSS; interpret it as the commit time in UTC
  • source branch and repository channel, such as main, stable, or another branch name
  • platform (openwrt or keenetic), firmware version, and package architecture/config
  • package variant: default to full; accept headless
  • the complete crash log, including stack pcs: and memory-map/module lines when available

Treat source branch and artifact channel as the same value unless the user distinguishes them.

Run legacy deterministic preparation

From the repository root, run:

bash
python3 .agents/skills/keen-pbr-symbolize-crash/scripts/analyze_crash.py \
  --repo . \
  --branch main \
  --channel main \
  --version 3.0.7 \
  --build 20260705144235 \
  --platform openwrt \
  --target-version 24.10.6 \
  --arch aarch64_cortex-a53 \
  --variant full \
  --log-file /path/to/crash.log

Add --fetch when the requested branch may be absent or stale. Fetch only that branch. Add --debug-file PATH to reuse an already downloaded artifact. Add --maps-file PATH when a separate /proc/<pid>/maps capture is available. The script leaves its temporary worktree and downloaded artifact in place and prints their paths for inspection and cleanup.

For OpenWrt, use the artifact layout:

text
https://raw.githubusercontent.com/maksimkurb/keen-pbr-repository/main/
repository/<channel>/openwrt-debug/<openwrt>/
keen-pbr_<version>-<build>_openwrt_<openwrt>_<arch>_<variant>.debug

For Keenetic, use repository/<channel>/keenetic-debug/<version>/<package-arch>/keen-pbr_<version>-<build>_keenetic_<config>_<variant>.debug.

Interpret addresses conservatively

  • For ET_EXEC, symbolize a runtime address directly only when it falls inside a PT_LOAD virtual-address range from the debug ELF.
  • For ET_DYN or a relocated module, normalize with a load bias derived from a captured memory map and matching ELF segment. Never subtract a guessed high-address prefix.
  • Treat frame kind=fault, pc, rip, and eip as fault instructions. Treat frame kind=return, link registers, and legacy stack PCs as return addresses; use the architecture-specific call-site adjustment implemented by the analyzer.
  • Trust the embedded commit only after verifying its timestamp matches the build ID and it is reachable from the embedded branch.
  • If the PC maps to a shared library, require that exact library/build's debug ELF plus its memory mapping. The Keen PBR debug file cannot symbolize libc, libstdc++, libcurl, or another DSO.
  • Distinguish function-only from source-line. A symbol table can identify a function while missing DWARF line coverage produces ??:0.
  • Inspect the resolved file in the temporary worktree at the historical commit. Do not cite the same path from the current checkout.

If CodeGraph is unavailable inside the temporary worktree, use the resolved historical file directly. Do not use a current-checkout CodeGraph index as evidence for an old line.

Show full SKILL.md (185 more words)Show less

Recognize incomplete crash-handler output

At commits whose handler calls write_frame_list() after printing registers, a log that stops after registers (...) and then prints plain Segmentation fault did not capture the promised backtrace. Report a likely secondary fault during signal-safe unwinding separately from the original fault. Do not call the secondary fault the original root cause without additional evidence.

Report the result

Include:

  1. exact commit SHA, commit time, subject, and requested branch;
  2. temporary worktree and debug artifact paths;
  3. artifact URL and ELF type/load ranges;
  4. a numbered stack trace plus each raw address, mapping, proven normalization, function, file, and line;
  5. the exact historical source statement and a short causal explanation when resolved;
  6. confidence and missing evidence when unresolved.

Say explicitly when the available data cannot establish a source line. Request one of the following, as applicable: full stack pcs: output, /proc/<pid>/maps, module-plus-offset output, the matching shared-library debug file, or a rebuild with application DWARF line information.

After completing the investigation, remove the temporary worktree with git worktree remove <path> and delete only the script-created temporary directory when cleanup is safe and desired.

© maksimkurb, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in .agents/skills/keen-pbr-symbolize-crash of maksimkurb/keen-pbr.

  • SKILL.md
  • agents/openai.yaml
  • scripts/analyze_crash.py
  • scripts/test_analyze_crash.py

Open the folder on GitHubat commit 4b0a09b

Compare with similar skills

Keen Pbr Symbolize Crash 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.

Keen Pbr Symbolize Crash compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Keen Pbr Symbolize Crash this skillmaksimkurb/keen-pbr141—~1.4kAutomated safety check: PassGPL-3.0
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
OpenCLI Adapter Autofixjackwener/OpenCLI30k1 repos~3.2kAutomated safety check: PassApache-2.0
Issue Fixmono/SkiaSharp5.6k—~5.1kAutomated safety check: PassMIT
React Router Bug Fix Workflowremix-run/react-router57k—~1.3kAutomated safety check: PassMIT

Similar skills

  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • OpenCLI Adapter Autofix

    jackwener/OpenCLI

    Repairs a broken OpenCLI site adapter after a command fails: collects a trace, patches only the adapter, retries, and files an upstream GitHub issue once fixed.

    30k GitHub starsUsed in 1 repo~3.2k tokens
    DevelopmentAuto-check passed
  • Issue Fix

    mono/SkiaSharp

    Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.

    5.6k GitHub stars~5.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • React Router Bug Fix Workflow

    remix-run/react-router

    Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.

    57k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Codewhale Landing Workflow

    codewhale-hq/Codewhale

    Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.

    41k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from maksimkurb/keen-pbr

  • Keen Pbr Release Post

    maksimkurb/keen-pbr

    Draft keen-pbr release posts for GitHub and Telegram from git history.

    141 GitHub stars~844 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Keen Pbr Symbolize Crash

What does Keen Pbr Symbolize Crash do?

Diagnose Keen PBR native crashes from KPBR-CRASH v1 or legacy raw logs. Keen Pbr Symbolize Crash is an agent skill from maksimkurb/keen-pbr. Diagnose Keen PBR native crashes from KPBR-CRASH v1 or legacy raw logs.

When should I use Keen Pbr Symbolize Crash?

Keen Pbr Symbolize Crash fits situations like: A user has a Keen PBR SIGSEGV; terminate report and wants the exact historical commit; temporary worktree; matching OpenWrt.

How do I install Keen Pbr Symbolize Crash in Claude Code?

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

How do I install Keen Pbr Symbolize Crash in Codex?

Run `npx skills add maksimkurb/keen-pbr --skill keen-pbr-symbolize-crash -a codex`. Or copy the skill folder (.agents/skills/keen-pbr-symbolize-crash in maksimkurb/keen-pbr) into .agents/skills/keen-pbr-symbolize-crash in your project. Codex loads it when a task matches its description.

Can I use Keen Pbr Symbolize Crash 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 maksimkurb/keen-pbr --skill keen-pbr-symbolize-crash -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/keen-pbr-symbolize-crash, .gemini/skills/keen-pbr-symbolize-crash, .github/skills/keen-pbr-symbolize-crash and .opencode/skills/keen-pbr-symbolize-crash in your project.

What does Keen Pbr Symbolize Crash need to run?

Going by SKILL.md and its folder, Keen Pbr Symbolize Crash needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and git). Our summary lists: Python 3.

Does Keen Pbr Symbolize Crash access the network?

SKILL.md names 1 domain. In commands or code: raw.githubusercontent.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Keen Pbr Symbolize Crash 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Keen Pbr Symbolize Crash use?

Keen Pbr Symbolize Crash is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Keen Pbr Symbolize Crash use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Keen Pbr Symbolize Crash?

Skills that share tags, products or a category with Keen Pbr Symbolize Crash: Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), OpenCLI Adapter Autofix (jackwener/OpenCLI, 30k stars) and Issue Fix (mono/SkiaSharp, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Keen Pbr Symbolize Crash?

maksimkurb (a GitHub user) maintains it in maksimkurb/keen-pbr, which has 141 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

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