skills.rest
Sailfishc
SailfishcCOMMUNITY
Explore all skills by this author →
Website𝕏@sailfishcc1GitHub

electron-app-inspection-harness

Coordinate CDP, MCP, and parity tooling to inspect Electron apps and generate Codex-ready task packs.

Updated Apr 25, 2026
Search Tags:#automation#codex#mcp#electron#cdp#inspection#parity
One-click install
npx skills add https://github.com/Sailfishc/guanfu --skill electron-app-inspection-harness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: electron-app-inspection-harness
Source: https://github.com/Sailfishc/guanfu/tree/main/skills/electron-app-inspection-harness
Command: npx skills add https://github.com/Sailfishc/guanfu --skill electron-app-inspection-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @electron/asar, chrome-remote-interface, puppeteer-core, playwright, pixelmatch, pngjs, and includes scripts (resource) components.

What problem does it solve?

The Electron App Inspection Harness provides a repeatable, end-to-end workflow to observe, analyze, and report on the UI/UX and runtime behavior of Electron applications, turning scattered findings into Codex-ready tasks.

Core Features & Use Cases

  • Multi-channel observation: CDP/Chrome DevTools MCP, and Playwright MCP to gather DOM, events, performance, and accessibility data.
  • Static analysis and parity: asar extraction mapping, IPC/menus/tokens, and parity-driven implementation planning.
  • Handoff automation: generates a Codex task contract, vertical slices, and implementation prompts for fast, modular delivery.
  • Workflows and tooling bootstrap: scripts to initialize, capture evidence, validate packs, and evolve the harness.

Quick Start

Initialize the inspection with the script for your target app and output directory, then inspect the generated 00-meta and 01-runtime artifacts.

Frequently Asked Questions about electron-app-inspection-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Electron app inspection for UI parity and runtime analysis?▼

Automate Electron app inspection by coordinating CDP, MCP, and parity tooling to gather DOM, events, performance, and accessibility data. The harness extracts asar files, maps IPC and menus, and outputs structured evidence packs for review.

What is the best way to generate Codex-ready tasks from Electron app runtime behavior?▼

Generate Codex-ready tasks by using an inspection harness to observe runtime behavior and convert findings into task contracts. It produces vertical slices and implementation prompts for fast, modular delivery directly from captured evidence.

Can I use Playwright and Puppeteer together for Electron app static analysis and automation?▼

Yes, the inspection harness uses Playwright and puppeteer-core alongside chrome-remote-interface for multi-channel observation. This combination gathers UI/UX parity data and performs asar static analysis to map application structure.

Do I need CDP to inspect Electron apps and produce structured evidence packs?▼

You need CDP to inspect Electron apps because it enables Chrome DevTools MCP integration for gathering runtime data. The harness coordinates this with parity tooling to validate packs and ensure provenance for handoff.

Why does my Electron app inspection workflow lack provenance and structured task contracts?▼

Your inspection workflow lacks provenance because it does not use a coordinated harness to organize findings. The harness generates hierarchical packs with meta and runtime artifacts, validating them to satisfy task contract requirements.

What limitations exist when using asar extraction and pixelmatch for Electron UI testing?▼

Asar extraction maps static structure while pixelmatch compares PNG screenshots for UI parity testing. Limitations arise if the target app lacks accessible DOM elements or if runtime behavior cannot be captured through CDP automation.

Related Skills

Explore More Software Engineering Skills→
Sacred-GSacred-G
2

playwright-interactive

Orchestrate a persistent Playwright session for debugging local web and Electron apps.

Community
Advanced
ollieb89ollieb89

agent-native-architecture

Design agent-native architectures with atomic tools and prompts for UI action parity.

Community
Advanced
ruuxiruuxi
29

electron

Automate Electron desktop apps via Chrome DevTools Protocol remote debugging.

Community
Intermediate
adobeadobe
45

Testing Blocks

Validate Alpine Eco Drive project code changes with unit, browser, linting and performance checks.

Official
Intermediate