[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EBQ2KT03G9C3H8VQTMBQ0R":3,"skill-same:01M7EBQ2KT03G9C3H8VQTMBQ0R":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":52},"01M7EBQ2KT03G9C3H8VQTMBQ0R","baoyu-electron-extract",null,"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 \u003Capp>\", \"inspect app.asar\", \"看 Electron 应用源码\", \"提取 .asar\", or asks how a desktop Electron app is built. Skips `node_modules` and supports both macOS and Windows.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fbaoyu-electron-extract\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: baoyu-electron-extract\ndescription: 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 \u003Capp>\", \"inspect app.asar\", \"看 Electron 应用源码\", \"提取 .asar\", or asks how a desktop Electron app is built. Skips `node_modules` and supports both macOS and Windows.\nversion: 1.119.0\nmetadata:\n  openclaw:\n    homepage: https:\u002F\u002Fgithub.com\u002FJimLiu\u002Fbaoyu-skills#baoyu-electron-extract\n    requires:\n      anyBins:\n        - bun\n        - npx\n---\n\n# Electron App Extract\n\nExtracts 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 `..\u002F..\u002Fsrc\u002Fmain.ts` restore to readable paths such as `restored\u002Fsrc\u002Fmain.ts` instead of hashed placeholders. Always skips `node_modules`. Works on macOS and Windows.\n\n## User Input Tools\n\nWhen this skill prompts the user, follow this tool-selection rule (priority order):\n\n1. **Prefer built-in user-input tools** exposed by the current agent runtime — e.g., `AskUserQuestion`, `request_user_input`, `clarify`, `ask_user`, or any equivalent.\n2. **Fallback**: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number\u002Fanswer for each question.\n3. **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.\n\nConcrete `AskUserQuestion` references below are examples — substitute the local equivalent in other runtimes.\n\n## Script Directory\n\nScripts in `scripts\u002F` subdirectory. `{baseDir}` = this SKILL.md's directory path. Resolve `${BUN_X}` runtime: if `bun` installed → `bun`; if `npx` available → `npx -y bun`; else suggest installing bun. Replace `{baseDir}` and `${BUN_X}` with actual values.\n\n| Script            | Purpose                                                                        |\n| ----------------- | ------------------------------------------------------------------------------ |\n| `scripts\u002Fmain.ts` | App discovery + asar extraction + source-map restoration + Prettier formatting |\n\n## When to use\n\nUse this skill whenever the user wants to look inside an installed Electron application or inspect its bundled code. Trigger phrases include:\n\n- \"extract Electron app\", \"decompile this Electron app\", \"unpack app.asar\"\n- \"show me the source of \u003Capp>\", \"look inside \u003Capp>\", \"how is \u003Capp> built\"\n- \"get the source code of Codex \u002F Cursor \u002F Discord \u002F Slack \u002F VS Code \u002F Notion \u002F Obsidian \u002F ChatGPT desktop\"\n- \"提取 Electron 应用\", \"看 \u003Capp> 的源码\", \"反编译 Electron\", \"解包 app.asar\", \"还原 source map\"\n\nBoth **app name** (e.g., `Codex`) and **absolute path** (e.g., `\u002FApplications\u002FCodex.app`, a `.asar` file, or a Windows install dir) are accepted. The script handles discovery for both platforms.\n\n## Workflow\n\n**1. Determine the input.** Ask the user for the app name or path if they haven't given one. If they want a custom output directory, ask for that too.\n\n**2. Run the script.**\n\n```bash\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts \"\u003Capp>\" [--output \u003Cdir>] [--asar \u003Cpath>] [--force]\n```\n\nStart with `--dry-run` first if you're unsure whether discovery will find the right bundle — it prints the resolved paths and exits without touching the filesystem.\n\n**3. Handle the result.**\n\n- **Success** → report the output paths and the counts (extracted \u002F restored \u002F formatted).\n- **Multiple matches** → the script lists candidates and exits non-zero. Show the user the candidates, ask which one to use (via `AskUserQuestion` or the runtime equivalent), then re-run with the chosen absolute path.\n- **Existing non-empty output dir** → the script refuses without `--force`. Ask the user whether to overwrite (`--force`) or pick a new `--output` path.\n- **Unsupported platform \u002F no match** → suggest passing `--asar \u002Ffull\u002Fpath\u002Fto\u002Fapp.asar` if the user knows where the bundle lives.\n\n**4. Point the user at the result.** The default output dir is `~\u002FDownloads\u002F\u003CAppName>-electron-extract\u002F`. The most interesting subdirectory depends on what was found:\n\n- `restored\u002F` exists → the original source tree was reconstructed from `.js.map` files; this is what to read first.\n- Only `extracted\u002F` exists (no maps) → the JS\u002FCSS in `extracted\u002F` was Prettier-formatted in place; read from there.\n\n## Source-map path restoration\n\nThe script should preserve original source names and directory structure as much as the source map allows:\n\n- Resolve each `sources[]` entry with `sourceRoot` when present, then relative to the `.js.map` file's directory inside `extracted\u002F`.\n- Collapse normal bundler-relative paths into the restored project tree. For example, `.vite\u002Fmain\u002Findex.js.map` + `..\u002F..\u002Fsrc\u002Fmain.ts` becomes `restored\u002Fsrc\u002Fmain.ts`.\n- If a source path climbs above `extracted\u002F`, keep the readable remaining path under `restored\u002F` instead of hashing it. For example, `.vite\u002Fmain\u002Findex.js.map` + `..\u002F..\u002F..\u002Fshared\u002Fsrc\u002Flib\u002Ffoo.ts` becomes `restored\u002Fshared\u002Fsrc\u002Flib\u002Ffoo.ts`.\n- Strip URL\u002Fquery decorations from source names, including common `webpack:\u002F\u002F`, `file:\u002F\u002F`, and `?loader` suffixes.\n- Use `restored\u002F__unknown\u002F\u003Chash>.\u003Cext>` only when the source name is empty or cannot be reduced to a safe file path.\n- Continue skipping `node_modules` and `webpack\u002Fruntime\u002F*` entries; these are bundler\u002Fruntime noise, not app sources.\n\n## Usage\n\n```bash\n# Extract by app name (default output: ~\u002FDownloads\u002FCodex-electron-extract\u002F)\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex\n\n# Extract by absolute path (works for .app bundles, install dirs, or .asar files)\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts \"\u002FApplications\u002FVisual Studio Code.app\"\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts \"C:\\Users\\you\\AppData\\Local\\Programs\\codex\"\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts --asar \u002FApplications\u002FCodex.app\u002FContents\u002FResources\u002Fapp.asar Codex\n\n# Custom output\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex --output ~\u002Fwork\u002Fcodex-source\n\n# Preview discovery without writing anything\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex --dry-run\n\n# Overwrite an existing output dir\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex --force\n\n# Machine-readable result (one JSON line on stdout)\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex --json\n```\n\n## Options\n\n| Option           | Short | Description                                                     | Default                                  |\n| ---------------- | ----- | --------------------------------------------------------------- | ---------------------------------------- |\n| `\u003Capp>`          |       | App name or absolute path. Required unless `--asar` is given.   | —                                        |\n| `--output`       | `-o`  | Output directory                                                | `~\u002FDownloads\u002F\u003CAppName>-electron-extract` |\n| `--asar`         |       | Override the resolved `.asar` path                              | auto-discovered                          |\n| `--force`        | `-f`  | Allow writing into a non-empty existing output dir              | false                                    |\n| `--skip-format`  |       | Skip Prettier formatting                                        | false                                    |\n| `--skip-restore` |       | Skip source-map restoration                                     | false                                    |\n| `--no-unpacked`  |       | Don't copy `app.asar.unpacked\u002F` alongside                       | false                                    |\n| `--dry-run`      |       | Print resolved paths and exit without writing                   | false                                    |\n| `--json`         |       | Emit one JSON-line summary on stdout (suppresses normal output) | false                                    |\n\n## Output layout\n\n```\n~\u002FDownloads\u002F\u003CAppName>-electron-extract\u002F\n├── extract-report.json          # JSON summary: counts, warnings, resolved paths\n├── extracted\u002F                   # raw asar contents (JS\u002FCSS Prettier-formatted when no map)\n│   └── ...                      # node_modules left untouched (skipped from format)\n├── extracted.unpacked\u002F          # copied from \u003Casar>.unpacked\u002F if present\n│   └── ...                      # native modules (.node), large assets\n└── restored\u002F                    # only present if at least one .js.map was usable\n    └── \u003Coriginal\u002Fsource\u002Ftree>   # rebuilt from sourcesContent in each .js.map\n```\n\n## Notes\n\n- **node_modules** is always skipped — both for source-map restoration and Prettier formatting — because vendored dependencies are noise when inspecting an app.\n- **Source-map restoration** only works when the `.js.map` embeds `sourcesContent`. This is the common case for modern bundlers (webpack, esbuild, Vite, rollup). If a map references external `.ts`\u002F`.js` files without embedding them, that map is skipped and the corresponding `.js` is Prettier-formatted instead. Skipped maps are listed in `extract-report.json` under `warnings`.\n- **Readable paths over hashes** — don't treat `..\u002F` segments in source-map paths as automatically unsafe. First resolve them from the map location and then sanitize the final output path so it still stays under `restored\u002F`. Hash fallback is only for unusable source names.\n- **App discovery** searches `\u002FApplications` + `~\u002FApplications` on macOS, and `%LOCALAPPDATA%\\Programs`, `%PROGRAMFILES%`, `%PROGRAMFILES(X86)%`, `%APPDATA%` on Windows. If discovery finds multiple matches, the script exits and lists them — re-run with an absolute path. On Linux or other platforms, pass `--asar \u002Fpath\u002Fto\u002Fapp.asar` explicitly.\n- **Safety** — the script refuses to write to `\u002F`, the user home directly, or the current working directory, and refuses to populate an existing non-empty output dir without `--force`.\n- **No global installs** — `@electron\u002Fasar` and `prettier` are resolved on-the-fly via `npx -y`. First run will be slower while npx caches them.\n","# Electron App Extract\n\nExtracts 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 `..\u002F..\u002Fsrc\u002Fmain.ts` restore to readable paths such as `restored\u002Fsrc\u002Fmain.ts` instead of hashed placeholders. Always skips `node_modules`. Works on macOS and Windows.\n\n## User Input Tools\n\nWhen this skill prompts the user, follow this tool-selection rule (priority order):\n\n1. **Prefer built-in user-input tools** exposed by the current agent runtime — e.g., `AskUserQuestion`, `request_user_input`, `clarify`, `ask_user`, or any equivalent.\n2. **Fallback**: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number\u002Fanswer for each question.\n3. **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.\n\nConcrete `AskUserQuestion` references below are examples — substitute the local equivalent in other runtimes.\n\n## Script Directory\n\nScripts in `scripts\u002F` subdirectory. `{baseDir}` = this SKILL.md's directory path. Resolve `${BUN_X}` runtime: if `bun` installed → `bun`; if `npx` available → `npx -y bun`; else suggest installing bun. Replace `{baseDir}` and `${BUN_X}` with actual values.\n\n| Script            | Purpose                                                                        |\n| ----------------- | ------------------------------------------------------------------------------ |\n| `scripts\u002Fmain.ts` | App discovery + asar extraction + source-map restoration + Prettier formatting |\n\n## When to use\n\nUse this skill whenever the user wants to look inside an installed Electron application or inspect its bundled code. Trigger phrases include:\n\n- \"extract Electron app\", \"decompile this Electron app\", \"unpack app.asar\"\n- \"show me the source of \u003Capp>\", \"look inside \u003Capp>\", \"how is \u003Capp> built\"\n- \"get the source code of Codex \u002F Cursor \u002F Discord \u002F Slack \u002F VS Code \u002F Notion \u002F Obsidian \u002F ChatGPT desktop\"\n- \"提取 Electron 应用\", \"看 \u003Capp> 的源码\", \"反编译 Electron\", \"解包 app.asar\", \"还原 source map\"\n\nBoth **app name** (e.g., `Codex`) and **absolute path** (e.g., `\u002FApplications\u002FCodex.app`, a `.asar` file, or a Windows install dir) are accepted. The script handles discovery for both platforms.\n\n## Workflow\n\n**1. Determine the input.** Ask the user for the app name or path if they haven't given one. If they want a custom output directory, ask for that too.\n\n**2. Run the script.**\n\n```bash\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts \"\u003Capp>\" [--output \u003Cdir>] [--asar \u003Cpath>] [--force]\n```\n\nStart with `--dry-run` first if you're unsure whether discovery will find the right bundle — it prints the resolved paths and exits without touching the filesystem.\n\n**3. Handle the result.**\n\n- **Success** → report the output paths and the counts (extracted \u002F restored \u002F formatted).\n- **Multiple matches** → the script lists candidates and exits non-zero. Show the user the candidates, ask which one to use (via `AskUserQuestion` or the runtime equivalent), then re-run with the chosen absolute path.\n- **Existing non-empty output dir** → the script refuses without `--force`. Ask the user whether to overwrite (`--force`) or pick a new `--output` path.\n- **Unsupported platform \u002F no match** → suggest passing `--asar \u002Ffull\u002Fpath\u002Fto\u002Fapp.asar` if the user knows where the bundle lives.\n\n**4. Point the user at the result.** The default output dir is `~\u002FDownloads\u002F\u003CAppName>-electron-extract\u002F`. The most interesting subdirectory depends on what was found:\n\n- `restored\u002F` exists → the original source tree was reconstructed from `.js.map` files; this is what to read first.\n- Only `extracted\u002F` exists (no maps) → the JS\u002FCSS in `extracted\u002F` was Prettier-formatted in place; read from there.\n\n## Source-map path restoration\n\nThe script should preserve original source names and directory structure as much as the source map allows:\n\n- Resolve each `sources[]` entry with `sourceRoot` when present, then relative to the `.js.map` file's directory inside `extracted\u002F`.\n- Collapse normal bundler-relative paths into the restored project tree. For example, `.vite\u002Fmain\u002Findex.js.map` + `..\u002F..\u002Fsrc\u002Fmain.ts` becomes `restored\u002Fsrc\u002Fmain.ts`.\n- If a source path climbs above `extracted\u002F`, keep the readable remaining path under `restored\u002F` instead of hashing it. For example, `.vite\u002Fmain\u002Findex.js.map` + `..\u002F..\u002F..\u002Fshared\u002Fsrc\u002Flib\u002Ffoo.ts` becomes `restored\u002Fshared\u002Fsrc\u002Flib\u002Ffoo.ts`.\n- Strip URL\u002Fquery decorations from source names, including common `webpack:\u002F\u002F`, `file:\u002F\u002F`, and `?loader` suffixes.\n- Use `restored\u002F__unknown\u002F\u003Chash>.\u003Cext>` only when the source name is empty or cannot be reduced to a safe file path.\n- Continue skipping `node_modules` and `webpack\u002Fruntime\u002F*` entries; these are bundler\u002Fruntime noise, not app sources.\n\n## Usage\n\n```bash\n# Extract by app name (default output: ~\u002FDownloads\u002FCodex-electron-extract\u002F)\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex\n\n# Extract by absolute path (works for .app bundles, install dirs, or .asar files)\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts \"\u002FApplications\u002FVisual Studio Code.app\"\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts \"C:\\Users\\you\\AppData\\Local\\Programs\\codex\"\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts --asar \u002FApplications\u002FCodex.app\u002FContents\u002FResources\u002Fapp.asar Codex\n\n# Custom output\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex --output ~\u002Fwork\u002Fcodex-source\n\n# Preview discovery without writing anything\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex --dry-run\n\n# Overwrite an existing output dir\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex --force\n\n# Machine-readable result (one JSON line on stdout)\n${BUN_X} {baseDir}\u002Fscripts\u002Fmain.ts Codex --json\n```\n\n## Options\n\n| Option           | Short | Description                                                     | Default                                  |\n| ---------------- | ----- | --------------------------------------------------------------- | ---------------------------------------- |\n| `\u003Capp>`          |       | App name or absolute path. Required unless `--asar` is given.   | —                                        |\n| `--output`       | `-o`  | Output directory                                                | `~\u002FDownloads\u002F\u003CAppName>-electron-extract` |\n| `--asar`         |       | Override the resolved `.asar` path                              | auto-discovered                          |\n| `--force`        | `-f`  | Allow writing into a non-empty existing output dir              | false                                    |\n| `--skip-format`  |       | Skip Prettier formatting                                        | false                                    |\n| `--skip-restore` |       | Skip source-map restoration                                     | false                                    |\n| `--no-unpacked`  |       | Don't copy `app.asar.unpacked\u002F` alongside                       | false                                    |\n| `--dry-run`      |       | Print resolved paths and exit without writing                   | false                                    |\n| `--json`         |       | Emit one JSON-line summary on stdout (suppresses normal output) | false                                    |\n\n## Output layout\n\n```\n~\u002FDownloads\u002F\u003CAppName>-electron-extract\u002F\n├── extract-report.json          # JSON summary: counts, warnings, resolved paths\n├── extracted\u002F                   # raw asar contents (JS\u002FCSS Prettier-formatted when no map)\n│   └── ...                      # node_modules left untouched (skipped from format)\n├── extracted.unpacked\u002F          # copied from \u003Casar>.unpacked\u002F if present\n│   └── ...                      # native modules (.node), large assets\n└── restored\u002F                    # only present if at least one .js.map was usable\n    └── \u003Coriginal\u002Fsource\u002Ftree>   # rebuilt from sourcesContent in each .js.map\n```\n\n## Notes\n\n- **node_modules** is always skipped — both for source-map restoration and Prettier formatting — because vendored dependencies are noise when inspecting an app.\n- **Source-map restoration** only works when the `.js.map` embeds `sourcesContent`. This is the common case for modern bundlers (webpack, esbuild, Vite, rollup). If a map references external `.ts`\u002F`.js` files without embedding them, that map is skipped and the corresponding `.js` is Prettier-formatted instead. Skipped maps are listed in `extract-report.json` under `warnings`.\n- **Readable paths over hashes** — don't treat `..\u002F` segments in source-map paths as automatically unsafe. First resolve them from the map location and then sanitize the final output path so it still stays under `restored\u002F`. Hash fallback is only for unusable source names.\n- **App discovery** searches `\u002FApplications` + `~\u002FApplications` on macOS, and `%LOCALAPPDATA%\\Programs`, `%PROGRAMFILES%`, `%PROGRAMFILES(X86)%`, `%APPDATA%` on Windows. If discovery finds multiple matches, the script exits and lists them — re-run with an absolute path. On Linux or other platforms, pass `--asar \u002Fpath\u002Fto\u002Fapp.asar` explicitly.\n- **Safety** — the script refuses to write to `\u002F`, the user home directly, or the current working directory, and refuses to populate an existing non-empty output dir without `--force`.\n- **No global installs** — `@electron\u002Fasar` and `prettier` are resolved on-the-fly via `npx -y`. First run will be slower while npx caches them.\n",{"name":5,"version":24,"metadata":25,"description":7},"1.119.0",{"openclaw":26},{"homepage":27,"requires":28},"https:\u002F\u002Fgithub.com\u002FJimLiu\u002Fbaoyu-skills#baoyu-electron-extract",{"anyBins":29},[30,31],"bun","npx","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","03-逆向工程\u002Fbaoyu-electron-extract",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":41,"prompt":50,"zipAvailable":51},[42,44,47],{"tool":31,"command":43},"npx skills add lza6\u002FArmor-piercing-system-prompts --skill baoyu-electron-extract",{"tool":45,"command":46},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill baoyu-electron-extract",{"tool":48,"command":49},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill baoyu-electron-extract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fbaoyu-electron-extract\u002FSKILL.md",true,[],[54,62,67,74,81,88],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":61},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":63,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":61},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":61},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":61},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":61},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":61},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]