TG0 EE Skills

Five electrical engineering skills for local Claude Code and Codex.

Package: tg0-ee-skills · Version: 0.1.0 View on npm. Use a pinned version for reproducible reviews.

Public npm distribution of the five skills in this repository, for local Claude Code and Codex. Source remains in Bitbucket; package users do not need Bitbucket access. The npm name tg0-ee-skills is unscoped: no npm organization is required.

Included skills

| Skill | Purpose | | --- | --- | | datasheet-lookup | Evidence-based component datasheet reading | | pcb-schematic-review | Schematic, connectivity and BOM review | | pcb-layout-review | Copper, placement, routing and manufacturing review | | pcb-review | Combined schematic and layout review | | product-datasheet-filler | Populate the ODT template, verify source coverage, and prepare DOCX delivery |

The remote repository's pcb-review name is retained. The older, separate pcb-design-review-v1.1.0.zip is not used to overwrite the newer repository checkers. The BACKGROUND/link-gate changes from that archive still need a separately tested merge.

Install

Prerequisite: Node.js 22 or newer, including npm/npx. Python helpers require Python 3.11–3.13. The installer does not download Node, Python, Chrome or the agent applications.

# Preview; no files written
npx tg0-ee-skills@latest setup --dry-run

# All five skills for both local agents, plus isolated Python dependencies
npx tg0-ee-skills@latest setup --with-python

# Skills only, or one agent
npx tg0-ee-skills@latest setup
npx tg0-ee-skills@latest setup --agent codex

Claude Code receives copies in ~/.claude/skills; Codex receives copies in ~/.agents/skills. Start a new agent session after installation. This does not install skills into Claude web/Cowork or remote/cloud agents. Local agent settings are not edited. No Git, Bitbucket account, Google login, or MCP server is required by end users.

After starting a new session, ask for the task you need, for example:

• "Check this component's supply limits and cite the datasheet pages."
• "Review these Altium schematics for connectivity and BOM issues."
• "Review this board's layout, decoupling and manufacturing constraints."
• "Run a complete review of this Altium project and identify unverified checks."
• "Fill the product datasheet template using this structured JSON."

These skills support engineering review; script output does not replace physical validation or the responsible engineer's release decision.

The tool refuses existing unmanaged skill folders, locally edited managed copies, symlink/junction destinations and conflicting legacy ~/.codex/skills copies. It does not silently replace work installed by another manager. Back up and resolve such copies before retrying; no --force option is provided.

Update and remove

npx tg0-ee-skills@latest check
npx tg0-ee-skills@latest update --dry-run
npx tg0-ee-skills@latest update --with-python
npx tg0-ee-skills@latest status
npx tg0-ee-skills@latest uninstall

check only queries public npm metadata. update applies the version of the package being executed, only to copies previously installed by this tool; @latest fetches the current package first. Running an old cached CLI does not fetch new skill content. Downgrades are refused. No automatic updater, scheduled task or startup hook is created. Close active reviews before updating: source files switch on disk, while an existing agent may retain previously loaded instructions. Use a fixed npm version for reproducible work.

Changes are preflighted across all selected skills, staged, then switched; ordinary errors restore prior directories. Concurrent installers use a lock. Prior copies and state are kept under ~/.tg0/ee-skills/backups/. This is not a power-failure-proof filesystem transaction: after a killed process, inspect the transaction's operations.json and previous-state.json, restore any interrupted moves, then remove the stale install.lock only when no installer is running. There is no automatic rollback command yet. Uninstall keeps backups and Python environments; it leaves other skills untouched.

Python helpers

npx [email protected] deps
npx [email protected] doctor
npx [email protected] run pcb-review intake.py /path/to/submission

deps creates ~/.tg0/ee-skills/runtimes/<package-version>/ and installs the union of the authored requirements there, never into system Python. --python PATH selects a Python executable. Version is checked rather than inferred from the launcher name. Requirements currently use upstream minimum versions, not a fully reproducible lockfile. run uses that environment and preserves the caller's working directory; provide template and reference paths relative to the installed skill directory or as absolute paths. The template fill step uses the Python standard library. Its image and design-check helpers also use the packaged Python dependencies and the sibling pcb-review skill.

The upstream DOCX delivery step uses product-datasheet-filler/scripts/to_docx.ps1 and requires Windows PowerShell and desktop Microsoft Word (COM automation). It is not installed by deps. Run that PowerShell script directly using its installed path, then run harden_docx.py through the Python runner. The run command currently accepts Python scripts only. ODT generation does not require Word; complete DOCX delivery does.

Chrome/Chromium is required for PCB PDF reports. On macOS the upstream renderer's search paths are incomplete; exposing the browser as google-chrome on PATH is currently required. doctor reports environment findings, not hardware acceptance or proof of a correct review.

Troubleshooting

| Message or symptom | What to do | | --- | --- | | npx is not recognized | Install Node.js 22+ and reopen your terminal. | | Compatible Python not found | Install Python 3.11–3.13 or pass --python with its executable path. | | Existing unmanaged skill | Back up and resolve an existing installation before retrying. The tool will not overwrite another manager's copy. | | Local modifications | Preserve and review your edits before updating or uninstalling. | | Legacy Codex skill exists | Resolve the duplicate under ~/.codex/skills before installing into ~/.agents/skills. | | Chrome missing | Install Chrome/Chromium; see the macOS path limitation above. | | npm returns 404 | Check the package name and whether the first release has been published. |

Development and release

npm ci --ignore-scripts
npm run build
npm test
npm run verify:pack
npm pack

Tests install exclusively into temporary home directories. No personal agent installation or Python dependency installation is performed by the test suite. release-files.json lists the exact source files copied into bundle/; package.json only publishes bundle, CLI/runtime code and release documentation. The build adds portable runtime guidance to the bundled SKILL.md copies and shortens their discovery descriptions below 1024 characters, without changing the authored source instructions/checkers. SHA-256 inventories detect missing/modified package and installed files; they are not a publisher signature. npm handles registry package integrity.

See public release contents and Bitbucket release setup. A matching v0.1.0 tag triggers the configured CI release after checks pass when publishing credentials are configured; normal commits only validate.

A personal npm publisher account is sufficient for the unscoped tg0-ee-skills package; an npm organization is not required. Configure the secured NPM_TOKEN deployment variable in Bitbucket's npm-production environment before releasing. End users do not need npm accounts. Never commit publishing credentials or share them in documentation.

The public package includes the authored reference files, ODT template and product example. Review the linked inventory before publishing. The current license field is UNLICENSED; maintainers must choose the intended license terms before the first release.