EDA Skillpack
Public Made by Adomby adom
All skills for all EDA capabilities across the Adom ecosystem.
ff7a528
28d ago
name: eda-design-summary-video description: >- Make a narrated evidence-based video of PCB placement, routing, validation and native 3D comparison. Use when asked to show the team what the AI did, summarize my PCB redesign, record a before and after, or make an engineering meeting video. user-invocable: true
Parent skill: eda-engineering
Show the engineering work in a concise video
Use the selected bridge's native recording capabilities and the shared demo/recording and speech skills. Record actual CAD windows. Preserve raw takes and edits; do not create an animation of traces and present it as live editor execution. For public sharing, verify source/design visibility and keep unrelated private windows or boards out of the capture.
Plan the story around visible evidence: original board; proved stripped/off-board state if requested; new placement; native trace/via commits; pours and revisions; measured native checks; full native 3D assembly and comparison. Explain the criteria and decisions a user can assess. Distinguish precomputed candidate replay from fresh calculation occurring live. A concise rationale and calculation result is sufficient; do not expose private internal chain-of-thought.
Log start/stop IDs and native operations. Stop recording in a finally block and collect the actual finalized file. Encoded duration can differ from wall-clock logs, so locate cut points from frames. Inspect transitions, last route additions and final repair; never use a fully routed shot as proof of an unrouted placement state. Keep unsuccessful takes as evidence.
Remove idle intervals and label the actual action speed. Repeated inspection camera clips should say replay; still frames should say hold. For comparisons use matching scale/orientation, readable labels and a responsive presentation. Show important component moves with native selection or clearly editorial callouts. Preserve enough context that viewers can identify the tool and board.
Write narration from verified results. State what changed, why, what failed and was corrected, what the checks measured, and what remains unqualified. Use Adom's shared TTS skill for narration assets, normalize speech loudness, check clipping and transitions, and leave a short final reading hold after the last words. Do not cut speech to meet an arbitrary duration.
Validate the final media with ffprobe, a full decode, sampled sequential frames and an audio-ending check. Save a manifest of sources, intervals, playback factors, captions, narration and file hash. Retain the original output when revising an ending.
Transfer the finished MP4 to the user's actual host and verify its bytes. Open through the host's video association when requested; verify exact filename and playback state in the player. A container link or successful launch response alone does not prove playback.
For a meeting page, lead with a responsive native HTML video element: <video width="100%" controls playsinline preload="metadata" src="ABSOLUTE_PUBLISHED_MEDIA_URL"></video>. Add a short outcome
summary, chapter timestamps, measured results/limits, original source and shared skill links. Verify
published playback metadata and page layout. Publishing source skills is distinct from publishing an
installable skillpack; do not promise package installation unless the released tarball actually
contains them.
---
name: eda-design-summary-video
description: >-
Make a narrated evidence-based video of PCB placement, routing, validation and native 3D comparison. Use when asked to show the team what the AI did, summarize my PCB redesign, record a before and after, or make an engineering meeting video.
user-invocable: true
---
Parent skill: eda-engineering
# Show the engineering work in a concise video
Use the selected bridge's native recording capabilities and the shared demo/recording and speech
skills. Record actual CAD windows. Preserve raw takes and edits; do not create an animation of
traces and present it as live editor execution. For public sharing, verify source/design visibility
and keep unrelated private windows or boards out of the capture.
Plan the story around visible evidence: original board; proved stripped/off-board state if
requested; new placement; native trace/via commits; pours and revisions; measured native checks;
full native 3D assembly and comparison. Explain the criteria and decisions a user can assess.
Distinguish precomputed candidate replay from fresh calculation occurring live. A concise rationale
and calculation result is sufficient; do not expose private internal chain-of-thought.
Log start/stop IDs and native operations. Stop recording in a finally block and collect the actual
finalized file. Encoded duration can differ from wall-clock logs, so locate cut points from frames.
Inspect transitions, last route additions and final repair; never use a fully routed shot as proof
of an unrouted placement state. Keep unsuccessful takes as evidence.
Remove idle intervals and label the actual action speed. Repeated inspection camera clips should say
replay; still frames should say hold. For comparisons use matching scale/orientation, readable
labels and a responsive presentation. Show important component moves with native selection or
clearly editorial callouts. Preserve enough context that viewers can identify the tool and board.
Write narration from verified results. State what changed, why, what failed and was corrected, what
the checks measured, and what remains unqualified. Use Adom's shared TTS skill for narration assets,
normalize speech loudness, check clipping and transitions, and leave a short final reading hold
after the last words. Do not cut speech to meet an arbitrary duration.
Validate the final media with ffprobe, a full decode, sampled sequential frames and an audio-ending
check. Save a manifest of sources, intervals, playback factors, captions, narration and file hash.
Retain the original output when revising an ending.
Transfer the finished MP4 to the user's actual host and verify its bytes. Open through the host's
video association when requested; verify exact filename and playback state in the player. A
container link or successful launch response alone does not prove playback.
For a meeting page, lead with a responsive native HTML video element: `<video width="100%" controls
playsinline preload="metadata" src="ABSOLUTE_PUBLISHED_MEDIA_URL"></video>`. Add a short outcome
summary, chapter timestamps, measured results/limits, original source and shared skill links. Verify
published playback metadata and page layout. Publishing source skills is distinct from publishing an
installable skillpack; do not promise package installation unless the released tarball actually
contains them.