/SKILL.md
Extract or stage Claude Code source from the installed CLI so you can inspect internals and reverse engineer features. Use when the user wants to understand how Claude Code works, trace a behavior, or find where a feature is implemented.
npx skillsauth add gswangg/inspect-claude-source inspect-claude-sourceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Extract or stage Claude Code's JavaScript source from the installed CLI. Works for both Bun-compiled builds and npm-installed cli.js bundles.
VERSION="$(python3 ~/.claude/skills/inspect-claude-source/extract.py --print-version)"
To see which Claude install is being inspected:
python3 ~/.claude/skills/inspect-claude-source/extract.py --print-binary
Check if /tmp/claude-source/$VERSION/src/entrypoints/cli.js exists. If not, run the extraction script bundled with this skill:
python3 ~/.claude/skills/inspect-claude-source/extract.py --text-only
The script auto-detects the install type and:
claude from PATH by default (or uses --binary PATH)cli.js, stages it directly to /tmp/claude-source/<version>/src/entrypoints/cli.js--pretty/tmp/claude-source/<version>/Options:
--text-only - skip binary modules (.node, .wasm) when extracting Bun builds--pretty - use prettier via bunx for full prettification (slower)--binary PATH - inspect a different Claude executable or cli.js--output-dir DIR - change output directory (default: /tmp/claude-source)--print-version - print the resolved Claude Code version and exit--print-binary - print the resolved Claude Code path and exitThe main source file is:
/tmp/claude-source/<version>/src/entrypoints/cli.js
If the user provided a search term ($ARGUMENTS), search for it:
grep -n "$ARGUMENTS" /tmp/claude-source/$VERSION/src/entrypoints/cli.js | head -50
For broader exploration, use Grep/Glob/Read against /tmp/claude-source/<version>/.
assistant, result, system, tool_use, stream, permission.tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.