CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong operational skill body: executable, placeholder-resolved commands with complete options and usage examples, a sequenced workflow with dry-run validation and explicit error-recovery branches, and correct separation of implementation into the bundled script. The only deductions are trimmable meta-guidance about user-input tooling and inlined source-map internals that belong in the script or a reference file.

Suggestions

Compress the "User Input Tools" section to a single line (e.g., 'Ask the user via the runtime's user-input tool if available; otherwise numbered plain-text questions, batched when possible') — Claude already knows how to prompt users, and the current ~9 lines are the largest source of avoidable tokens.

Move the "Source-Map Path Restoration" internals (sourceRoot resolution, ../-segment policy, URL stripping, __unknown fallback) into comments in scripts/main.ts or a reference file; SKILL.md only needs the outcome — restored/ is rebuilt from embedded sourcesContent and skipped maps are listed in extract-report.json warnings.

Trim the Usage block's overlapping examples with Workflow step 2 (the plain app-name invocation appears in both) to remove duplication and reduce token cost.

DimensionReasoningScore

Conciseness

The body is dense and operational (options table, output layout, platform paths) with no explanation of concepts Claude already knows, but the "User Input Tools" section spends ~9 lines on meta-guidance about prompting mechanics Claude can handle, and the Usage block duplicates the Workflow's command. This fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Commands are fully executable once the two explicitly-defined placeholders are substituted ("Replace {baseDir} and ${BUN_X} with actual values", with the bun/npx resolution rule given), and the Usage block covers the common cases: app name, macOS .app path, Windows install dir, --asar override, --output, and --json. Copy-paste ready with specific examples; no gaps that would drop it to 4.

5 / 5

Workflow Clarity

The 4-step workflow has explicit validation and feedback loops: "run with --dry-run first" as a pre-check, and step 3's error-recovery branches ("Multiple matches → ... re-run with the chosen absolute path", "Existing non-empty output dir → ... --force or pick a new --output"), plus a result report with counts and warnings. Although the operation is batch-like, validation is present (dry-run, safety refusals, extract-report.json warnings), so the missing-validation cap at 3 does not apply.

5 / 5

Progressive Disclosure

The bundle structure is well used: all implementation lives in the clearly-signaled one-level-deep `scripts/main.ts` (verified to exist), and SKILL.md stays an operational overview. However, the "Source-Map Path Restoration" section inlines ~10 lines of script internals (path-resolution edge cases) that Claude does not need to run the skill, which fits 'good structure; minor organization gaps' rather than the fully clean split at 5. The unreferenced scripts/main.test.ts in the bundle is a minor navigational gap.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person voice, multiple concrete capabilities, explicit scope limits, and a rich 'Use when' clause with natural trigger phrases, file extensions, synonyms, and bilingual variants. Both 'what' and 'when' are answered explicitly with no fluff or over-claims.

DimensionReasoningScore

Specificity

"Extracts resources and JavaScript from any installed Electron app (.asar bundle)", "restoring original sources from .js.map files", and "formatting minified code with Prettier otherwise" are multiple concrete actions covering the skill's full capability space, plus explicit scope constraints ("Skips node_modules", "supports both macOS and Windows"). This matches the comprehensive-coverage anchor; score 4 would require identifiable gaps in coverage, and none are present.

5 / 5

Completeness

Both parts are explicit: 'what' via the concrete action list, and 'when' via a full "Use when user wants to..." clause with concrete trigger phrases. This matches the anchor for clearly answering both what AND when; score 4 would require the 'when' to be less explicit, but it enumerates specific user utterances.

5 / 5

Trigger Term Quality

Trigger phrases include natural user wording ("extract Electron app", "decompile Electron", "get the source code of <app>", "inspect app.asar"), file extensions (.asar, .js.map), synonyms across verbs, and even non-English variants ("看 Electron 应用源码", "提取 .asar"). This is comprehensive coverage including synonyms and extensions, exceeding the good-coverage anchor at 4.

5 / 5

Distinctiveness Conflict Risk

The Electron/.asar niche is clear and the triggers ("inspect app.asar", "decompile Electron", "get the source code of <app>") are distinct from other extraction or decompilation domains, giving minimal conflict risk. Score 4's anchor (minor overlap with closely related skills) does not fit better since no plausible sibling skill shares these triggers.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

JimLiu/baoyu-skills

Path

skills/baoyu-electron-extract/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.