メニュー
Install and validate a teammate-delivered FlowPad test build. Builds the matching backend from source, installs the provided Electron app, and verifies FlowPad ownership of the SOD key in the OS credential store.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Cut a Flowpad release — bump the version (patch by default; minor/major on request), build the wheel (UI baked in), publish to PyPI, tag + push to GitHub, and validate the install. Then, if the electron/ directory changed since the previous release, trigger the desktop build. Use when asked to deploy/release Flowpad, publish to PyPI, or cut a new version (including a new minor like 0.3.0).
toplog — topic-tracing assistant for debugging. `run` activates the right trace topics for a given issue (in code or tests) so RCA has better traceability; `scan` reconciles the topics referenced in code against the topic catalog; `learn` consolidates post-RCA findings (enrich a topic, add a new one with its trace points, or retire a stale one). Use when debugging a hard failure and you want richer logs before or alongside RCA, when adding or auditing toplog topics, or after proving a root cause to capture the traceability that helped. Also triggers on "turn on tracing for X", "what topics cover Y", "add a toplog topic", or "audit toplog topics".
Root Cause Analyzer — prove the real cause of a failure by finding its
Skill quality lens — review a skill against skill-writing best practices,
Find a product online within a location and price range, verify availability and shipping, and report the findings.
Analyze an agentic execution from its session transcript and produce
| id | 664c9bc2-4afa-528d-b7c5-a3998c27aecf |
| name | install-flowpad-test-build |
| description | Install and validate a teammate-delivered FlowPad test build. Builds the matching backend from source, installs the provided Electron app, and verifies FlowPad ownership of the SOD key in the OS credential store. |
| tags |
Use this skill when a teammate sends:
The backend and desktop application must come from the same branch.
Set these before starting:
BRANCH_NAME=FLOWPAD-1862
DMG_PATH=~/Downloads/Flowpad-arm64.dmg
WORKDIR=~/Developer/flowpad-$BRANCH_NAME
Verify all prerequisites before proceeding.
which uv
git --version
Verify repository access:
gh auth status
or
ssh -T git@github.com
If any prerequisite fails, stop and report the issue.
Clone or update the repository:
if [ ! -d "$WORKDIR" ]; then
git clone git@github.com:langware-labs/flowpad.git "$WORKDIR"
fi
cd "$WORKDIR"
git fetch origin
git checkout "$BRANCH_NAME"
git pull
Build the backend:
uv sync
source .venv/bin/activate
rm -rf dist build *.egg-info
python build_ui.py
uv build
deactivate
uv tool uninstall flowpad || true
uv cache clean flowpad --force || true
uv tool install \
--reinstall \
--force \
./dist/flowpad-*.whl
open "$DMG_PATH"
In Finder:
flow
Verify static assets exist:
STATIC_DIR=~/.local/share/uv/tools/flowpad/lib/python*/site-packages/flow_sdk/server/static/assets
find $STATIC_DIR -name "index-*.js" | head
Verify application signature:
codesign -dv --verbose=4 \
/Applications/Flowpad.app
Verify:
ls -l \
/Applications/Flowpad.app/Contents/Resources/flow-rs/flow-rs
Verify binary executes:
/Applications/Flowpad.app/Contents/Resources/flow-rs/flow-rs --version
Verify binary signature:
codesign -dv --verbose=4 \
/Applications/Flowpad.app/Contents/Resources/flow-rs/flow-rs
Verify:
Launch FlowPad.
Log in using the normal cloud login flow.
Wait until the application is fully initialized.
Open:
Keychain Access
Search for:
Flowpad.ai.sod_key
Open the keychain item.
Navigate to:
Access Control
Expected:
flow-rs
must appear in the trusted applications list.
Expected:
python3.*
must NOT appear.
This is the primary validation that the migration succeeded.
Navigate to:
Attributes
Expected Account value:
prod.flow-rs
If the account still contains the legacy value:
prod
the migration likely did not run.
After login:
Expected:
No dialog stating:
python3.12 wants to use your confidential information...
If such a prompt appears:
Capture a screenshot and collect logs.
Confirm:
LATEST_MAIN=$(ls -t ~/.flow/logs/main_desktop/*.log | head -1)
LATEST_SERVER=$(ls -t ~/.flow/instances/prod/logs/server/*.log | head -1)
grep -Ei \
"flow-rs|sod_key|keychain|secret|seed|migrate" \
"$LATEST_MAIN" \
"$LATEST_SERVER" | tail -100
Report immediately if any of the following occur:
Successful migration means:
Electron ↓ flow-rs ↓ OS Keychain
and NOT:
Electron ↓ python3.12 ↓ OS Keychain
The user should experience a single trusted FlowPad identity with no Python-attributed keychain prompts.