CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-framework-electron

Electron 33+ desktop app development specialist covering Main/Renderer process architecture, IPC communication, auto-update, and packaging with Electron Forge. Use when building cross-platform desktop applications.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.moai/archive/skills/v2.16/moai-framework-electron/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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.

The skill is well-organized with clear sequences, a useful verification checklist, and genuinely valuable security judgment (Red Flags, Rationalizations), but its core delivery mechanism is broken: it deliberately stripped all code examples and delegates to reference.md and examples.md, which are missing from the bundle, leaving it as narrative direction with dead links. Internal telemetry metadata and a recap of Electron fundamentals further dilute the token budget.

Suggestions

Add the missing reference.md and examples.md files to the bundle (under references/), since every 'see reference.md/examples.md' pointer currently resolves to a nonexistent file and the delegated detail is unreachable.

Restore minimal executable snippets for the core flows — the exact create-electron-app command, a BrowserWindow webPreferences block, and an electron-builder.yml skeleton — so the main workflows are actionable without the (currently missing) external files.

Remove the internal 'Telemetry Window' audit metadata and the 'Core Capabilities' recap of standard Electron architecture, and fix the false 'auto-loaded via paths frontmatter' claim (no paths field exists in the frontmatter).

DimensionReasoningScore

Conciseness

Mostly prescriptive direction rather than tutorial padding, but it includes unnecessary material: the "Core Capabilities" section restates Electron fundamentals Claude already knows ("Main process runs as single instance per application with full Node.js access", "Renderer processes display web content in sandboxed environments"), and the "Telemetry Window" section is ~15 lines of internal governance metadata (audit verdicts, wave dates, decision criteria) irrelevant to executing the skill. Prose-only descriptions of directory layout also cost more tokens than a tree or snippet would.

3 / 5

Actionability

There is concrete guidance — specific settings ("contextIsolation enabled, nodeIntegration disabled, sandbox enabled"), real API names (app.enableSandbox(), ipcMain.handle, contextBridge.exposeInMainWorld, webRequest.onHeadersReceived), and executable debug commands ("npx electron-rebuild", "DEBUG=electron-updater") — but it is incomplete. The footer admits "removed all code examples, converted to narrative text format", and even Project Initialization only says it "requires running the create-electron-app command" without giving the command. Not 4 because there is essentially no copy-paste-ready code or commands for the core implementation flows.

3 / 5

Workflow Clarity

Multi-step processes are clearly sequenced ("First, enable sandbox globally using app.enableSandbox()... Then request single instance lock... Window creation should occur after the app ready event"), with per-platform packaging steps and a Verification checklist ("Application packages successfully with Electron Forge (show build output)") plus a Troubleshooting section for error recovery. Not 5 because validation checkpoints are end-state checks rather than embedded validate-and-retry feedback loops within the workflows.

4 / 5

Progressive Disclosure

The body is structured as an overview delegating detail to reference.md and examples.md ("see examples.md Main Process Entry Point section", "see reference.md Security Best Practices section") — good signaling and one level deep — but neither file exists in the bundle: there are no references/, scripts/, or assets/ directories at all, so every delegated link is dead and the detailed content is simply unavailable. It also claims TypeScript/JavaScript rules are "auto-loaded via paths frontmatter" when no paths field exists in the frontmatter. Not 3 because clearly-signaled references to nonexistent files are a worse navigation failure than the unclear signaling at anchor 3; not 1 because the SKILL.md body itself is well-sectioned and does not nest references multiple levels deep.

2 / 5

Total

12

/

20

Passed

Description

75%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.

A solid description that clearly states both capabilities and an explicit 'Use when' trigger, with good natural keyword coverage for the Electron/desktop domain. Its main weakness is the generic trigger clause, which doesn't bind activation to Electron specifically, and topic-framing rather than action-framing of capabilities.

DimensionReasoningScore

Specificity

The description lists several concrete coverage areas — "Main/Renderer process architecture, IPC communication, auto-update, and packaging with Electron Forge" — going beyond naming the domain. It falls short of 5 because capabilities are framed as topics being "covered" by a "specialist" rather than concrete actions, a slightly fluffy framing.

4 / 5

Completeness

Both parts are explicit: what ("Electron 33+ desktop app development specialist covering Main/Renderer process architecture, IPC communication, auto-update, and packaging") and when ("Use when building cross-platform desktop applications"). Not 5 because the 'when' clause is generic — it omits Electron itself and concrete trigger phrases, so the trigger guidance could be considerably more specific.

4 / 5

Trigger Term Quality

Strong natural terms are present: "Electron", "desktop app development", "IPC communication", "auto-update", "packaging", "building cross-platform desktop applications" — phrases users would genuinely say. Not 5 because common variations like "Electron app", "desktop installer", or file artifacts (.dmg, .exe, AppImage) are missing.

4 / 5

Distinctiveness Conflict Risk

The 'what' carves a clear Electron-specific niche with minimal conflict risk against unrelated skills. Not 5 because the trigger clause "building cross-platform desktop applications" is framework-agnostic and could fire for Tauri, Qt, or Flutter desktop requests; not 3 since the domain is far more distinct than broadly overlapping skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

modu-ai/moai-adk

Path

.moai/archive/skills/v2.16/moai-framework-electron/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.