Agent skill

baoyu-electron-extract

Extracts resources and JavaScript from any installed Electron app (`.asar` bundle), restoring original sources from `.js.map` files when available or formatting minified code with Prettier otherwise. Use when user wants to "extract Electron app", "decompile Electron", "get the source code of <app>", "inspect app.asar", "看 Electron 应用源码", "提取 .asar", or asks how a desktop Electron app is built. Skips `node_modules` and supports both macOS and Windows.

JimLiugithub.com/JimLiuGitHub ↗
claude-codecodexships scriptsMIT
Install
npx skills add JimLiu/baoyu-skills --skill baoyu-electron-extract --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 10 KB
Bundled scripts: yes
Version: 1.119.0
Path: skills/baoyu-electron-extract/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 24,562
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Electron App Extract Extracts resources and code from an installed Electron app's `app.asar`. When a `.js.map` is present, restores the original source files from the embedded `sourcesContent`; otherwise formats the minified code with Prettier. Source-map paths are resolved relative to the `.js.map` file first, so bundled paths like `../../src/main.ts` restore to readable paths such as `restored/src/main.ts` instead of hashed placeholders. Always skips `node_modules`. Works on macOS and Windows. ## User Input Tools When this skill prompts the user, follow this tool-selection rule (priority order): 1. **Prefer built-in user-input tools** exposed by the current agent runtime — e.g., `AskUserQuestion`, `request_user_input`, `clarify`, `ask_user`, or any equivalent. 2. **Fallback**: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number/answer for each question. 3. **Batching**: if the tool supports multiple questions per call, combine all applicable questions into a single call; if only single-question, ask them one at a time in priority order. Concrete `AskUserQuestion` references below are examples — substitute the local equival

What's inside
Steps it walks through
  1. User Input Tools
  2. Script Directory
  3. When to use
  4. Workflow
  5. Source-map path restoration
  6. Usage
  7. Options
  8. Output layout
  9. Notes
Ships with 2 files
  • scripts/main.test.ts
  • scripts/main.ts
Commands it runs
Extract by app name (default output: ~/Downloads/Codex-electron-extract/)
Extract by absolute path (works for .app bundles, install dirs, or .asar files)
Custom output
Preview discovery without writing anything
Overwrite an existing output dir
Machine-readable result (one JSON line on stdout)
More from baoyu-skills
All skills →
About this skill
What does the baoyu-electron-extract skill do?

Extracts resources and JavaScript from any installed Electron app (`.asar` bundle), restoring original sources from `.js.map` files when available or formatting minified code with Prettier otherwise. Use when user wants to "extract Electron app", "decompile Electron", "get the source code of <app>", "inspect app.asar", "看 Electron 应用源码", "提取 .asar", or asks how a desktop Electron app is built. Skips `node_modules` and supports both macOS and Windows.

How do I install it?

Run `npx skills add JimLiu/baoyu-skills --skill baoyu-electron-extract --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JimLiu/baoyu-skills, a repository with 24,562 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going