Decompress Binary Skill for Claude

Extract the inner ELF from a ClickHouse self-extracting `clickhouse` binary, including when its architecture differs from the host (e.g. to load an aarch64 CI core dump on an x86 workstation). Use when gdb/lldb needs real symbols from a downloaded CI/release binary, or when self-extraction by running the binary is not possible because of an architecture mismatch.

2k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

49040

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/ClickHouse/ClickHouse --skill decompress-binary

What comes with it

2 875 bytes besides the instruction

extract_self_extracting.py

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

5 sections, as written by the author

Decompress a ClickHouse Binary (Cross-Architecture)

ClickHouse release and CI clickhouse binaries are self-extracting: a small

decompressor stub, followed by the zstd-compressed real ELF and a trailer.

The normal way to decompress is to run the binary once: it extracts the inner

ELF in place and re-execs it. That works on the binary's own architecture,

and also on a foreign architecture **if qemu user-mode emulation for it is

installed** (e.g. qemu-aarch64 to run an aarch64 binary on x86). When qemu for

the target is not available, you cannot run the binary at all and must extract the

payload offline.

This skill extracts the inner ELF without executing anything, on any host.

When to use

You downloaded a CI/release clickhouse and gdb/lldb shows no real symbols

(it only sees the decompressor stub's tiny symbol table).

The binary's architecture differs from the host (cannot self-extract by running).
You need the inner ELF to load a core dump (see ci/decrypt-cores.md for the

matching core-dump decryption procedure).

Format

See utils/self-extracting-executable/types.h:

[ decompressor ELF ]
[ compressed file blobs ]
[ FileData[] ]                 # one per packed file, each followed by its name
[ MetaData (16 bytes) @ EOF ]

MetaData { uint64 number_of_files; uint64 start_of_files_data; }
FileData { uint64 start, end, name_length, uncompressed_size, umask; bool exec; }

MetaData sits at the very end of the file. start_of_files_data points at the

FileData array; each 48-byte FileData is followed by the file name. The

compressed bytes for a file are input[start:end] (zstd, possibly multi-frame).

The packed clickhouse ELF is the entry with exec = true.

Steps

Download the binary from the build job for the exact commit, for example:

   curl -s "https://clickhouse-builds.s3.amazonaws.com/PRs/<pr>/<sha>/build_<arch>_<sanitizer>/clickhouse" -o clickhouse.sfx

Find the precise URL in the build job's artifact_report_build_*.json, or via

.claude/tools/fetch_ci_report.js "<pr-url>". Download in the foreground (a

killed/resumed curl can append garbage past EOF and break the trailer; verify

the size matches Content-Length).

Extract the inner ELF:

   python3 .claude/skills/decompress-binary/extract_self_extracting.py clickhouse.sfx clickhouse.elf

Verify it is the right build and has symbols:

   file clickhouse.elf                                          # ELF ..., not stripped, with debug_info
   llvm-objdump -s -j .note.gnu.build-id clickhouse.elf | tail  # must match the core's build id

The build id must equal the one in the crash report / core. A mismatched

binary yields unusable backtraces.

Use it with the core dump:

   gdb clickhouse.elf core.<pid>      # or: lldb clickhouse.elf -c core.<pid>

gdb and lldb read foreign-architecture cores fine for backtraces and memory

inspection (you are not executing the target).

Notes

A truncated or corrupted download is the most common failure: if the script

reports an implausible number_of_files, re-download cleanly and check the size.

The inner ELF is large (several GB for sanitizer builds, unstripped). Make sure

there is enough disk.

Shortcut when you can run the binary: if the host matches the binary's

architecture, or qemu user-mode emulation for it is installed, just run

./clickhouse once to self-extract in place. This skill is for the case where

neither is possible.

Other skills for the same job

different authors, same section of the catalogue

Postgresql Code Review

by christophacham

×1

PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS).

Use when writing a commit message or opening a PR in the go-redis repo — covers the Conventional-Commit format, the repo's scope vocabulary (pool, conn, sentinel, command, …), breaking-change syntax, and the rule that NO AI-attribution trailer is added.

Review a GitHub issue or pull request URL as a redis-py maintainer, with a staged assessment of whether the claim is real, practically important, already solvable with supported functionality, correctly scoped, better served by another design, and worth maintainer and contributor effort. Use when assessing issue validity or severity, deciding whether an issue should be prioritized or closed, determining whether a requested feature represents an unmet need rather than a discoverability or usage gap, judging whether a PR is worth bringing to mergeable quality, comparing open PRs or alternative designs, separating code quality from repository readiness, or drafting a concise maintainer assessment. When closure, additional evidence, or code changes should be requested, also produce a polite, concise, complete, copy-paste-ready maintainer comment.

Produce PR-ready output for redis-py — a one-line commit message and a copy-pasteable Markdown PR description (Change summary + Test coverage, 5–6 paragraphs) covering all staged changes plus the commits already on the current branch. Trigger whenever the user's message mentions any of these keywords or phrases: "PR", "pr", "PR description", "PR draft", "pull request", "the PR block", "commit msg", "commit message", or otherwise asks for a commit message or PR write-up for their local changes.

Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.

3k tokens

Wp Performance Review

by elvismdev

WordPress performance code review and optimization analysis. Use when reviewing WordPress PHP code for performance issues, auditing themes/plugins for scalability, optimizing WP_Query, analyzing caching strategies, checking code before launch, or detecting anti-patterns, or when user mentions "performance review", "optimization audit", "slow WordPress", "slow queries", "high-traffic", "scale WordPress", "code review", "timeout", "500 error", "out of memory", or "site won't load". Detects anti-patterns in database queries, hooks, object caching, AJAX, and template loading.

21k tokens

How to use it

Copy the folder

Take clickhouse/decompress-binary from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.