Safeflow Sui Skill

What to check before installing or running this skill: - Understand the real effect: the scripts will call your local 'sui' CLI and operate on the local keystore (create addresses, switch active address, create session caps, and execute payments). Only run them if you (or the owner) fully control and trust the keys on that machine. - Packaging gap: the E2E test script expects an agent_scripts directory containing TypeScript runner code (create_intent.ts, e2e_runner.ts) which is not in the bundle. The publish-api test flow will fail unless you supply or inspect those scripts from a trusted source. - Network endpoints: the scripts contact known SafeFlow/Walrus endpoints and public faucets (producer.safeflow.space, dash.safeflow.space, walrus-testnet endpoints). Verify those domain names are the intended services before running against mainnet or trusting them with evidence uploads. - Secrets: the bundle does not request credentials, but you may be asked to pass --postgres-dsn or --api-key when running tests; these contain secrets and will be written into local env files if you use save_owner_config.sh. Do not paste secrets unless you trust the deployment and have reviewed agent_scripts. - Run in a safe environment first: test on a separate machine or testnet wallet with no funds or with testnet faucet funds. Review all scripts line-by-line (you have them) and ensure you are comfortable with the file writes and sui CLI calls. - Avoid autonomous execution: do not allow the skill to run unattended or autonomously execute these scripts, since they can make on-chain payments. Require manual owner approval for any run that will call execute_payment.sh or create session caps. If you need a safer assessment, provide the missing agent_scripts directory (create_intent.ts, e2e_runner.ts) or confirm the origin/trustworthiness of the producer/walrus endpoints and I can reassess with higher confidence.